10 Replies Latest reply on Jul 25, 2016 12:31 PM by 1EarEngineer

    ldprovisoning.cmd wont automatically run after imaging Windows 10

    Apprentice

      In our template we have 4 task that should run automatically after the image has been completed. This is under the System Configuration part in the template. I can see that in the Setup folder Scripts SetupComplete.cmd that it has the ldprovisoning.cmd in there to run but it never does. I can do this manually and everything runs fine. Anyway to fix this?

       

      We are running LANDesk MS 2016

        • 1. Re: ldprovisoning.cmd wont automatically run after imaging Windows 10
          Alex.Richardson SSMMVPGroup

          Do you have a ldprovision folder on the c drive once it boots into windows? If yes does the ldprovision.log file show and errors?

           

          Normally if this isn't working its due to a problem with the CTOS action adding the command into your unattend.xml for this to run or a network issue on the client when it boots into windows but you say you can run manually so this shouldn't be it.

          • 2. Re: ldprovisoning.cmd wont automatically run after imaging Windows 10
            Henk Hillaert Employee

            Maybe you want to add the templates you are using to this article.

            • 3. Re: ldprovisoning.cmd wont automatically run after imaging Windows 10
              Apprentice

              Yes I do have the ldprovison folder on the C drive but I do not see any log file. Is this because I am not using Landesk to pass the unattend.xml. I have it setup when I capture the device.

              • 4. Re: ldprovisoning.cmd wont automatically run after imaging Windows 10
                Apprentice

                I couldn't find the way to attach the .xtp file so here is the text

                 

                <templates><template id="3a0e48f2-935b-4cc3-8741-dfabe7824a56" name="EITS-BaseImage-Win10-06-13-16" version="4"><description>EITS-BaseImage-Win10-06-13-16</description><preboot-os>WindowsPE</preboot-os><final-os><name>Windows</name><type-id>All</type-id><family-id>Windows</family-id><vendor-id>All</vendor-id><major-ver>-1</major-ver><minor-ver>-1</minor-ver><architecture>All</architecture></final-os><variables><variable name="_ShowClientUI" transform="none">True</variable><variable name="_CloseClientUI" transform="none">wait30</variable><variable name="_RemoveClientFolder" transform="none">True</variable><variable name="_provTitle" transform="none">EITS CTS LANDesk Provisioning</variable></variables><section id="SystemMigration" name="System migration"><description>Back up personal or custom files before the system is modified.</description><action name="Vboot" version="4"><description /><action-type>Reboot_shutdown</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">false</option></options><parameters><usepeer>True</usepeer><usepref>True</usepref><usesource>True</usesource><type>vboot</type><TimeOut>0</TimeOut></parameters></action></section><section id="PreOsInstall" name="Pre-OS installation"><description>Configure the hardware and get the system ready for installing the target OS.</description><action name="Create Default Partitions" version="4"><description /><action-type>Partition</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">true</option></options><parameters><diskID>0</diskID><action>autocreate</action></parameters></action></section><section id="OsInstall" name="OS installation"><description>Install the target operating system with the specified options.</description><action name="Deploy Image" version="4"><description /><action-type>Deploy_image</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">true</option></options><parameters><application>c:\ldprovision\imagex.exe</application><arguments>/apply \\cts-fileserver.msmyid.uga.edu\CTS\LDImageStore\EITSBaseImages\EITS-BaseImage-Win10-06-13-16.wim 1 C:</arguments><imagetype>XImage</imagetype><imagepath>\\cts-fileserver.msmyid.uga.edu\CTS\LDImageStore\EITSBaseImages\EITS-BaseImage-Win10-06-13-16.wim</imagepath><use_multicast>False</use_multicast></parameters></action></section><section id="PostOsInstall" name="Post-OS installation"><description>Add additional items after OS installation, before rebooting into the target OS. For example, you might add service pack updates.</description><action name="Execute BCDBoot" version="4"><description /><action-type>Execute_file</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">true</option></options><parameters><application>bcdboot.exe</application><arguments>c:\windows /s s:</arguments><retvalop>EqualTo</retvalop><retvalarg1>0</retvalarg1><workingdirectory /><environmentvariables /><capture_output>True</capture_output></parameters></action><action name="Hardware Independent Imaging" version="4"><description /><action-type>HII</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">true</option></options><parameters><GetDriverFilesMethod>copy</GetDriverFilesMethod><ForceUnsigned>False</ForceUnsigned></parameters></action><action name="Configure Target OS" version="4"><description /><action-type>Configure_target_os</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">true</option></options><parameters><Insert_uniqueID>False</Insert_uniqueID></parameters></action></section><section id="SystemConfiguration" name="System configuration"><description>Automate system configuration that must happen after booting into the target OS such as installing drivers and applications and updating scan files.</description><action name="Install LANDESK Agent" version="4"><description /><action-type>Configure_agent</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">true</option></options><parameters><RebootIfRequired>True</RebootIfRequired><exe_agent_path /><usepref>True</usepref><use_pref_credentials>True</use_pref_credentials><configuration>Default Windows Configuration</configuration><usepeer>True</usepeer><pConfigurationId>1</pConfigurationId><use_exe_agent>False</use_exe_agent><usesource>True</usesource><type>namedconfig</type><configtool>wscfg32.exe</configtool><corename /></parameters></action><action name="Hardware Independent Imaging" version="4"><description /><action-type>HII</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">true</option></options><parameters><GetDriverFilesMethod>copy</GetDriverFilesMethod><ForceUnsigned>False</ForceUnsigned></parameters></action><action name="Force update of LANDESK client policies" version="4"><description /><action-type>Execute_file</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">true</option></options><parameters><application>%%LDMS_CLIENT_DIR%%\PolicySync.exe</application><arguments>/wait</arguments><retvalop>EqualTo</retvalop><retvalarg1>0</retvalarg1><workingdirectory /><environmentvariables /><capture_output>True</capture_output></parameters></action><action name="Install Mapped Software" version="4"><description /><action-type>MappedSoftwareInstaller</action-type><variables /><options><option name="StopProcessingTemplateIfActionFails">true</option></options><parameters /></action></section></template></templates>

                • 5. Re: ldprovisoning.cmd wont automatically run after imaging Windows 10
                  Henk Hillaert Employee

                  That worked fine; thank you. In the bottom of your entry is the Attach option

                   

                  I don't see any action that calls your script. To do so I would add the "Execute file" option or maybe 'insert script' like in my example.

                   

                  Hope this helps.

                   

                  Henk

                  • 6. Re: ldprovisoning.cmd wont automatically run after imaging Windows 10
                    Apprentice

                    Well my unattended.xml is not being injected by landesk. It happens before I capture the image. What would the Execute file do?

                    • 8. Re: ldprovisoning.cmd wont automatically run after imaging Windows 10
                      Apprentice

                      It looks like the execute file did not work for me

                      • 10. Re: ldprovisoning.cmd wont automatically run after imaging Windows 10
                        1EarEngineer Specialist

                        Should have a look at Solved: Windows 10 unattend ComputerName

                        Had the exact same issue you are having.