Hi Metthew, looking at the documentation which is available at
http://docs.sun.com/app/docs/doc/819-2397 with respect to deployment of differential flash archives it says on page 18: "If the clone system has already been modified or is not running the unchanged master image, the update fails. If you have many changes to make on the clone systems, you can do an initial installation at any time." According to the figure 1-2, it is not possible to deploy differential archive on clone system, if * extra files were installed on the clone * some files were removed from the clone As far as skipping some validation steps is concerned, forced_deployment seems to work only if new files are found during validation process - for other cases you might want to try following keywords: * no_content_check - skips file-by-file validation (and causes to delete new files on clone) * no_master_check - skips validation that clone was built from master system I am not sure if they might help you in your case - also even if you are able to proceed with deployment, you might not end up with system in the desired state. For more information, please also see http://docs.sun.com/app/docs/doc/819-2396 Best regards, Jan Matthew C Aycock wrote: > I have used jumpstart to install approximately 150 workstations. Now its time > to patch/update them. I created a new incremental flash archive, but it does > not want to install. It complains about new and modified files. Well of > course some things have been changed in the course of 3 months of use. > > Any hints on how to force the deployment? I tried the forced_deployment > keyword in the profile but no luck. > > BlueUmp > > > This message posted from opensolaris.org > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/install-discuss >
