I created an unattend.xml with embedded product key, and skiprearm 1 command following the info in this thread, but after I reboot from running the sysprep command from your Method 3, #CANNOT RESUME WINDOWS 10 SERIAL KEY AFTER DOWNLOAD PRO#I'm attempting to replicate your feat, with activated Win 7 Pro 64 OEM. But the problem is that using the generalize option resets the activation, forcing the customer to now activate Windows 7. When using the generalize option, it appears the oobe successfully uses the product key that's embedded in the unattend.xml. Kubilay Elmas MCITP (Enterprise Desktop Administrator Windows 7) Look at the following links for further information. Unattended Windows Setup Reference (Unattend.chm). For more information about this setting, see the Sysprep command multiple times without resetting the activation clock. SkipRearm setting in the Microsoft-Windows-Security-SPP component. You can bypass resetting the activation clock by using the When you run the sysprep /generalize command, the activation clock will automatically reset. Sysprep /generalize command, the clock can no longer be reset. Sysprep /generalize command to reset Windows Product Activation a maximum of three times. However, the clock for Windows Product Activation begins its countdown the first time Windows starts. There is no limit to the number of times that the Sysprep command can run on a computer. #CANNOT RESUME WINDOWS 10 SERIAL KEY AFTER DOWNLOAD INSTALL#When you install Windows with a single license product key, you have 30 days during which you must activate that installation of Windows. But the problem is that using the generalize option resets the activation, forcing the customer to now activate Windows 7.Īgain, I need a method that maintains activation, and does not ask for a product key during the OOBE. When using the generalize option, it appears the the oobe successfully uses the product key thats embedded in the unattend.xml. Method #3: sysprep /generalize /oobe /shutdown /unattend:unattend.xml I then read about using the generalize option. The unattend.xlm contains my product key, so the customer should not have to enter it? Apparently not, during the oobe, customer is still prompted for product key. Method #2: sysprep /oobe /shutdown /unattend:unattend.xml This would be fine except I do not want them to have to enter the product key. #CANNOT RESUME WINDOWS 10 SERIAL KEY AFTER DOWNLOAD WINDOWS 7#The problem is that I've tried mulitiple methods and neither do what I want.Ĭustomer has to re-enter the product key, and as long as it matches, Windows 7 remains activated. I do not want the end user to have to enter a product key or activate Windows when they obtain this machine. Then I run sysprep to prepare the machine for delivery. I want to enter the product key and activate Windows 7 prior to delivering. I go into audit mode on that machine to finalize any customizations that I'm an OEM and have a image that I've deployed to a customer machine. I've done a fair amount of searching and reading and cannot find a solution to what I'm attempting to do here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |