Quantcast
Channel: Ivanti User Community : Document List - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 639

Issue: Configure target OS (CTOS) action fails after reboot

$
0
0

Applies to LDMS 9.0 and LDMS 9.5

 

Issue

Devices get to the Configure Target OS (CTOS) action, they reboot into Windows, but provisioning fails to continue.

 

Provisioning.log would show the following:

/Provisioning/windows/ProvisionGUI.exe)

2013-11-12 14:15:12(1300-1876) ldProvision.exe:Process exit code:2

2013-11-12 14:15:12(1300-1876) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\provcomm.dll" http://LDMS/LdLogon/Provisioning/windows/provcomm.dll)

2013-11-12 14:15:33(1300-1876) ldProvision.exe:Process exit code:2

2013-11-12 14:15:33(1300-1876) ldProvision.exe:download prerequisite files OK

2013-11-12 14:15:33(1300-1876) ldProvision.exe:Unable to load action configuration file; using default action configuration

2013-11-12 14:15:33(1300-1876) ldProvision.exe:Running in Daemon mode.

2013-11-12 14:15:33(1300-1876) ldProvision.exe:Provision Mode = PROVISION_MODE_CORE_SID

2013-11-12 14:15:48(1300-1876) ldProvision.exe:Start TryallWebService Attempt:0.

2013-11-12 14:16:09(1300-1876) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:2

2013-11-12 14:16:21(1300-1876) ldProvision.exe:Start TryallWebService Attempt:1.

2013-11-12 14:16:43(1300-1876) ldProvision.exe:End TryallWebService Attempt:1. ExitCode:2

2013-11-12 14:16:56(1300-1876) ldProvision.exe:Start TryallWebService Attempt:2.

2013-11-12 14:17:17(1300-1876) ldProvision.exe:End TryallWebService Attempt:2. ExitCode:2

2013-11-12 14:17:31(1300-1876) ldProvision.exe:Failed to call web service. exitCode=2

2013-11-12 14:17:31(1300-1876) ldProvision.exe:Caught exception in main: code=80001500H, file=.\ProvisioningWebSvc.cpp, line=933


Cause

httpclient is not able to resolve the Core name

 

Resolution

Edit the boot.wim file and look for file corename.txt (it should be in the \temp folder).

Edit that file and replace the hostname by FQDN

Commit the change and try again.

 

 

See also Troubleshooting Configure Target OS action in Provisioning Template.


Viewing all articles
Browse latest Browse all 639

Trending Articles



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