Might sound a daft question but does sysprep reset the GUID of a install?
Thanks

Might sound a daft question but does sysprep reset the GUID of a install?
Thanks
Found this:
here: WinXP activation, sysprep, open license, retail license - Windows XP SetupSysprep allows you to
install software and make other changes on a single computer system for
mass duplication to other computer systems without creating GUIDs...And
if you accidently create a GUID, it will reset it up to 3 times before
it will not reset it again.
not sure if that helps at all..
EDIT: on second thoughts the poster may be refering to SIDS
Last edited by Crispin; 2nd March 2009 at 10:50 PM.

The GUID is generally hard-coded into the NIC/mainboard and cannot be changed (at least not without software specific to the system). By using this GUID (which should be unique to each machine) when a network is joined, the computers should all play nice.
Associated with the whole networking-side is the SID which is generated when the machine is installed with Windows. This is a software thing that needs to be reset if you image a machine - SYSPREP does this by default (although you can tell it not to).
A little more on the difference can be seen at windows server active_directory Difference Between ObjectSID & objectGUID

This is the GUID i am talking about Configuring Symantec AntiVirus for deployment as part of a drive image


From reading your link, they are definitely two separate things. Sysprep focuses just on Windows; so that guide tells you how to prepare the image for Symantec before running Sysprep.
In my experience, deploying Anti-Virus or any type of security software as part of an image is a no-no. I remember the last time I tried it with Sophos. Absolute disaster. It was a lot quicker to deploy it to all new machines on the network through the Management Console.
There are currently 1 users browsing this thread. (0 members and 1 guests)