If you have a job that contains a deploy image task, reboot to production, and then a set of tasks to continue the configuration of the workstation (we'll refer to these as the "follow-up" tasks), these jobs often fail during the follow-up tasks. Sometimes, you may as well see odd failures in Minisetup that, because MiniSetup doesn't complete, may as well fail the tasks/job.
For instance, we've seen at least the following results:
Tasks fail while executing if a policy "fires" at the same time and forces some conflicting behavior (e.g. reboot)
There are varying errors that occur depending on the timing of Windows setup:
1) The tasks designed to execute in production don't complete because something running in the background interrupts them.. This is the case for #2 and #3 above.
2) Portions of the unattend.xml file that Windows is using to complete Windows setup aren't processed correctly because a task (e.g. an apply system configuration task) modified the workstation configuration and makes Windows believe setup is complete, or confuses it, or something. Often MiniSetup will simply skip sections.
For instance, if the OOBESystem, audituser, and auditsystem passes are skipped, users commonly report things like:
The cause of the issue is that the Symantec Management Agent is connecting up to the Notification Server, selecting a task server, and running tasks before Windows setup / MiniSetup is complete. The issue is more pronounced in MP1 most likely due to improved performance in the Symantec Management Agent communication to the Notification Server.
Development has made a change to the 'configservice.exe' file. The 'configservice.exe' file now starts the Symantec Management Agent after Windows setup is complete.
Follow the steps below to install the fix:
Note: There are multiple methods to install / use this fix. Each method can be used independent ot the other methods.
1. Update an Existing Captured Image:
2. Update the 'source' machine before creating an image:
3. Deploy using a 'copy file to' task:
Note: There are multiple methods to install / use this fix. Each method can be used independent ot the other methods.
1. Update an Existing Captured Image:
2. Update the 'source' machine before creating the image:
3. Deploy using a 'copy file to' task:
Applies To
All builds of DS 7.1 up to SP2 MP1