1 Reply Latest reply on Apr 4, 2018 10:39 AM by Aaron_Day

    provisioning actions are not retrieved and provisioning GUI is empty

    HermiM Apprentice

      Hi,

       

      I am running on weird situation I never saw before. The Windows PE is loaded successfully and the startnet.cmd script is running until it reaches the step "A subdirectory or file \ldprovision already exist". Normally the provisionin GUI should start now but it is not the case. It will take too much time (more than 10 minutes) before it is displayed and the problem is it shown no provisioning actions.

       

      I made a dummy template on which I have added just 1 provisioning action which is wait(xx). and I tried on the same device and I got the same behavior. I deleted the device and import it again and I am still seeing the same weird behavior.

      I don't think that it is a general problem since some other devices were able to finish successfully provisioning tasks!!

       

      From the core server I checked the follwing log files :

       

      provisioning.log

      VERBOSE ProvisioningWebService  3/12/2018 11:12:07 AM  : Identifiers to use - Mac Address: True, Serial Number: True, AMT GUID: True

      VERBOSE ProvisioningWebService  3/12/2018 11:12:07 AM  :  Identifiers:

      VERBOSE ProvisioningWebService  3/12/2018 11:12:07 AM  :   MACAddress: XXXXXXXXXXXX

      VERBOSE ProvisioningWebService  3/12/2018 11:12:07 AM  :   SerialNumber: XXXXXXX

      VERBOSE ProvisioningWebService  3/12/2018 11:12:08 AM  : Returning task XML

      TemplateFinder.log

       

      DEBUGGING TemplateFinder  3/12/2018 11:12:07 AM  : GetProvisioningTaskForComputer.computerIdn 11334

      VERBOSE TemplateFinder  3/12/2018 11:12:07 AM  : info.taskId 7255.info.templateId 226

       

      ==> since it is the right task ID and the right template ID I presume that the provisioing task (with the provisioning action wait(xx) was successfully retrieved by the core server).

       

      From the client I can see that all prerequisite files were succesfully downloaded:

       

      ldprovision.log

       

      2018-03-12 20:12:28(1696-1704) ldProvision:Using [CORESERVER] for Core

      2018-03-12 20:12:28(1696-1704) ldProvision:Getting server identifiers

      2018-03-12 20:12:28(1696-1704) ldProvision:Getting BIOS Serial number by WMI.

      2018-03-12 20:12:28(1696-1704) ldProvision:Serial Number by WMI: XXXXXXX

      2018-03-12 20:12:28(1696-1704) ldProvision:Serial Number: XXXXXXX

      2018-03-12 20:12:28(1696-1704) ldProvision:ldProvision started

      2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)

      2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1

      2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)

      2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1

      2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)

      2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1

      2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)

      2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1

      2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "x:\CBA8\cbaroot\alert\provisioning.ruleset.xml" http://CORESERVER/LdLogon/alertrules/provisioning.ruleset.xml)

      2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:1

      2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\ldprovision_config.windows.xml" http://CORESERVER/LdLogon/Provisioning/windows/ldprovision_config.windows.xml)

      2018-03-12 20:12:28(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:28(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:28(1696-1704) ldProvision:The file (X:\ldprovision\ldprovision_config.windows.xml) was successfully downloaded

      2018-03-12 20:12:28(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:28(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\ProvisionHandlerLibrary.dll" http://CORESERVER/LdLogon/Provisioning/windows/ProvisionHandlerLibrary.dll)

      2018-03-12 20:12:29(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:29(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:29(1696-1704) ldProvision:The file (X:\ldprovision\ProvisionHandlerLibrary.dll) was successfully downloaded

      2018-03-12 20:12:29(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:29(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\ProvisioningCommon.dll" http://CORESERVER/LdLogon/Provisioning/windows/ProvisioningCommon.dll)

      2018-03-12 20:12:29(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:29(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:29(1696-1704) ldProvision:The file (X:\ldprovision\ProvisioningCommon.dll) was successfully downloaded

      2018-03-12 20:12:29(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:29(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\ClientRollinglog.dll" http://CORESERVER/LdLogon/ClientRollinglog.dll)

      2018-03-12 20:12:29(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:29(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:29(1696-1704) ldProvision:The file (X:\ldprovision\ClientRollinglog.dll) was successfully downloaded

      2018-03-12 20:12:29(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:29(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\log4net.dll" http://CORESERVER/LdLogon/log4net.dll)

      2018-03-12 20:12:30(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:30(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:30(1696-1704) ldProvision:The file (X:\ldprovision\log4net.dll) was successfully downloaded

      2018-03-12 20:12:30(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:30(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\ClientRollingLog.log4net" http://CORESERVER/LdLogon/ClientRollingLog.log4net)

      2018-03-12 20:12:30(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:30(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:30(1696-1704) ldProvision:The file (X:\ldprovision\ClientRollingLog.log4net) was successfully downloaded

      2018-03-12 20:12:30(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:30(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\ldprovision.sig" http://CORESERVER/LdLogon/Provisioning/windows/ldprovision.sig)

      2018-03-12 20:12:30(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:30(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:30(1696-1704) ldProvision:The file (X:\ldprovision\ldprovision.sig) was successfully downloaded

      2018-03-12 20:12:30(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:30(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\LaunchldprovisionAsUser.exe" http://CORESERVER/LdLogon/Provisioning/windows/LaunchldprovisionAsUser.exe)

      2018-03-12 20:12:30(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:30(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:30(1696-1704) ldProvision:The file (X:\ldprovision\LaunchldprovisionAsUser.exe) was successfully downloaded

      2018-03-12 20:12:30(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:30(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\ProvisionGUI.exe" http://CORESERVER/LdLogon/Provisioning/windows/ProvisionGUI.exe)

      2018-03-12 20:12:31(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:31(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:31(1696-1704) ldProvision:The file (X:\ldprovision\ProvisionGUI.exe) was successfully downloaded

      2018-03-12 20:12:31(1696-1704) ldProvision:Entering downloadbyproxy.

      2018-03-12 20:12:31(1696-1704) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\provcomm.dll" http://CORESERVER/LdLogon/Provisioning/windows/provcomm.dll)

      2018-03-12 20:12:32(1696-1704) ldProvision:Waiting for process result: 0.

      2018-03-12 20:12:32(1696-1704) ldProvision:Process exit code:0

      2018-03-12 20:12:32(1696-1704) ldProvision:The file (X:\ldprovision\provcomm.dll) was successfully downloaded

      2018-03-12 20:12:32(1696-1704) ldProvision:download prerequisite files OK

      2018-03-12 20:12:32(1696-1704) ldProvision:Running in Daemon mode.

      2018-03-12 20:12:32(1696-1704) ldProvision:Provision Mode = PROVISION_MODE_CORE_SID

      2018-03-12 20:12:32(1696-1704) ldProvision:Calling Program:x:\cba8\httpclient.exe  -b ncs -H"X:\ldprovision\header.txt" -o"X:\ldprovision\body.txt" -f"X:\ldprovision\result.xml" https://CORESERVER/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

      2018-03-12 20:12:33(1696-1704) ldProvision:Web service call attempt:0. ExitCode:0

      2018-03-12 20:12:33(1696-1704) ldProvision:Computer ID: 11334

      2018-03-12 20:15:51(1696-1704) ldProvision:Saving DeviceID to file.

      2018-03-12 20:15:51(1696-1704) ldProvision:Found BrokerConfig.exe in PE path x:\cba8\BrokerConfig.exe

      2018-03-12 20:15:51(1696-1704) ldProvision:Serial Number: XXXXXXX

      2018-03-12 20:15:51(1696-1704) ldProvision:Program: x:\cba8\BrokerConfig.exe

      2018-03-12 20:15:51(1696-1704) ldProvision:Args:  /b x:\cba8\ /p /a 28F10E48230D /s "XXXXXXX" /i 7255

      2018-03-12 20:20:51(1696-1704) ldProvision:Warning, not able to obtain a client certificate.  Secrets may not be able to be decrypted.

      2018-03-12 20:20:51(1696-1704) ldProvision:Session Data: <session><variable name="XXXXXXXXX" type="none">CORESERVER</variable><variable name="XXXXXXXX" type="none">Unassigned</variable><variable name"XXXXXX" type="none">XXXXXX</variable><variable name"XXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name"XXXXXXXXX" type="sensitive">XXXXXXXXXXXXXXX</variable><variable name="XXXXXXXX" type="none">CORESERVER</variable><variable name="XXXXXXXXXX" type="none">XXXXXXXXX</variable><variable name="XXXXXXXXXXX" type="none">XXXXXXXXXXX</variable><variable name="XXXXXXX" type="none">XXXXXX</variable><variable name="XXXXXXXXXX" type="none">XXXXXXXXX</variable><variable name="XXXXXXXXX" type="none">XXXXXXXXXXXXXXXX</variable><variable name="XXXXXX" type="none">XXXXXXXXX</variable><variable name="xXXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name="XXXXXXXXXXXX" type="none">XXXXXXX</variable><variable name="xXXXXXXXX" type="none">XXXXXXXXXXXX</variable><variable name="XXXXXXXXX" type="none">XXXXXXXXXXXX</variable><variable name="XXXXXXXXX" type="none">XXXXX</variable><variable name="XXXXXXXXXX" type="none">Unassigned</variable><variable name="XXXXXXXXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name="XXXXXXXXXXX" type="none">XXXXXX</variable><variable name="XXXXXXXXX" type="none">XXXXXXXXXX</variable><variable name="XXXXXXXXXX" type="none">XXXXXXXXXXXXXXXX</variable><variable name="_XXXXXXXXX" type="none">wait30</variable><variable name="XXXXXXXXXXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name="XXXXXXX" type="none">XXXXXXXXXX</variable><variable name="XXXXXXX" type="none">XXXXXXXX</variable><variable name="XXXXXXXXXXXXXXXXXX" type="none">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</variable><variable name="XXXXXXXXXX" type="none">XXXX</variable><variable name="XXXXXXXXX" type="sensitive">XXXXXXXXXXXXXXXXXXXXXXXXXXX</variable></session>

      2018-03-12 20:20:51(1696-1704) ldProvision:Going to have the core decrypt a password

      2018-03-12 20:41:10(1696-1704) ldProvision:Decrypting Provisioning Password http://coreserver:443/LANDesk/ManagementSuite/Core/serverauthentication/serverauthentication.asmx

      2018-03-12 20:41:10(1696-1704) ldProvision:Requesting for deviceId: {9CB96B07-766C-EC4F-B482-17DAF597922C}  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

      2018-03-12 20:41:10(1696-1704) ldProvision:Found httpclient.exe at x:\cba8\httpclient.exe

      2018-03-12 20:41:10(1696-1704) ldProvision:Making web service call via proxyhost.

      2018-03-12 20:41:10(1696-1704) ldProvision:httpclient args:  -b ncs -p"127.0.0.1:9592" -H"X:\ldprovision\wscheader.txt" -o"X:\ldprovision\wscbody.xml" -f"X:\ldprovision\wscresult.xml" http://CORESERVER:443/LANDesk/ManagementSuite/Core/serverauthentication/serverauthentication.asmx

      2018-03-12 20:41:40(1696-1704) ldProvision:TryallWebService exitcode: -1

      2018-03-12 20:42:15(1696-1704) ldProvision:TryallWebService exitcode: -1

      2018-03-12 20:42:55(1696-1704) ldProvision:TryallWebService exitcode: -1

      2018-03-12 20:43:05(1696-1704) ldProvision:Unable to decipher attribute name: 11

       

      For the log file proxyhost.log it was empty. I tried the same template with another device and proxyhost.log wasn't empty. There was some HTTP traffic.

       

       

      Proxyhost.log (!!! not on the affected device but in another device that succesfully retrieved and started processing provisioning task)

       

      2018-03-12 17:49:49(364-332) proxyhost.exe:127.0.0.1:49688 - - [12/Mar/2018:09:49:49 -0800] "POST http://CoreServer/landesk/managementsuite/core/core.anonymous/ClientCertificateRequest.asmx HTTP/1.1" 200 1621 2292

      2018-03-12 17:49:49(364-332) proxyhost.exe:127.0.0.1:49688 EOS on request

      2018-03-12 17:49:49(1220-1204) proxyhost.exe:FIPS mode = 0

      2018-03-12 17:49:49(1220-1204) proxyhost.exe:IsProcessSigned succeeded - returning: 1

      .

      .

      2018-03-12 17:49:49(1220-1204) proxyhost.exe:127.0.0.1:49690 - - [12/Mar/2018:09:49:49 -0800] "POST http://CoreServer:443/LANDesk/ManagementSuite/Core/serverauthentication/serverauthentication.asmx HTTP/1.1" 200 721 862

      2018-03-12 17:49:49(1220-1204) proxyhost.exe:127.0.0.1:49690 Connection terminated reading request line for socket 4 error code -2

      2018-03-12 17:49:49(348-352) proxyhost.exe:FIPS mode = 0

      2018-03-12 17:49:49(348-352) proxyhost.exe:IsProcessSigned succeeded - returning: 1

       

      In the IIS log file I can see this traffic. But for the device that keeps failing I can't see any traffic related to certificate or serverauthentication.

       

      One more thing, in the device that successfully started the provisioning task, the folder X:\cba8\cbaroot\broker there was .csr file + .Key file + proxy.state.xml + crt file but for the failed device this folder was empty.

       

      Many community articles and conversation talks about borkerconfig.exe /r I tried it but without any success.

       

      Could any one support me with this issue. I don't understand what is the role of brokerconfig.exe and why the device should apply for a certificate since I am not enabling client certificate-based feature and I don't have any blocked device.

        • 1. Re: provisioning actions are not retrieved and provisioning GUI is empty
          Aaron_Day SupportEmployee

          Hello,

           

          Even without Client Certificate-Based Security, the clients will need to authenticate via SSL when interacting with Core Web Services. Broker runs during the Provisioning process in order to get the validation certificate so it can use Web Services such as ServerAuthentication.

           

          When the device is failing vs Succeeding, is there a difference in what PXE Representative its getting the WinPE WIM Image from? Its possible you have a PXE Representative with a "Stale" version of the WinPE Image on it that is causing the failures.

           

          Thanks

           

          Aaron