MDT 2012 asks for product key during deployment of XP
-
Monday, July 30, 2012 2:45 PM
When setting up the task sequence to deploy Windows XP, I specified the OEM CD Key I use to use with MDT 2010. I am using Dell OEM media on Dell Hardware with a Dell OEM Key. I can enter the key when prompted during the deployment, but it will not automatically be used during the deployment.
Mark
All Replies
-
Monday, July 30, 2012 3:43 PM
Hi,
OEM key is individual to each computer, even if you manage to automate the setup with only one key, that's not what you're suppose to do. If you want to use only one key, then it has to be a volume licence key (VLK).
David Sebban | Nelite North America | http://www.nelite.com/community/b/dsebban/default.aspx
- Proposed As Answer by Jean-Lou Piermé Thursday, August 23, 2012 1:16 PM
- Unproposed As Answer by Jean-Lou Piermé Thursday, August 23, 2012 1:16 PM
-
Monday, July 30, 2012 10:31 PM
It's possible to do this, you should verify your unattend.txt file and check the productkey setting. This can accept an OEM key, however this is not a generally supported method to install Windows XP.
The only case I can imagine using this kind of OEM key provisioning would be if you're installing XP using the setup and at the end of the process run sysprep again to delete the productkey (windows doesn't need to activate first). And then upon next boot the user would be prompted to enter the OEM key printed on the CoA sticker.
If the number of XP clients is really low, you could make use of the MDT DB and populate the information for each individual machine along with the product key it should use. I doubt it's worth the trouble though.
You'll need to double check your licensing if you're going to be using the OEM key(s) though.
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT -
Wednesday, August 01, 2012 3:12 PMIf I used OEM media to create my reference machine. Is there anyway to switch to Volume licensing media? Or do I need to rebuild my reference system? This would go for both XP and WIN7.
Mark
-
Wednesday, August 01, 2012 3:39 PMI believe you would need to recreate your ref image from a support standpoint, It might be technically possible to keep the same image but I wouldn't recommend it :)
David Sebban | Nelite North America | http://www.nelite.com/community/b/dsebban/default.aspx
- Edited by David SebbanMVP Wednesday, August 01, 2012 3:39 PM
-
Wednesday, August 01, 2012 4:16 PMMy organization has a volume license download and product key for XP. Can I use this and deploy to desktops that have an OEM sticker on them for XP?
Mark
-
Wednesday, August 01, 2012 4:38 PM
Hi Mark,
You'll need to recreate the images for Windows XP, since you can't activate an OEM version of Windows XP with a VL key. This however does not matter for Windows 7.
You can use any Windows 7 source OEM/Retail/TechNet/MSDN/VL and activate it with a product key matching the Windows Edition (e.g. Pro/Ult/Ent), so in your case you will not need to rebuild the Windows 7 images.
As for the licensing for Windows XP, yes you can use the Windows XP image from the Volume License Center and the product key for the OEM machines, you will not need to purchase additional licenses for these machines (assuming we're dealing with machines supplied with WinXP Pro OEM)
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT -
Wednesday, August 01, 2012 4:43 PM
My organization has a volume license download and product key for XP. Can I use this and deploy to desktops that have an OEM sticker on them for XP?
Mark
Volume License are upgrades (i'm not talking technically here) for OEM License, not only you can, but you have to install a VM on a machine that has been sold with an OEM licenceDavid Sebban | Nelite North America | http://www.nelite.com/community/b/dsebban/default.aspx
-
Wednesday, August 15, 2012 7:14 PMHave now created a new reference image using a volume media of Windows XP Pro SP3 as well as the Volume license key that went with it. During the creation of the task sequence, I used the volume license product key. The RED exclamation point did not go away, but it allowed me to pass. I copy and pasted the key too. Now, when I deploy to a physical machine. I am being prompted for a product key. An idea?
Mark
-
Thursday, August 16, 2012 5:51 PMhave you tested to use the key during a manual setup ?
David Sebban | Nelite North America | http://www.nelite.com/community/b/dsebban/default.aspx
-
Friday, August 17, 2012 2:03 PMYes, this is the same key I specified when creating the reference image. When I create a task sequence to capture XP, I omitted the product key and password. When I created the task sequence to deploy, I added the same product I used to create the image and password. When I run the deployment, I am prompted for the product key. I enter the product key, then it asks me for the password. So it seems the settings need to be done in the capture sequence rather than the deploy sequence? Seems backwards.
Mark
-
Friday, August 17, 2012 8:21 PM
If I used OEM media to create my reference machine. Is there anyway to switch to Volume licensing media? Or do I need to rebuild my reference system? This would go for both XP and WIN7.
Mark
Yes, there is a way for Windows XP and you need to edit i386\setupp.ini . However you still need a valid key.
http://www.mydigitallife.info/how-to-change-windows-xp-version-between-retail-oem-and-volume-license-channel/ -
Sunday, August 19, 2012 5:40 PM
Could you try if it makes a difference by providing your product key into the sysprep.inf file in addition to the unattend.txt (open the properties of the task sequence and open the last tab).
If that makes no difference, try the same as stated above, but instead in the task sequence that you use to capture the Windows XP installation.
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT- Marked As Answer by markfromit Monday, August 20, 2012 6:36 PM
-
Monday, August 20, 2012 2:32 PM
The product key is specified in both the sysprep.ini file and unattended.txt for the deployment task sequence.
If I add the product key for both sysprep.ini and unattended.txt for the capture sequence, will I need to recapture the reference virtual xp computer?
Mark
-
Monday, August 20, 2012 3:36 PM
Yes. Can't promise any results just trying to think of something you can test since I can't verify your scenario at the time being
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT -
Monday, August 20, 2012 4:08 PMI recreated the capture sequence with product key in both sysprep and unattend files. I will then recreate the deploy sequence, deploy it and post results.
Mark
-
Monday, August 20, 2012 6:37 PMAfter creating a new deploy task sequence with the new capture, I was able to deploy without being prompted with the product key.
Mark
-
Thursday, August 23, 2012 12:56 PM
If you open the captured Win XP image (wim file), you will see that in the root, there is a sysprep folder, if you remove this folder (in the wim file)
you will be able to put in the TS any product key an any config you want, the sysprep in the captured wim file will apply his config first
and not the one in the TS, so if in the TS you add a new admin password, it will not be applied if the sysprep folder still in the captured Windows XP wim file
- Edited by duber3 Thursday, August 23, 2012 1:07 PM
.png)
