1 2 3 Previous Next 38 Replies Latest reply on Jul 19, 2017 11:15 AM by phoffmann

    OSD task fails after Reboot action executed

    Jon Miller Apprentice

      I am imaging Windows 10 Enterprise LTSB and have successfully deployed the image. I am struggling with the "Reboot/Shutdown" action in the System configuration portion of the template. I have tried the built in action and I have tried the execute option with shutdown.exe -r -t 00 and both will cause the template to fail. The action executes and does reboot the computer but the task does not pick up and continue upon the log in. In the template, I do not have "Stop processing the template if this action fails" checked. Please see the screen shot below for the outline of the template. Do you have any suggestions why this might be happening and how to correct this?

       

      I am running LDMS 2016.3 on Server 2012r2

       

       

       

      Thanks,

      Jon

        • 1. Re: OSD task fails after Reboot action executed
          Jon Miller Apprentice

          Out of curiosity I put one of the reboot actions before the LANDesk Agent install and it worked fine. It seems if I install the agent before I issue a reboot instruction, it will cause the issue I'm experiencing. I have the agent install early in the setup for the second phase of HII- I was informed that the full agent must be installed for the second HII action to work. Two HII tasks do a great job of discovering and installing all drivers for the endpoints. See the below screenshot. Any ideas?

           

          • 2. Re: OSD task fails after Reboot action executed
            dustin.schnabel Rookie

            I'm having the same issue on 2016 SU5.  I'm going to test just removing the reboot and see if the process completes, although it's recommended you reboot after the Agent install.

             

            Be interested if anyone found a workaround for this.

             

            Cheers,
            DJS

            • 3. Re: OSD task fails after Reboot action executed
              Peter Massa Expert

              Can you post the last 20 lines of your provisioning log from the client here?

               

              Even if the ldprovisioning folder deletes, the logs are stored at c:\windows\temp\.

               

              I want to see what the client thinks happened.  Usually when I see this - there is a hiccup in the communications of the client to the core in some way, either network or internal permission on the core processing side for the device's scope permission or unique ids.

               

              To add additional detail - the "stop processing if failure" check box only works when the template is properly processed on the core side.  So if there is an internal error in the way the core processed the request from the client asking where it left off, it will stop processing regardless of this check box because it is a fatal error.

               

              Peter

              • 4. Re: OSD task fails after Reboot action executed
                dustin.schnabel Rookie

                I noticed this morning when I did another deploy that EPS was alarming and blocking ldprovision.  I'm investigating this currently and trying again.

                1 of 1 people found this helpful
                • 5. Re: OSD task fails after Reboot action executed
                  Jon Miller Apprentice

                  Here's a few more than the 20 you requested.

                   

                   

                  2017-01-24 23:17:31(3828-3832) ldProvision.exe:Entering downloadbyproxy.

                  2017-01-24 23:17:31(3828-3832) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\PatchHandler.exe" http://SCISTCEMS03/LdLogon/Provisioning/windows/PatchHandler.exe)

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Waiting for process result: 0.

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Process exit code:0

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:The file (C:\ldprovisioning\PatchHandler.exe) was successfully downloaded

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Looking for existing file (C:\ldprovisioning\PatchHandler.sig)

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Entering downloadbyproxy.

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\PatchHandler.sig" http://SCISTCEMS03/LdLogon/Provisioning/windows/PatchHandler.sig)

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Waiting for process result: 0.

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Process exit code:-1

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Failed to download (C:\ldprovisioning\PatchHandler.sig)

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Informational: No sig file downloaded.

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Done with download handler.

                  2017-01-24 23:17:32(3828-3832) ldProvision.exe:Launching action handler [PatchHandler.exe] with parameters ["]

                  2017-01-24 23:17:35(3828-3832) ldProvision.exe:handler launched.

                  2017-01-24 23:17:36(3828-3832) ldProvision.exe:End of action - Patch_system

                  2017-01-24 23:17:36(3828-3832) ldProvision.exe:Reporting action status: 0 to core.

                  2017-01-24 23:17:36(3828-3832) ldProvision.exe:Call web service SetActionStatus()

                  2017-01-24 23:17:36(3828-3832) ldProvision.exe:Calling Program:C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe  -b ncs -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" https://SCISTCEMS03/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

                  2017-01-24 23:17:36(3828-3832) ldProvision.exe:Web service call attempt:0. ExitCode:0

                  2017-01-24 23:17:36(3828-3832) ldProvision.exe:

                   

                   

                  2017-01-24 23:17:36(3828-3832) ldProvision.exe:***********   Processing Action - Reboot/shutdown

                  2017-01-24 23:17:36(3828-3832) ldProvision.exe:Not able to set action as running

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Handling Action - Reboot_shutdown

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Do EnvironmentCheck

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Is WinPE Action=0, Is WinPe Environment=0

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:In Handle Action.

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Workdir in RebootHandler is C:\Program Files (x86)\LANDesk\LDClient\

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Reboot requested.

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Call web service SetActionStatus()

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Calling Program:C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe  -b ncs -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" https://SCISTCEMS03/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Web service call attempt:0. ExitCode:0

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Rebooting / Shutting down the machine

                  2017-01-24 23:17:37(3828-3832) ldProvision.exe:Exit ldProvision

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:Using [SCISTCEMS03] for Core

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:Getting server identifiers

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:Serial Number by WMI: 20NGRC2

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:Serial Number: 20NGRC2

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:ldProvision started

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:Going to add START:landesk.provisioning:C:\ldprovisioning\LaunchLdprovisionAsUser.exe C:\ldprovisioning\ldProvision.exe -c SCISTCEMS03 -t C:\ldprovisioning -w 15 -r 20 -s to C:\Program Files (x86)\LANDesk\Shared Files\\cbaroot\actions.ini

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:Could not write INI file C:\Program Files (x86)\LANDesk\Shared Files\\cbaroot\actions.ini : 5

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\Program Files (x86)\LANDesk\Shared Files\cbaroot\alert\provisioning.ruleset.xml) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ldprovision_config.windows.xml) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ProvisionHandlerLibrary.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ProvisioningCommon.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ClientRollinglog.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\log4net.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ClientRollingLog.log4net) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\brokerconfig.exe) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ldprovision.sig) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\LaunchldprovisionAsUser.exe) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ProvisionGUI.exe) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\provcomm.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\httprequest.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\libhttp.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\lddwnld.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\curllib.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ldredirect.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\libeay32.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ssleay32.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\libeay32mt.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\ssleay32mt.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:The file (C:\ldprovisioning\rollinglog.dll) is already present

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:download prerequisite files OK

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:Running in Daemon mode.

                  2017-01-24 23:18:27(5868-5896) ldProvision.exe:Provision Mode = PROVISION_MODE_CORE_SID

                  2017-01-24 23:18:43(5868-5896) ldProvision.exe:Calling Program:C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe  -b ncs -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" https://SCISTCEMS03/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

                  2017-01-24 23:18:43(5868-5896) ldProvision.exe:Web service call attempt:0. ExitCode:0

                  2017-01-24 23:18:43(5868-5896) ldProvision.exe:Computer ID: 217

                  2017-01-24 23:18:43(5868-5896) ldProvision.exe:Found existing DeviceID file. Importing to registry.

                  2017-01-24 23:18:43(5868-5896) ldProvision.exe:Found existing core server name file. Importing to registry.

                  2017-01-24 23:18:43(5868-5896) ldProvision.exe:Copying certificate C:\ldprovisioning\336e4453.0, to C:\Program Files (x86)\LANDesk\Shared Files\cbaroot\certs\336e4453.0

                  2017-01-24 23:18:44(5868-5896) ldProvision.exe:Could not copy certificate C:\ldprovisioning\336e4453.0, error code: 5

                  2017-01-24 23:18:44(5868-5896) ldProvision.exe:Caught exception in main: code=80000000H, file=ldProvision.cpp, line=892

                  2017-01-24 23:18:44(5868-5896) ldProvision.exe:Call web service GetStatusString()

                  2017-01-24 23:18:44(5868-5896) ldProvision.exe:Calling Program:C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe  -b ncs -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" https://SCISTCEMS03/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

                  2017-01-24 23:18:44(5868-5896) ldProvision.exe:Web service call attempt:0. ExitCode:0

                  2017-01-24 23:18:44(5868-5896) ldProvision.exe:StatusString = An unknown error occurred. If the problem persists, contact the LANDESK administrator.

                  2017-01-24 23:18:44(5868-5896) ldProvision.exe:Call web service SetActionStatus()

                  2017-01-24 23:18:44(5868-5896) ldProvision.exe:Calling Program:C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe  -b ncs -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" https://SCISTCEMS03/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx

                  2017-01-24 23:18:45(5868-5896) ldProvision.exe:Web service call attempt:0. ExitCode:0

                  2017-01-24 23:18:45(5868-5896) ldProvision.exe:Provision GUI still found alive, waiting.

                  2017-01-24 23:18:46(5868-5896) ldProvision.exe:Entering downloadbyproxy.

                  2017-01-24 23:18:46(5868-5896) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "ldsleep.exe" http://SCISTCEMS03/landesk/files/ldsleep.exe)

                  2017-01-24 23:18:46(5868-5896) ldProvision.exe:Waiting for process result: 0.

                  2017-01-24 23:18:46(5868-5896) ldProvision.exe:Process exit code:0

                  • 6. Re: OSD task fails after Reboot action executed
                    Jon Miller Apprentice

                    Sorry- as a side note, this was a clipping from the most recent imaging sequence where the reboot happens at the end of the template. It does still result in a failure on the reporting side of the task but does all imaging tasks correctly. If needed I can rearrange the task how you'd like.

                    • 7. Re: OSD task fails after Reboot action executed
                      tdavenport Specialist

                      Just curious but do you really need a LANDESK agent deployment at this time? As a test, take out the Agent deployment action and leave everything else the same. If the prov template continues successfully after a reboot (without the agent deployment action) then the issue is that the core does not associate the new agent with the existing provisioning task. Just a guess, but if this does happen, check your Inventory Service settings and confirm that (under Manage Duplicate Devices) you have "Restore Old Device IDs" checked. Another thing to check is: - at the time that the provisioning task fails: Run a query against the MAC address of your target machine. Does your query return more than one device? If so, the provisioning task is looking for the first device to continue the prov task and does not recognize your rebooted machine as being the correct target for the continuation of the prov. task. This happens to me sometimes when I run repetitive tests on the same box. Just delete all machines with that MAC address and rerun the template.

                       

                      I assume that you have auto logon enabled in your unattend.xml and that your target machine is auto-logging into the desktop and not stuck at the login prompt. If you're stuck at the login screen you need to update your unattend to allow auto login for the duration of your provisioning task.

                       

                      One last thing I noticed in your logs is that you are getting a cert error. I'm not sure it that is related to the new agent deployment or not.  If you go to Configure-Client Access - on the Manage Client Certificates - is your target machine being blocked.

                       

                      I know I just threw a few things out there but it should help you. I'm leaning towards duplicate MACs in your inventory.

                      • 8. Re: OSD task fails after Reboot action executed
                        Jon Miller Apprentice

                        Thanks for the info! To answer some of the questions- I do need the agent to install at that time to do the second phase of the HII and to deploy the software successfully. If I remove the agent before any of these tasks, the software distribution and HII fail. I did look at the Configure-Client Access and approve the device, it was not approved. I will try it again and I will also look for duplicate entries in the database. I also made the change in the Inventory Service Settings to enable "Restore Old Device IDs" as I did not have that selected before.

                         

                        I'll let you know what the query turns up- Do you know what table I should look at or the query I should use? I'm not too familiar with the database back end.

                        • 9. Re: OSD task fails after Reboot action executed
                          tdavenport Specialist

                          You could do a SQL query on the NetworkSoftware table. That will show MAC addresses. The easier thing to do would be to just run an LD query as shown below.MAC Search.PNG

                          • 10. Re: OSD task fails after Reboot action executed
                            Jon Miller Apprentice

                            So it is only returning 1 result, the computer it is suppose to. I verified via LD query and running a query against the sql database. I will give it another go since I made the other changes in the console and see if it works now.

                            • 11. Re: OSD task fails after Reboot action executed
                              Jon Miller Apprentice

                              Sadly, I got the same results.

                              • 12. Re: OSD task fails after Reboot action executed
                                Jon Miller Apprentice

                                Any other thoughts?

                                • 13. Re: OSD task fails after Reboot action executed
                                  1EarEngineer Specialist

                                  We have been getting this error for some time now. It's continue from 9.6 SP2, SP3 and into 2016. At first it appeared to be a package returning a non standard code when completing, even though LD reported it successful. However, with no change in the template, it is now doing the same thing again. Interestingly enough, I noticed your script also stops after the 2nd reboot. I'm curious if you remove the 1st reboot in your task, if it continues. For whatever reason it seems that none of my tasks will continue after the 2nd reboot action

                                  • 14. Re: OSD task fails after Reboot action executed
                                    Jon Miller Apprentice

                                    Thanks for the suggestion but I am still having zero luck. It appears the issue only happens when a reboot occurs after the install of the full agent.

                                    1 2 3 Previous Next