Description
The Sysprep [GUIRunOnce] commands are conflicting or preventing Provisioning from running actions in the System Configuration stage.
LANDESK recommends NOT using the [GUIRunOnce] section.
Instead, LANDesk recommends adding each command that would be in the [GUIRunOnce] section as a Provisioning action.
Cause
The Sysprep file is configured to autologon in the [GUIUnattended] section:
[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=No
AutoLogon=Yes
AutoLogonCount=1
TimeZone=10
OemSkipRegional=1
OemSkipWelcome=1
The Sysprep file is also configured to run commands in the [GUIRunOnce] section. One of them may even be a reboot. This could occur if a Sysprep.inf created by an OS Deployment script was used or if the [GUIRunOnce] was populated manually.
[GuiRunOnce]
Command0="c:\ldsleep.exe 30"
Command1="net use \\ld87\ldlogon admin /u:Caldor\admin"
Command2="cmd /q /c \\ld87\ldlogon\wscfg32.exe /F /NOUI /REBOOT /DONTSTARTSVCS"
Command3="net use \\ld87\ldlogon /d /y"
The Provisioning actions and the [GUIRunOnce] commands will run at the same time and this may cause a conflict or interrupt that prevents the Provisioning actions from completing.
The Provisioning System Configuration actions are trying to start, but the [GUIRunOnce] commands are conflicting with the Provisioning process.
This is especially problematic if the [GUIRunOnce] section contains a reboot command.
Resolution
To resolve this issue, do the following:
Comment out (or remove) the following lines from the [GUIRunOnce]:
AutoLogon=Yes AutoLogonCount=1
The [GUIUnattended] section should now look as follows:[GuiUnattended] AdminPassword=* EncryptedAdminPassword=No ;AutoLogon=Yes ;AutoLogonCount=1 TimeZone=10 OemSkipRegional=1 OemSkipWelcome=1
Remove the entire [GUIRunOnce] section.
Create a Provisioning action under the System Configuration section of the Provisioning template for each of the needed commands in the [GUIRunOnce] section that were just deleted.