We are seeing all of our images fail like clockwork at the "Install Provisioning Agent" action with a return error code of 1603 (MSG_ERROR_INSTALL_FAILURE). I've turned on logging, and sure enough it's all going pear shaped during that action.
From the ldprovision log I can cull the following information:
2014-10-13 19:53:09(2788-2792) ldProvision.exe:********* Begin an action - Configure_agent
2014-10-13 19:53:09(2788-2792) ldProvision.exe:Do EnvironmentCheck
2014-10-13 19:53:09(2788-2792) ldProvision.exe:Is WinPE Action=0, Is WinPe Environment=0
2014-10-13 19:53:09(2788-2792) ldProvision.exe:Report might reboot status to core.
2014-10-13 19:53:09(2788-2792) ldProvision.exe:Call web service SetActionStatus()
2014-10-13 19:53:09(2788-2792) ldProvision.exe:Start TryallWebService Attempt:0.
2014-10-13 19:53:10(2788-2792) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0
2014-10-13 19:53:10(2788-2792) ldProvision.exe:Session Data: <variables/>
2014-10-13 19:53:10(2788-2792) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args ( -f "C:\ldprovisioning\ConfigHandler.exe" http://<CORE>/LdLogon/Provisioning/windows/ConfigHandler.exe)
2014-10-13 19:53:12(2788-2792) ldProvision.exe:Process exit code:0
2014-10-13 19:53:12(2788-2792) ldProvision.exe:The file (C:\ldprovisioning\ConfigHandler.exe) was successfully downloaded
2014-10-13 19:53:12(2788-2792) ldProvision.exe:Download handler ok.
2014-10-13 19:53:12(2788-2792) ldProvision.exe:Launching action handler [ConfigHandler.exe] with parameters ["]
2014-10-13 19:53:12(2788-2792) ldProvision.exe:handler launched.
2014-10-13 20:00:05(2788-2792) ldProvision.exe:Reporting action status: 5 to core
2014-10-13 20:00:05(2788-2792) ldProvision.exe:Call web service GetStatusString()
2014-10-13 20:00:05(2788-2792) ldProvision.exe:Start TryallWebService Attempt:0.
2014-10-13 20:00:05(2788-2792) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0
2014-10-13 20:00:05(2788-2792) ldProvision.exe:StatusString = The action failed.
2014-10-13 20:00:05(2788-2792) ldProvision.exe:Call web service SetActionStatus()
2014-10-13 20:00:05(2788-2792) ldProvision.exe:Start TryallWebService Attempt:0.
2014-10-13 20:00:06(2788-2792) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0
2014-10-13 20:00:06(2788-2792) ldProvision.exe:End of action - Configure_agent
2014-10-13 20:00:06(2788-2792) ldProvision.exe:Last action failed
2014-10-13 20:00:06(2788-2792) ldProvision.exe:********************************** End processing actions **********************************
2014-10-13 20:00:06(2788-2792) ldProvision.exe:ldProvision ended
I followed the thread to the ConfigHandler log, which tells me pretty much the same thing.
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Got core name: <CORE>
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Got config tool: wscfg32.exe
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Got configuration file: Windows Provisioning Agent
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Got user: <CORE>\ldadmin
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:password is not variable, encrypted
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Mapping Drive
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Going to connect
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Going to decrypt password
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:going to try and connect to [] \\<CORE>\ldlogon with <DOMAIN>\ldadmin
2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:going to execute \\<CORE>\ldlogon\wscfg32.exe /f /L /NOUI /NOREBOOT /C="Windows Provisioning Agent.ini"
2014-10-13 20:00:05(1756-3056) ConfigHandler.exe:system() return 1603
I can ping the CORE from this machine after it fails, but I understand that using the FQDN is best practice. Based on the logs, it's not using the FQDN. Could this be the source of the problem, and if so where should I make the change? I've been through the Provisioning template and can't see any point where I only have the CORE listed. The same goes for the Windows Provisioning Agent. I've also rebuilt the agents, to no effect.
Any ideas?