Ghost Solution Suite

Hi,

I am moving your post to the Ghost Solution forum for greater visibility.

My suspicion is that this is a group policy setting rather than a build issue - especially since only some users are affected. This configuration is a registry key setting and Ghosting is not going to randomly change registry keys in this way.

Check out this MS article :

http://support.microsoft.com/kb/328010

Thank you EdT.  We are considering a group policy setting on the Domain to resolve that.  However, it would be interesting to know what is actually causing this.  We have compared our unattend.xml files and found them to be the same.  We even checked and found that incorporating the unattend.xml file into the configuration setting adds the same lines for processing.  It is just crazy that two of us don't encounter this and two of us do.  I contacted Symantec Tech Support to be told by the person that he thinks it is a microsoft problem (which it could be).  It just surprises me that a group policy would fail like this.  We moved to ghost console because of all the scripts we were having to run with ghost server.  I do appreciate your feedback.  We were hoping to gain a better understanding as to why this was happening.

Are these deployments being used with existing user profiles, or are new user profiles being created each time?  It could be something residual in an existing user profile.

Is the same logon used on all four machines?  If not, can you try using the same logon and see if that changes anything.

You could also try extracting the registry files from the image using Ghost explorer, and mounting them on an existing machine to verify the default policy setting in the image.

Finally, is there anything in the event logs to give additional clues as to what might be going on?