1 2 Previous Next 18 Replies Latest reply on Jun 22, 2016 11:40 AM by Abnranger67

    Provisioning template-System Config-Distribute software

    ddavis Rookie

      Hello,


      I am new to LANDesk and I'm trying to create a provisioning template to install Win 7 x64 and install certain applications.  So far I've been doing ok.  I can get the image deployed and configured and boot into the OS, but the distribute software section just kind of sits there and nothing starts.  I believe I'm doing this correctly because it seems very similar to MDT which I have quite a bit of experience in.  I have it pointing to my package (Java) which is a standard MSI file.  Is there something I'm missing?  I've tried looking through the log locations found on the  knowledge base here and I can't get any good info about what is going on.  Is anyone able to give me any suggestions on how to troubleshoot this?  Any help will be appreciated, thanks!

       

      PS I'm running the latest LANDesk 9.5 SP2.

        • 1. Re: Provisioning template-System Config-Distribute software
          LANDave SupportEmployee

          Post your LDPROVISION.EXE.LOG and your SDClientHandler.log?

           

          Both should be in X:\LDProvision if you are in WinPE.

           

          C:\LDProvision from Windows.

          • 2. Re: Provisioning template-System Config-Distribute software
            ddavis Rookie

            Dave, after looking at these it seems that it knows the packages to install, just never does?

             

            .

             

            LDProvision

             

            2014-04-23 21:05:01(2544-2136) ldProvision.exe:Process exit code:0
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:Installing the driver
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:Installing service C:\ldprovisioning\cismbios.sys
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:SMBiosHelper::InstallSMBios - Checking to see if smbios service is running
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:Checking to see if smbios Service Exists
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:Installing smbios driver
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:Checking to see if smbios Service Exists
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:Checking to see if smbios service is running.
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:Starting smbios service
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:SUCCEEDED:  smbios service started
            2014-04-23 21:05:01(2544-2136) ldProvision.exe:Getting server identifiers
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Serial Number by WMI: PK2ECR0
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Serial Number: PK2ECR0
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:ServerIdentifier::getAMT_GUID - Checking to see if smbios service is running
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:SMBiosHelper::IsRunning - Checking to see if smbios service is running
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Checking to see if smbios service is running.
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Smbios service is running.
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Getting smbios service path.
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:checking path C:\ldprovisioning vs \??\C:\ldprovisioning
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:SMBiosHelper::StopSMBIOS - Checking to see if smbios service is running
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Checking to see if smbios service is running.
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Smbios service is running.
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Stopping smbios service
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Checking to see if smbios Service Exists
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Removing smbios driver
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:ldProvision started
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Going to add START:landesk.provisioning:C:\ldprovisioning\LaunchLdprovisionAsUser.exe C:\ldprovisioning\ldProvision.exe -c AM01B013 -t C:\ldprovisioning -w 15 -r 20 -s to C:\Program Files (x86)\LANDesk\Shared Files\\cbaroot\actions.ini
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\Program Files (x86)\LANDesk\Shared Files\cbaroot\alert\provisioning.ruleset.xml" http://AM01B013/LdLogon/alertrules/provisioning.ruleset.xml)
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Process exit code:0
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:The file (C:\Program Files (x86)\LANDesk\Shared Files\cbaroot\alert\provisioning.ruleset.xml) was successfully downloaded
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\ldprovision_config.windows.xml" http://AM01B013/LdLogon/Provisioning/windows/ldprovision_config.windows.xml)
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Process exit code:0
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:The file (C:\ldprovisioning\ldprovision_config.windows.xml) was successfully downloaded
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\ProvisionGUI.exe" http://AM01B013/LdLogon/Provisioning/windows/ProvisionGUI.exe)
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Process exit code:0
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:The file (C:\ldprovisioning\ProvisionGUI.exe) was successfully downloaded
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\provcomm.dll" http://AM01B013/LdLogon/Provisioning/windows/provcomm.dll)
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Process exit code:0
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:The file (C:\ldprovisioning\provcomm.dll) was successfully downloaded
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:download prerequisite files OK
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Running in Daemon mode.
            2014-04-23 21:05:03(2544-2136) ldProvision.exe:Provision Mode = PROVISION_MODE_CORE_SID
            2014-04-23 21:05:19(2544-2136) ldProvision.exe:Start TryallWebService Attempt:0.
            2014-04-23 21:05:21(2544-2136) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0
            2014-04-23 21:05:21(2544-2136) ldProvision.exe:Computer ID: 311
            2014-04-23 21:05:21(2544-2136) ldProvision.exe:Session Data: <session><variable name="corename" type="none">AM01B013</variable><variable name="coreIP" type="none">10.210.3.13</variable><variable name="ldDeviceID" type="none">Unassigned</variable><variable name="ldHostname" type="none"/><variable name="macAddress" type="none">3C970EE29186</variable><variable name="_ShowClientUI" type="none">True</variable><variable name="_CloseClientUI" type="none">wait30</variable><variable name="_RemoveClientFolder" type="none">True</variable></session>
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:ProvisionGUI.exe start OK
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:********************************** Begin processing actions **********************************
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:

            2014-04-23 21:05:26(2544-2136) ldProvision.exe:*********  Begin an action - Distribute_software
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Do EnvironmentCheck
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Is WinPE Action=0, Is WinPe Environment=0
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Session Data: <variables/>
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\SDClientHandler.exe" http://AM01B013/LdLogon/Provisioning/windows/SDClientHandler.exe)
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Process exit code:0
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:The file (C:\ldprovisioning\SDClientHandler.exe) was successfully downloaded
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Download handler ok.
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Launching action handler [SDClientHandler.exe] with parameters ["]
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:handler launched.
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Built SWD handler input [<GlobalSchedulerData Type="LANDesk.ManagementSuite.SoftwareDistribution.Data.XmlCommandLines"><XmlCommandLines><cmdLines><item><key>LDMS9_5_1</key><value>"%LDMS_CLIENT_DIR%\sdclient.exe" /p="\\am01b033.america.veka.ads\installs\Java\jre1.7.0_51\jre1.7.0_51.msi" /levels=4 /Hash=aPD2ZyPQL3N5LOOSoaJqtg== /pkgid=7 /pkgname="Java 7.51 x86" /FileListName="taskmanifest.AM01B013.65.7.ini" /FileListHash="wKrUU5m0K4spV76Xf4grGQ==" /msi /msiexec /noparse /An /wan=25 /lan=75 /cmds="/i /quiet /norestart" /taskid=65 /taskName="Win7 X64 Test" /core="AM01B013:10.210.3.13" /sad=50 /EnableVirtualAppShortcuts /enableloggedoffuserinstall  /dmname="Always listed for installation" /dmtype=4 /token /detachedmode /primaryPkgId=7</value></item><item><key>LDMS9_5</key><value>"%LDMS_CLIENT_DIR%\sdclient.exe" /p="\\am01b033.america.veka.ads\installs\Java\jre1.7.0_51\jre1.7.0_51.msi" /levels=4 /Hash=aPD2ZyPQL3N5LOOSoaJqtg== /FileListName="taskmanifest.AM01B013.65.7.ini" /FileListHash="wKrUU5m0K4spV76Xf4grGQ==" /msi /msiexec /noparse /An /wan=25 /lan=75 /cmds="/i /quiet /norestart" /taskid=65 /core="AM01B013:10.210.3.13" /sad=50 /EnableVirtualAppShortcuts /enableloggedoffuserinstall  /token /detachedmode /primaryPkgId=7</value></item><item><key>LDMS9</key><value /></item><item><key>LDMS8_8_1</key><value /></item><item><key>LDMS8_8</key><value /></item><item><key>LDMS8_7_8</key><value /></item><item><key>LDMS8_7_7</key><value /></item><item><key>LDMS8_7_5</key><value /></item><item><key>LDMS8_7</key><value /></item><item><key>LDMS8_6_1</key><value /></item><item><key>LDMS8_5</key><value /></item><item><key>LDMS8</key><value /></item><item><key>LDMS7_or_earlier</key><value /></item></cmdLines></XmlCommandLines></GlobalSchedulerData>]
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Report waiting on swd action status to core.
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Call web service SetActionStatus()
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:Start TryallWebService Attempt:0.
            2014-04-23 21:05:26(2544-2136) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0
            2014-04-23 21:05:28(2544-2136) ldProvision.exe:Report might reboot status to core.
            2014-04-23 21:05:28(2544-2136) ldProvision.exe:Call web service SetActionStatus()
            2014-04-23 21:05:28(2544-2136) ldProvision.exe:Start TryallWebService Attempt:0.
            2014-04-23 21:05:29(2544-2136) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0
            2014-04-23 21:27:26(3240-3244) ldProvision.exe:Using [AM01B013] for Core
            2014-04-23 21:27:26(3240-3244) ldProvision.exe:Checking to see if smbios service is running.
            2014-04-23 21:27:26(3240-3244) ldProvision.exe:Could not open smbios service.
            2014-04-23 21:27:26(3240-3244) ldProvision.exe:SMBios service not running
            2014-04-23 21:27:26(3240-3244) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\cismbios.sys" http://AM01B013/ldlogon/cismbios64.sys)
            2014-04-23 21:27:26(3240-3244) ldProvision.exe:Process exit code:0
            2014-04-23 21:27:26(3240-3244) ldProvision.exe:Installing the driver
            2014-04-23 21:27:26(3240-3244) ldProvision.exe:Checking to see if smbios Service Exists
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Checking to see if smbios Service Exists
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Checking to see if smbios service is running.
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Starting smbios service
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Getting server identifiers
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Serial Number by WMI: PK2ECR0
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Serial Number: PK2ECR0
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:ServerIdentifier::getAMT_GUID - Checking to see if smbios service is running
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Checking to see if smbios service is running.
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Smbios service is running.
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Getting smbios service path.
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Checking to see if smbios service is running.
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Smbios service is running.
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Stopping smbios service
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Checking to see if smbios Service Exists
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Removing smbios driver
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:ldProvision started
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Going to add START:landesk.provisioning:C:\ldprovisioning\LaunchLdprovisionAsUser.exe C:\ldprovisioning\ldProvision.exe -c AM01B013 -t C:\ldprovisioning -w 15 -r 20 -s to C:\Program Files (x86)\LANDesk\Shared Files\\cbaroot\actions.ini
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:download prerequisite files OK
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Running in Daemon mode.
            2014-04-23 21:27:27(3240-3244) ldProvision.exe:Provision Mode = PROVISION_MODE_CORE_SID
            2014-04-23 21:27:42(3240-3244) ldProvision.exe:Start TryallWebService Attempt:0.
            2014-04-23 21:27:43(3240-3244) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0
            2014-04-23 21:27:43(3240-3244) ldProvision.exe:Computer ID: 311
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:ProvisionGUI.exe start OK
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:********************************** Begin processing actions **********************************
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:

            2014-04-23 21:27:49(3240-3244) ldProvision.exe:*********  Begin an action - Distribute_software
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:Do EnvironmentCheck
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:Is WinPE Action=0, Is WinPe Environment=0
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:Download handler ok.
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:Launching action handler [SDClientHandler.exe] with parameters ["]
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:handler launched.
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:Built SWD handler input [<GlobalSchedulerData Type="LANDesk.ManagementSuite.SoftwareDistribution.Data.XmlCommandLines"><XmlCommandLines><cmdLines><item><key>LDMS9_5_1</key><value>"%LDMS_CLIENT_DIR%\sdclient.exe" /p="http://am01b013.america.veka.ads/patches/Installs/vmware/VMware-Horizon-View-Client-x86_64-2.3.0-1551379.exe" /levels=4 /Hash=XNVRUsKAXSpjzPnlH9bABg== /pkgid=21 /pkgname="VMWare view client" /FileListName="taskmanifest.AM01B013.65.21.ini" /FileListHash="mgQWSH5KaVLSpCmOIZZUBQ==" /exe /An /wan=25 /lan=75 /cmds="/S /V"" /qn VDM_SERVER=vdi.vekainc.com REBOOT=ReallySuppress""" /taskid=65 /taskName="Win7 X64 Test" /core="AM01B013:10.210.3.13" /sad=50 /EnableVirtualAppShortcuts /enableloggedoffuserinstall  /dmname="Always listed for installation" /dmtype=4 /token /detachedmode /primaryPkgId=21</value></item><item><key>LDMS9_5</key><value>"%LDMS_CLIENT_DIR%\sdclient.exe" /p="http://am01b013.america.veka.ads/patches/Installs/vmware/VMware-Horizon-View-Client-x86_64-2.3.0-1551379.exe" /levels=4 /Hash=XNVRUsKAXSpjzPnlH9bABg== /FileListName="taskmanifest.AM01B013.65.21.ini" /FileListHash="mgQWSH5KaVLSpCmOIZZUBQ==" /exe /An /wan=25 /lan=75 /cmds="/S /V"" /qn VDM_SERVER=vdi.vekainc.com REBOOT=ReallySuppress""" /taskid=65 /core="AM01B013:10.210.3.13" /sad=50 /EnableVirtualAppShortcuts /enableloggedoffuserinstall  /token /detachedmode /primaryPkgId=21</value></item><item><key>LDMS9</key><value /></item><item><key>LDMS8_8_1</key><value /></item><item><key>LDMS8_8</key><value /></item><item><key>LDMS8_7_8</key><value /></item><item><key>LDMS8_7_7</key><value /></item><item><key>LDMS8_7_5</key><value /></item><item><key>LDMS8_7</key><value /></item><item><key>LDMS8_6_1</key><value /></item><item><key>LDMS8_5</key><value /></item><item><key>LDMS8</key><value /></item><item><key>LDMS7_or_earlier</key><value /></item></cmdLines></XmlCommandLines></GlobalSchedulerData>]
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:Report waiting on swd action status to core.
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:Call web service SetActionStatus()
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:Start TryallWebService Attempt:0.
            2014-04-23 21:27:49(3240-3244) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0
            2014-04-23 21:27:51(3240-3244) ldProvision.exe:Report might reboot status to core.
            2014-04-23 21:27:51(3240-3244) ldProvision.exe:Call web service SetActionStatus()
            2014-04-23 21:27:51(3240-3244) ldProvision.exe:Start TryallWebService Attempt:0.
            2014-04-23 21:27:51(3240-3244) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

             

             

             

            SDClientHandler

             

            2014-04-23 21:05:26(3860-3880) SDClientHandler.exe:Starting Software Deployment.

            2014-04-23 21:05:26(3860-3880) SDClientHandler.exe:Diabling Client Queue for clients 9.0 SP2 and above.

            2014-04-23 21:05:26(3860-3880) SDClientHandler.exe:Diabling SDClient task status reporting for clients 9.5 and above.

            2014-04-23 21:05:26(3860-3880) SDClientHandler.exe:Checking for SDClient Mutex.

            2014-04-23 21:05:28(3860-3880) SDClientHandler.exe:Got mutex attempting distribution.

            2014-04-23 21:05:28(3860-3880) SDClientHandler.exe:Going to execute "C:\Program Files (x86)\LANDesk\LDClient\SDClient.exe" /stdin

            2014-04-23 21:27:49(3204-3228) SDClientHandler.exe:Starting Software Deployment.

            2014-04-23 21:27:49(3204-3228) SDClientHandler.exe:Diabling Client Queue for clients 9.0 SP2 and above.

            2014-04-23 21:27:49(3204-3228) SDClientHandler.exe:Diabling SDClient task status reporting for clients 9.5 and above.

            2014-04-23 21:27:49(3204-3228) SDClientHandler.exe:Checking for SDClient Mutex.

            2014-04-23 21:27:51(3204-3228) SDClientHandler.exe:Got mutex attempting distribution.

            2014-04-23 21:27:51(3204-3228) SDClientHandler.exe:Going to execute "C:\Program Files (x86)\LANDesk\LDClient\SDClient.exe" /stdin

            • 3. Re: Provisioning template-System Config-Distribute software
              Frank Wils ITSMMVPGroup

              Look in your Windows event logs... Is there something else installing things at the same time? Both Wsus and/or LD Patch manager can get in your way here.

               

              Frank

              • 4. Re: Provisioning template-System Config-Distribute software
                Rookie

                It could be as simple as the agent configuration. Is "Software Distribution" included with the agent that you are using for provisioning? I just had a similar issue, because I got the bright idea to turn it off in my provsioning agent.

                 

                Thanks,

                Scott

                • 5. Re: Provisioning template-System Config-Distribute software
                  ddavis Rookie

                  Yes, software distribution is turned on from what I can tell.  Would anyone be willing to share what their provisioning agent is setup like?  I'm thinking I missed something dumb and probably would have an a HA moment when I see a correct working one.  Thanks

                  • 6. Re: Provisioning template-System Config-Distribute software
                    Rookie

                    I am still trying to nail down my settings, but I used this link, http://community.landesk.com/support/docs/DOC-9526, as a reference.

                     

                    Pay close attention to the first image, as this is the area that I was referencing earlier.

                     

                    LD_Prov_main.png

                    LD_Prov_Inv.pngLD_Prov_Dist.png

                     

                    I only showed what I focused on in setting it up. The post still looks like it is valid, although at the beginning it shows as deprecated with 9.0 SP3.

                     

                    Hope this helps,

                    Scott

                    • 7. Re: Provisioning template-System Config-Distribute software
                      ddavis Rookie

                      Scott, this is very similar to what I have.  I will dig deeper and continue to test.  Thanks for the input

                      • 8. Re: Provisioning template-System Config-Distribute software
                        Alex.Richardson SSMMVPGroup

                        Can you check the application event log for any errors / crashes of the sdclienthalnder.exe process on the client PC like below?

                         

                        Description:

                        Faulting application name: SDClientHandler.exe, version: 9.50.2.16, time stamp: 0x515982df

                         

                        If yes then I have 2 environments with a similar problem and an open case with LANDesk for this but no resolution at present.

                        • 9. Re: Provisioning template-System Config-Distribute software
                          LANDave SupportEmployee

                          Also, I know we did have an issue with the Software Distribution action that was resolved in one of the later component patches for LDMS 9.5 SP2.

                           

                          The issue there was for example, if you had 10 packages to install, on various computers a random amount of those 10 packages would get installed.

                           

                          If you looked at a computer that only got 5 out of 10 packages installed, it would show successful for all 10 packages, however if you dug into the details you would see that it installed 5 of the 10 packages twice, not all 10 packages.

                           

                          Not sure how else to explain the issue.

                           

                          At any rate, the BASE component patch that is available under LANDESK Updates in Patch Manager resolves that issue.2014-04-28_5-30-44.jpg

                           

                          2014-04-28_5-33-11.jpg

                          • 10. Re: Provisioning template-System Config-Distribute software
                            ddavis Rookie

                            Thanks Dave, I'll give this a shot!

                            • 11. Re: Provisioning template-System Config-Distribute software
                              rickorhino Apprentice

                              I want to reply as well because it seems we are having the same issue ddavis however my software distribution works sometimes and sometimes does not. I am using "confgure agent" and not using a provisioning agent. Mostly because it seems the use of a provisioning agent was encouraged in earlier versions of OSD but I have found documentation stating anything past 9.0 SP3 the issue is resolved. Plus it seems redundant to me to install an OSD agent only to go back and install your full production agent later. My log performs the configure agent task and then just ends:

                               

                               

                               

                              2014-04-29 19:30:33(1152-1140) ldProvision.exe:*********  Begin an action - Configure_agent

                              2014-04-29 19:30:33(1152-1140) ldProvision.exe:Do EnvironmentCheck

                              2014-04-29 19:30:33(1152-1140) ldProvision.exe:Is WinPE Action=0, Is WinPe Environment=0

                              2014-04-29 19:30:33(1152-1140) ldProvision.exe:Report might reboot status to core.

                              2014-04-29 19:30:33(1152-1140) ldProvision.exe:Call web service SetActionStatus()

                              2014-04-29 19:30:33(1152-1140) ldProvision.exe:Start TryallWebService Attempt:0.

                              2014-04-29 19:30:33(1152-1140) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

                              2014-04-29 19:30:33(1152-1140) ldProvision.exe:Create process (C:\Program Files\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\ConfigHandler.exe" http://MICHGLDESK04.na.int.grp/LdLogon/Provisioning/windows/ConfigHandler.exe)

                              2014-04-29 19:30:34(1152-1140) ldProvision.exe:Process exit code:0

                              2014-04-29 19:30:34(1152-1140) ldProvision.exe:Download handler ok.

                              2014-04-29 19:30:34(1152-1140) ldProvision.exe:Launching action handler [ConfigHandler.exe] with parameters ["]

                              2014-04-29 19:30:34(1152-1140) ldProvision.exe:handler launched.

                              2014-04-29 19:39:24(1152-1140) ldProvision.exe:Reporting action status: 0 to core

                              2014-04-29 19:39:25(1152-1140) ldProvision.exe:Call web service SetActionStatus()

                              2014-04-29 19:39:25(1152-1140) ldProvision.exe:Start TryallWebService Attempt:0.

                              2014-04-29 19:39:25(1152-1140) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:-1073741512

                              2014-04-29 19:39:30(1152-1140) ldProvision.exe:Start TryallWebService Attempt:1.

                              2014-04-29 19:39:30(1152-1140) ldProvision.exe:End TryallWebService Attempt:1. ExitCode:-1073741512

                              2014-04-29 19:39:41(1152-1140) ldProvision.exe:Start TryallWebService Attempt:2.

                              2014-04-29 19:39:41(1152-1140) ldProvision.exe:End TryallWebService Attempt:2. ExitCode:-1073741512

                              2014-04-29 19:39:48(1152-1140) ldProvision.exe:Failed to call web service. exitCode=-1073741512

                              2014-04-29 19:39:48(1152-1140) ldProvision.exe:Caught exception in main: code=80001500H, file=.\ProvisioningWebSvc.cpp, line=933

                              2014-04-29 19:39:48(1152-1140) ldProvision.exe:Call web service GetStatusString()

                              2014-04-29 19:39:48(1152-1140) ldProvision.exe:Start TryallWebService Attempt:0.

                              2014-04-29 19:39:48(1152-1140) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:-1073741512

                              2014-04-29 19:39:58(1152-1140) ldProvision.exe:Start TryallWebService Attempt:1.

                              2014-04-29 19:39:58(1152-1140) ldProvision.exe:End TryallWebService Attempt:1. ExitCode:-1073741512

                              2014-04-29 19:40:11(1152-1140) ldProvision.exe:Start TryallWebService Attempt:2.

                              2014-04-29 19:40:11(1152-1140) ldProvision.exe:End TryallWebService Attempt:2. ExitCode:-1073741512

                              2014-04-29 19:40:16(1152-1140) ldProvision.exe:Failed to call web service. exitCode=-1073741512

                              2014-04-29 19:40:16(1152-1140) ldProvision.exe:Call web service SetActionStatus()

                              2014-04-29 19:40:16(1152-1140) ldProvision.exe:Start TryallWebService Attempt:0.

                              2014-04-29 19:40:16(1152-1140) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:-1073741512

                              2014-04-29 19:40:28(1152-1140) ldProvision.exe:Start TryallWebService Attempt:1.

                              2014-04-29 19:40:28(1152-1140) ldProvision.exe:End TryallWebService Attempt:1. ExitCode:-1073741512

                              2014-04-29 19:40:39(1152-1140) ldProvision.exe:Start TryallWebService Attempt:2.

                              2014-04-29 19:40:39(1152-1140) ldProvision.exe:End TryallWebService Attempt:2. ExitCode:-1073741512

                              2014-04-29 19:40:46(1152-1140) ldProvision.exe:Failed to call web service. exitCode=-1073741512

                              2014-04-29 19:41:16(1152-1140) ldProvision.exe:Create process (C:\Program Files\LANDesk\Shared Files\httpclient.exe) with args (  -f "ldsleep.exe" http://MICHGLDESK04.na.int.grp/landesk/files/ldsleep.exe)

                              2014-04-29 19:41:16(1152-1140) ldProvision.exe:Process exit code:-1073741512

                               

                              Agent is fully functioning without issue though.

                              • 12. Re: Provisioning template-System Config-Distribute software
                                ddavis Rookie

                                I installed this and now I can't load the provisioning template from winPE, just keeps retrying.  Looks like a support case to LANDesk it is!!!  LOL

                                • 13. Re: Provisioning template-System Config-Distribute software
                                  Frank Wils ITSMMVPGroup

                                  Did you also redeploy your PXE Rep after installing the update?

                                   

                                  Frank

                                  • 14. Re: Provisioning template-System Config-Distribute software
                                    Frank Wils ITSMMVPGroup

                                    If you don't use a Provisioning agent, automatically started processes like Vulscan, Policy Invoker can still interfere with your Software installations. Check your Windows Event log to see if other installations were also active at the time of your software installation faillure.

                                     

                                    Frank

                                    1 2 Previous Next