Windows 7 Activated before sysprep, is this ok?

[link470]

Hi everyone,

 

I've just finished creating an image for a small set of office computers [Windows 7 Pro 64-bit]. The image is very clean, and my sysprep script has skiprearm to 1, and also has 2 scripts that run after the image is deployed. One script sets the product key, and the other script activates it. Anyway, this works great. I captured the image, restarted the reference computer [which would be one of the office computers], and made sure sysprep ran correctly, which it did.

 

However, since sysprep ran correctly, the product key was applied and the machine was activated. Normally, this is great. But I then wanted to add Adobe Reader [cause I forgot to add it to the image like an idiot], and change one other thing with the wallpaper image. Great, did that. Cleaned up again, and ran sysprep using the same unattend.xml. Captured image.

 

When I restarted this time, again, everything went according to plan. But I didn't see the two cscript windows appear the first time I logged in as administrator. I checked Computer Properties though, and it said Windows is Activated. I also checked the event viewer though, and I see one of these: "Installation of the Proof of Purchase failed. 0xC004F050".

 

Only once, at the beginning. The machine seems to be running fine, I'm on it right now typing this. However, it hasn't been on for more than 45 minutes or so, and I've seen some weird things while Googling the above event that say the computer could randomly blue screen after 3 hours and that sort of thing. I just wanted to check with you guys, do you think I'm ok to push this image out to the other few office computers? Or is it safer to scrap it and start again with windows not activated? Or should I just reapply the product key and activate again? Everything seems to work beautifully, just want to be safe.

 

Any thoughts greatly appreciated, thanks in advance!

Edited April 2, 2014 by link470

[free780]

Bad idea to capture a activated image. Also things like Adobe reader update so often, theres not much point putting them in an image. After a capture. I blank the vm.

[FN-GM]

There is no point. Sysprep will clear any activation anyway.

[link470]

There is no point. Sysprep will clear any activation anyway.

Right, but I have SkipRearm set to 1, is that still ok to deploy this image? I was curious because I deployed the image to a second computer as a test, and after imagex ran, I unplugged the ethernet cable and restarted the computer. The machine still said "Windows is Activated" once setup completed and I was logged in, but couldn't possibly have contacted Microsoft to activate on a MAK key while the ethernet cable was unplugged. I then installed MSE though, and it didn't complain about windows being non genuine. So I don't know.

[FN-GM]

Why would you do this? Why not just setup a KMS server?

[link470]

Why would you do this? Why not just setup a KMS server?

 

It's for less than 10 computers. I'm just hoping to get these images pushed out and activated. Just need to know whether or not this image would be safe to use or not.

[snagrat]

Yes safe to use but will need to be activated again when deployed

[link470]

Yes safe to use but will need to be activated again when deployed

Even with the SkipRearm=1 set? I thought it would need to be reactivated too, which was why I ended up pulling the ethernet cable after copying the image to the second computer I tested. But when it boot up for the second time after completing setup during the first boot, it appeared activated when I logged in as a local admin. The machine never contacted the internet from the time imagex copied the image to the time I was looking at the Computer Properties window showing Windows is Activated.

[link470]

I opted for just building the image again, only took me a few hours.

[stevenlong1985]

For next time add this into your Windows AIK unatted.xml file.

 

THIS Automatically Activates the Machine with your VL / MAK Key

 

 

 

4. Specialize

 

amd64_Microsoft-Windows-Security-SPP-UX_6.1.7600.16385_neutral

 

SkipAutoActivation> true

 

7. OobeSystem

 

amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral

 

AutoLogon

 

Enabled> true

LogonCount>2

Username> administrator

 

Password> {Administrator Password}

 

FirstLogonCommands

 

SynchronousCommand[Order=1]

 

CommandLine = cscript //b c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (Windows 7 VL / MAK key)

Order 1

RequiresUserInput> false

 

SynchronousCommand[Order=2]

 

CommandLine = cscript //b c:\windows\system32\slmgr.vbs /ato

Order 2

RequiresUserInput = false