Windows 7 License Not Being Applied In OSD Task Sequence
Hello,
We have a mature OSD environment that has been working without issue for many months. Our VL MAK key for Windows 7 Enterprise recently changed so we updated each of the task sequences to reflect this. However since then, the MAK key isnt being applied to
newly imaged systems and the key is 100% correct because we can activate through the GUI upon boot.
We've looked through the local SMSTS.log file and found nothing pertaining to the license activation failing so we're at abit of a loose end, not sure why it would all of a sudden just stop working?
Any help would be greatly appreciated.
Thanks,
August 27th, 2015 5:22am
What command are you using to activate the devices and does that command work when you run it manually on the system.
TBH Scott why are you not using KMS in your environment and activating that way?
August 27th, 2015 5:59am
Hi Paul,
We aren't using a command to apply to license, its part of the Apply Windows Settings which then asks for a Username, Organisation Name etc. See below.
It has always just worked but since changing the product key to our new volume license MAK, the license isn't being applied as part of the task sequence.
August 27th, 2015 6:46am
If you run SLMGR.VBS -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx post OSD does that activate the client correctly?
August 27th, 2015 8:59am
Hi Paul,
Thanks for the reply but SLMGR.vbs isn't supported on our operating systems, Windows 7 and Server 2008 R2
https://technet.microsoft.com/en-us/library/dn502540.aspx?f=255&MSPPError=-2147217396
August 27th, 2015 9:50am
This is working ever since windows vista.
You need to read the article you posted
Because of WMI changes in Windows 7 and Windows Server 2008 R2, the Slmgr.vbs script is not intended to work across platforms.
Using Slmgr.vbs to manage a Windows 7 or Windows Server 2008 R2 system from the Windows Vista operating system is not supported. Attempting to manage an older system from Windows 7 or Windows Server 2008 R2 will generate
a specific version mismatch error. For example, running cscript slmgr.vbs <vista_machine_name> /dlv produces the following output:
log on the windows 7 you created and run what Paul ask.
http://windowsitpro.com/windows/control-your-licensing-slmgr
-
Edited by
Frederick Dicaire
17 hours 55 minutes ago
August 27th, 2015 9:55am
This is working ever since windows vista.
You need to read the article you posted
Because of WMI changes in Windows 7 and Windows Server 2008 R2, the Slmgr.vbs script is not intended to work across platforms.
Using Slmgr.vbs to manage a Windows 7 or Windows Server 2008 R2 system from the Windows Vista operating system is not supported. Attempting to manage an older system from Windows 7 or Windows Server 2008 R2 will generate
a specific version mismatch error. For example, running cscript slmgr.vbs <vista_machine_name> /dlv produces the following output:
log on the windows 7 you created and run what Paul ask.
http://windowsitpro.com/windows/control-your-licensing-slmgr
-
Edited by
Frederick Dicaire
Thursday, August 27, 2015 1:54 PM
-
Proposed as answer by
Joyce LMicrosoft contingent staff, Moderator
Tuesday, September 08, 2015 7:17 AM
-
Marked as answer by
Joyce LMicrosoft contingent staff, Moderator
Wednesday, September 09, 2015 5:26 AM
-
Unmarked as answer by
Scott2015
21 hours 50 minutes ago
-
Unproposed as answer by
Scott2015
21 hours 37 minutes ago
August 27th, 2015 1:54pm
This is working ever since windows vista.
You need to read the article you posted
Because of WMI changes in Windows 7 and Windows Server 2008 R2, the Slmgr.vbs script is not intended to work across platforms.
Using Slmgr.vbs to manage a Windows 7 or Windows Server 2008 R2 system from the Windows Vista operating system is not supported. Attempting to manage an older system from Windows 7 or Windows Server 2008 R2 will generate
a specific version mismatch error. For example, running cscript slmgr.vbs <vista_machine_name> /dlv produces the following output:
log on the windows 7 you created and run what Paul ask.
http://windowsitpro.com/windows/control-your-licensing-slmgr
-
Edited by
Frederick Dicaire
Thursday, August 27, 2015 1:54 PM
-
Proposed as answer by
Joyce LMicrosoft contingent staff, Moderator
Tuesday, September 08, 2015 7:17 AM
-
Marked as answer by
Joyce LMicrosoft contingent staff, Moderator
Wednesday, September 09, 2015 5:26 AM
-
Unmarked as answer by
Scott2015
Wednesday, September 09, 2015 9:53 AM
-
Unproposed as answer by
Scott2015
Wednesday, September 09, 2015 10:06 AM
August 27th, 2015 1:54pm
Sorry for the late responce.
I can confirm that running
SLMGR.VBS -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx from elevated CMD post OSD deployment doesn't activate the license. I get the following error;
Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid
I know for definite that the key is correct because if we try to activate manually with the same MAK, activation is successful.
September 9th, 2015 6:06am
I would still double check you are using the correct MAK. If slmgr -ipk returns an error, then that is the issue.
Jeff
September 9th, 2015 6:59am
200% certain that its the correct MAK.
September 10th, 2015 8:52am
check the report or log to review what error is coming during this step.
September 10th, 2015 4:19pm
I concur with Jeff there, if slmgr -ipk returns an error about the key being wrong, then it is wrong.
September 11th, 2015 3:38am
Hi Scott
With regards to the licence key issue, if you have a volume licensing agreement I would recommend you consider using a KMS server and apply a KMS key (available in your Microsoft volume licensing)
KMS is incredibly easy to setup, it publishes in DNS and your Windows 7 machines would then automatically activate against the KMS server.
This is a much simpler and much more manageable solution that embedding keys in task sequences.
September 11th, 2015 6:03am