[German]System administrators who tries to upgrade Windows 7 machines to Windows 10 via SCCM need to be careful. Upgrading OEM machines fails because SetupComplete.cmd cannot run.
Advertising
Another brief information for administrators in enterprises using OEM machines with Windows 7. If not done, in 2019 a migration to Windows 10 has to take place, and if no new hardware is purchased, the switch will be made by upgrading the Windows 7 systems.
Caution with SCCM and OEM machines
" src="https://vg02.met.vgwort.de/na/f2da51240e6e4d8692d13ae81a1bb629" width="1" height="1">I''m not active in this area, and this may isn't new to you. But I just post the information – maybe it will helpful for someone. The days I stumbled over this tweet.
A customer wanted to upgrade their Win7 Pro to Win10 Ent using #SCCM IPU TS. This failed, because Win7 had OEM license and SetupComplete.cmd is not run. I don't understand why SKU has any effect whether SetupComplete is run or not. https://t.co/GY5kZEYiao pic.twitter.com/err5doAtI6
— Panu Saukko (@panusaukko) 3. Mai 2019
Panu Saukko tried to upgrade Windows 7 Pro machines to Windows 10 using System Center Configuration Manager (SCCM). This approach has been described here. But since they were OEM machines, this upgrade failed with an error because the batch file SetupComplete.cmd could not run after the upgrade. The log file contains the hint:
Client OS edition and OEM license detected and no enterprise edition detected, will not run SetupComplete.cmd
Not allowed to run the SetupComplete.cmd, will not run SetupComplete.cmd
The SetupComplete.cmd batch file is usually run after the user displays the desktop. According to this document, this setting is disabled when OEM product keys are used. This reddit thread also indicates that OEM machines cannot be upgraded because of the license key.
Advertising
This article outlines, for example, how to perform an error diagnosis. Panu Saukko is not alone, because another user has reported to his tweet. What else can go wrong with OEM machines, e.g. regarding drivers, is described here – just to mention.
That's by design
On Panu Saukko's tweet, Microsoft employee Michael Niehaus contacted Microsoft and wrote that this was intended and by design.
That is a limitation – it was implemented that way to keep OEMs from leveraging that mechanism – it's only available with VL SKUs.
— Michael Niehaus (@mniehaus) 3. Mai 2019
Just provide a VL key during upgrade
Panu Saukko referred in the above tweet to a Microsoft support article Configuration Manager Client left in Provisioning Mode after upgrade to Windows 10. There is also the hint that the Configuration Manager client will remain in Provisioning Mode after a successful upgrade if OEM keys are used. The solution indicated within the article was simple: Just use only volume license or retail product keys for the operating system upgrade. In this blog post, someone has dealt with a similar case.
If you include the KMS key in Upgrade OS step, does it overcome this? Is this related to the key being embedded into the device?
— Adam Gross (ASquareDozen.com) (@AdamGrossTX) 4. Mai 2019
In the tweet above, Panu Saukko also confirms that this approach works. Maybe someone will help.
Advertising
