Regfix and Zenworks imaging

[PhoneTeck]

We have a computer lab that runs Windows Xp and a Base image has already been put on them. The base image is setup with the computer name like this C-XX-XXX-XXXX and then we run regfix. After a reboot we login to administrator and run sysprep. Ok after every machine in the lab is completley setup with entering in the serial number etc. so every machine has a unique sid and changing the computer names, then the machines are ready to go. My question is, if you create another image similiar and then use zenworks again to image them on the next image should you skip running sysprep, does zenworks keep the sid that was created from the previous image. I also noticed that on the second image I put on these machines in which I didnt run sysprep, Zenworks runs its configuration utility after the machine has been imaged and does a reboot and it keeps the computer name that was configured from last, but if you dont go into administrator and run regfix with the computer name that it kept, then when you try to login with a user it brings up a window that says default and asks for a password is there anyway around this so when we image are machines we dont have to run the regfix again if a previous image has been put on them, I hope this all makes since, It makes since in my mind, if anyone needs any clarification let me know.

 

[terry712]

you dont need to sysprep or sid them or anything like taht

when you squirt the image down it will run ziswin and so it all for you

 

[PhoneTeck]

If we didnt run sysprep on the image, then when we image all of the computers for the first time they all will have the same sid, the sids need to be different on all of the computers.

 

[Provogeek]

the sid only really matters if yo uhave a domain.

However, your doing it the hardway with to many fat finger mistakes possible (and lazy mistakes as well).

It is true that you MUST run Sysprep after imaging a system (this is true with all imaging software), not for the SID, but for the stupid license key. Unless your an enterpeise customer, you have OEM version of WinXP. So you only have OEM versions of the OS key, a key that requires activation (enterprise licenses do not require activation). So you need to use the key provided with the computer to be in compliance with M$ licensing.

There are ways around this, but it's called hacking so I won't go into it here so don't ask, and requires the use of the manufacture OS cd, a partial install of XP, and a DOS based NTFS reader program ... hint hint nudge nudge.

Now, you should run sysprep prior to creating your image so it runs on boot, and write up some scripts to automate the setup. You can configure the system to auto login and run what ever config apps you wish, and pause it for input were ever you wish. I like to use ZNCLite for workstation naming, many options are avilable, there is also another with more features in it (don't remember the name though). You will always have a little pause in the script when ziswin runs, but only for systems that were already imaged.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com