SYSPREP - XML answer file in windows 7-32 bit

Install the Windows Automated Installation Kit (WAIK).  Use the System Image Manager to build an answer file.  In it you will select this component (Microsoft-Windows-Security-SPP) and add the SkipRearm setting.

However, IMO the better option is to create an image that hasn't already been rearmed 3 times.

Sorry, not sure about disabling the NIC.

Not able to use WAIK since my image file is not in *.wim or *.clg, I added sysprep as last step to win 7 image. So, all I need is to have an un*.xml file to reset rearm, disable NIC,
Generalize, shutdown.
Thanks

Are you saying that you don't have a Windows install disk?  You can use the .WIM file from that.  It really is the best way to generate the answer file.  Syntax will be different depending on whether you're creating an answer file for a x86 or x64 image.  Can't remember if it also takes into account the Windows edition.

I believe you have created an image with a third party software such as Acronis, Ghost etc. You can deploy the image that you have created onto a HDD then without starting the computer, remove the HDD and attach to you techy cmputer. Navigate, find and edit your sysprep answer file under \Windows\System32\Sysprep. Then re attach this HDD to your sample computer and start with your image creator software and create your editted master image. That's it! :) Any questions please feel free to ask.

Navigate, find and edit your sysprep answer file, Well, i am looking in "HOW" to make the answer file. Please read the 1st post.

Thanks

I'll ask again, are you saying that you don't have a Windows install disk anywhere?

Yes, I have windows 7 32-bit installation disk.

Well then, you've got everything you need to create an answer file with the WAIK.

Thank you teomcam for your detailed comment. It was great ....!
I used Windows Embedded to build my base image. If I use "SkipRearm" to reset to zero would it also reset the windows activation. Because, right now the image is already activated, would users need to reactivate after 30 days or…..60 days. IF that's the case, then it would not be a proper way to reset Rearm as I need to keep the licensing as in my base image unchanged. I just need to
Avoid the fatal error occurred while trying to Sysprep the image. I do not want to have any licensing issue after deploy the image to all the PCs.

Thanks for the advice.

Hi,

Unfrotunately sysprep always resets the Windows Activation. After sysprep all clients will need to be reactivated. if you have KMS server in your environment no problem but if you don't have then  you need to activate them one by one. If you don't have KMS server you may install on your highest version of server. But to have KMS server you must have at least 25 clients!

""Unfrotunately sysprep always resets the Windows Activation""

Correct me if I am wrong, but I run SYSprep at the last step for windows 7 image. So That, once the image has been restore, a mini setup will run to seal the configuration ( MAC address, user name,…..SID….etc)
When Imaging is completed, I change the time of the PC to next year, I reboot and still my windows is activated and "windows is genuine"!!

2nd) I am getting  fatal error  after running Sysprep for the 3rd time and the work around is here:
http://support.microsoft.com/kb/929828

I f I do this ( Rearming) would change anything to the "Windows is genuine"  after image has been restore?

I found the Answer to my Question at the following link:

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/d54b34fa-f542-4b98-88da-13ffe7df16a4/

Any comments

Every time you run sysprep /generalize, the activation clock is reset (rearmed) unless you include the SkipRearm setting and set it to "1".  See this link:
http://technet.microsoft.com/en-us/library/ff716063

Although you can run sysprep pretty much an unlimited number of times on a machine, the activation clock can only be reset 3 times.  You can even reset the licensing status (and the 30 day grace period before activation is required) manually with the command "slmgr.vbs /rearm".  The behavior of generalizing can change depending on what type of key you have installed.  See http://technet.microsoft.com/en-us/library/dd744512(WS.10).aspx
 - If you have activated with a retail key, generalize will clear activation status and the product key whether you use the SkipRearm setting or not.
 - If you have activated with a KMS key, you can reactivate as much as you want (if you understand KMS activation you can see why).
 - If you have activated with a MAK key, product key will remain but activation clock is reset and will have to reactivate OS.  If you use SkipRearm, product will remain activated.
 - If you have an OEM key, pretty much no effect since it doesn't require activation.
 
You have already run into this limit which is why you are getting the error.  As I said earlier, best option is to build a new image which you can then sysprep without running into the rearm count limit.

full guide