What does the LDprovision.log file in c:\ldprovision say about running the ProvisioningGUI.exe?
The only reference to "GUI" when searching the LDProvision.log is the very last line.
ldProvision.exe:Provision GUI still found alive, waiting.
In task manager is ldprovision.exe running? Just not the GUI is showing up?
Correct. LDProvision.exe is running, ProvisionGUI.exe is not.
Is this in WinPE or in Windows? If WinPE, did you just upgrade to LD2016? If yes, have you rebuilt your boot wims from scratch after the upgrade? I had a similar issue in WinPE, and pulling the clean wims from your core at %programfiles%\LANDesk\ManagementSuite\landesk\vboot\clean and re-injecting drivers (I used DISM instead of LD's driver import, and I'll continue doing that until they add entire folder adding capabilities) and packages, and have had no issues since.
This in Windows 7 (32 and 64) when we're onto the System Configuration steps in Provisioning.
It seems that the 2016 Provision GUI requires .NET FrameWork 4.0 to work. Bit of a pain to deploy to Windows 7!
I have figured out a workaround which seems to work ok, and doesn't require modification to your original .wim image files for those of us (like me) that like to keep them clean and device-agnostic.
Basically, I created a new modified unattend.xml and added a RunSynchronous item to the auditUser pass, before the Sysprep action, to install .NET Framework 4.6.1. Here is my modified auditUser section:
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Description>Microsoft .NET Framework 4.6.1</Description>
<Path>\\path\to\frmework\installer\NDP461-KB3102436-x86-x64-AllOS-ENU.exe /Q /NORESTART /ChainingPackage ADMINDEPLOYMENT</Path>
<Path>c:\windows\System32\sysprep\sysprep.exe /oobe /generalize /reboot</Path>
What is the difference between processing this in the unattend and adding the feature with dism? Wouldn't the .Net 4 be needed regardless of which image you're deploying?
Not trying to criticize, just trying to get perspective into your decision making process. I'm always looking to improve.
You can't add .NET 4.0/4.5.x/4.6.x to Windows 7 as a feature with DISM, that is the issue.
Gotcha. I wasn't aware, as we always install .NET in the reference computer prior to sysprep/capture.