Quantcast
Channel: Ivanti User Community : All Content - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 1803

Provisioning on Windows 8 & 8.1 with an OEM license fails to continue after Configure Target OS action.

$
0
0

Description:


When provisioning a device with an OEM license provisioning doesn't continue after the reboot into windows.

 

Cause:


With Windows 8 and Windows 8.1 Microsoft made a change to the sysprep environment to improve the end user experience by skipping the SetupComplete.cmd section if an OEM license is detected. This allows the end user to get to the Welcome Screen faster. This is what causes provisioning to fail to start after the reboot.

 

To see if you are experiencing this issue look in C:\Windows\Panther\UnattendGC\Setupact.log after you have booted into windows and provisioning doesn't continue.

You should find this line.

 

[msoobe.exe] OEM license detected, will not run SetupComplete.cmd

 

 


Resolution:


To resolve this you need to add a First Logon Command to your unattend file. It should look like this.

<FirstLogonCommands>

                <SynchronousCommand wcm:action="add">

                    <Order>1</Order>

                    <CommandLine>C:\Windows\Setup\Scripts\SetupComplete.cmd</CommandLine>

                    <RequiresUserInput>false</RequiresUserInput>

                </SynchronousCommand>

</FirstLogonCommands>

If the SetupComplete.cmd file is not there, you can create your own file or script to inject to reference.

 

SetupComplete.cmd needs to have this command:

C:\ldprovisioning\ldprovisioning.cmd

 

An addition, change the following path to match your new file location:

<CommandLine>C:\Windows\Setup\Scripts\SetupComplete.cmd</CommandLine>

 




Viewing all articles
Browse latest Browse all 1803

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>