This may be nothing to do with your Config Manager environment.

I assume your using KMS keys to manage your Windows OS licensing. Have you confirmed that your KMS server is working correctly?

You would normally only need to enter additional steps in your TS re: activation if you were using a MAK type key (as KMS server would automatically activate the OS upon first restart following OSD provisioning).

Cheers

Damon

• Proposed as answer by Narcoticoo Saturday, May 23, 2015 6:07 AM

This may be nothing to do with your Config Manager environment.

I assume your using KMS keys to manage your Windows OS licensing. Have you confirmed that your KMS server is working correctly?

You would normally only need to enter additional steps in your TS re: activation if you were using a MAK type key (as KMS server would automatically activate the OS upon first restart following OSD provisioning).

Cheers

Damon

• Proposed as answer by Narcoticoo Saturday, May 23, 2015 6:07 AM

All of a sudden we started getting prompted to activate windows " Hardware or driver change requires windows to reactivate"

Never seen this before but getting the above Windows Activation request after the OSD and when user logs in

Tried adding c:\Windows\System32\SLMGR.vbs /ato

Task sequence errors out, anyone has any ideas?

I would start by adding cscript in front of your current command line. Also, what's the exact error that you're seeing?

We are not using Kmart, we are using mak key, but we did activation of windows when image was captured.

Sorry auto correction, meant to say KMS

We are not using KMS, we are using mak key, but we did activation of windows when image was captured.

That's where you went wrong. You must not activate Windows prior to capture. If you do activate, you must rearm prior to capture. It's better not to activate prior to capture..

I'm not 100% on this but I'm fairly certain that running sysprep will re-arm the licensing state of your source image before it is captured. Either way I'm sure that you can't activate your custom wim file and then deploy it out to workstations. Each workstation must activate individually against Microsoft's licensing servers when using a MAK key.

You will have to add some steps to your Task Sequence like this:

cscript c:\Windows\System32\slmgr.vbs -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

cscript c:\Windows\System32\slmgr.vbs -ato

Also consider Internet Access as it will be required during the Task Sequence. Pop the steps at the end. If your behind a proxy then you may need to set a machine proxy using the following command:

netsh winhttp set proxy %yourproxy%:portnumber

then run a step after the activation which resets the proxy.

netsh winhttp reset proxy

Cheers

Damon

• Edited by Damon A. Johns 5 hours 17 minutes ago

Hi,

Concur with the others. And you can also active windows during installation by using unattended files.

ProductKey

https://technet.microsoft.com/en-us/library/cc721925%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

This may be nothing to do with your Config Manager environment.

I assume your using KMS keys to manage your Windows OS licensing. Have you confirmed that your KMS server is working correctly?

You would normally only need to enter additional steps in your TS re: activation if you were using a MAK type key (as KMS server would automatically activate the OS upon first restart following OSD provisioning).

Cheers

Damon

• Proposed as answer by Narcoticoo 1 hour 39 minutes ago

I'm not 100% on this but I'm fairly certain that running sysprep will re-arm the licensing state of your source image before it is captured. Either way I'm sure that you can't activate your custom wim file and then deploy it out to workstations. Each workstation must activate individually against Microsoft's licensing servers when using a MAK key.

You will have to add some steps to your Task Sequence like this:

cscript c:\Windows\System32\slmgr.vbs -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

cscript c:\Windows\System32\slmgr.vbs -ato

Also consider Internet Access as it will be required during the Task Sequence. Pop the steps at the end. If your behind a proxy then you may need to set a machine proxy using the following command:

netsh winhttp set proxy %yourproxy%:portnumber

then run a step after the activation which resets the proxy.

netsh winhttp reset proxy

Cheers

Damon

• Edited by Damon A. Johns Sunday, May 24, 2015 2:27 AM

I'm not 100% on this but I'm fairly certain that running sysprep will re-arm the licensing state of your source image before it is captured. Either way I'm sure that you can't activate your custom wim file and then deploy it out to workstations. Each workstation must activate individually against Microsoft's licensing servers when using a MAK key.

You will have to add some steps to your Task Sequence like this:

cscript c:\Windows\System32\slmgr.vbs -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

cscript c:\Windows\System32\slmgr.vbs -ato

Also consider Internet Access as it will be required during the Task Sequence. Pop the steps at the end. If your behind a proxy then you may need to set a machine proxy using the following command:

netsh winhttp set proxy %yourproxy%:portnumber

then run a step after the activation which resets the proxy.

netsh winhttp reset proxy

Cheers

Damon

• Edited by Damon A. Johns Sunday, May 24, 2015 2:27 AM

Io appreciate prompt response, defensively have something to try. Although I did try slmgr.vbs /ato and task sequence failed, did not like the command

I want to try what you suggested Damon set the firewall, and it is turned on I see that in control panel\firewall, but how to find firewall name, its not in internet options.

I will post some screen shots of how were activating our Windows 7 builds tomorrow.

I'm not sure what your referring to with regards to the firewall, control panels and internet options.

Regards

Damon

Here you go:

• Edited by Damon A. Johns 5 hours 3 minutes ago

Here you go:

• Edited by Damon A. Johns Friday, May 29, 2015 2:44 AM