5 Replies Latest reply on Oct 17, 2017 1:40 AM by Binskin

    Windows 10 Provisioning in Ivanti End Point Manager 2017


      We are trying to provision Windows 10 1703 to Dell 7480 and 7280 hardware and currently running into an issue where the computer never picks up again after the CTOS action. Everything looks good including the SysPrep and the unattend file. I seem to remember that LANDesk creates an entry in the SysPrep, after processing it, for a command called ldprovision.cmd in the Specialize section.


      When our provisioning template is run and I check the unattended.xml file in C:\Windows\Panther folder, there is NO ldprovision.cmd entry created.


      Can any one confirm to deny this? And why would provisioning not pick up after the CTOS action?



        • 1. Re: Windows 10 Provisioning in Ivanti End Point Manager 2017
          Frank Wils ITSMMVPGroup

          Is the c:\ldprovision map available in Windows after processing the Unattend? If so, will it continue if you run the ldprovision.exe manually? CTOS should put the command to continue in the setupcomplete.cmd file.


          Or Do you have a LANDESK Agent in your image? If so, check if the LANDESK Management Agent Service has started properly. If CTOS detects a LANDESK Agent, it will put the command in the start.ini for this service



          • 2. Re: Windows 10 Provisioning in Ivanti End Point Manager 2017

            Sorry for the delay. I have it working. There was an issue with the diskpart actions and script we were using. Thanks for your help.

            • 3. Re: Windows 10 Provisioning in Ivanti End Point Manager 2017
              jParnell Specialist

              GJHorn could you elaborate on your issue and/or solution? We just stood up a new Ivanti EPM 2017 server and the CTOS action is failing... there is no ldprovision folder on the root of C:, though there is a FirstLogonCommand in our Unattend (I can't guarantee that wasn't put in our unattend.xml manually):



                  <SynchronousCommand wcm:action="add">

                      <CommandLine>cmd /c C:\ldprovisioning\ldprovisioning.cmd</CommandLine>

                      <Description>Launch LANDesk Provisioning</Description>






              However, the task is reporting as failed in the Management Console (Result: A provisioning action failed. Return code: 1163. Log file: no.)


              I'm not seeing any errors or warnings in event viewer specifically with attempting to run the batch script at first logon, but I'm searching the registry to see if I can see any indication.

              • 4. Re: Windows 10 Provisioning in Ivanti End Point Manager 2017

                We had to use a Disk Part script to partition the hard drive a certain way for the System Reserved partition. The CTOS failing action is working now without me doing anything to fix it.


                You can reference this thread for the Disk Part script information. There is a bug in the Ivanti Disk Part actions.


                There is also a bug in the OOBE unattend section with Windows 10 1703 Creators Update in the way it reboots after the image is layed down on the hard drive. You may have to add a first action in System Configuration to Reboot with a 100 second delay. Look at this link. https://community.ivanti.com/docs/DOC-60735

                • 5. Re: Windows 10 Provisioning in Ivanti End Point Manager 2017

                  We are having this exact issue and im struggling to have it resolved, it does look like its a disk partition issue but we can't figure it out.


                  Same model Dell 7480, image goes down ok, it reboots but the boot drive is not present - i can see it as a boot option, but its not recognised as bootable.


                  Our job has worked fine up until this point with Surface Pro's, previous Dell Latitudes, but we hit this model and we're stuck.


                  Our job is as below and the diskpart (grabbed from the linked post) script follows, if anyone could point me in the right direction it would be greatly appreciated.


                  rem == CreatePartitions-UEFI.txt ==

                  rem == These commands are used with DiskPart to

                  rem for a UEFI/GPT-based PC.

                  rem Adjust the partition sizes to fill the drive

                  select disk 0


                  convert gpt

                  rem == 1. System partition =========================

                  create partition efi size=500

                  rem ** NOTE: For Advanced Format 4Kn drives,

                  rem               change this value to size = 260 **

                  format quick fs=fat32 label="System"

                  assign letter="S"

                  rem == 2. Microsoft Reserved (MSR) partition =======

                  create partition msr size=128

                  rem == 3. Windows partition ========================

                  rem ==    a. Create the Windows partition ==========

                  create partition primary

                  rem ==    b. Create space for the recovery image ===

                  shrink minimum=1960

                  rem       ** NOTE: Update this size to match the size

                  rem                of the recovery image           **

                  rem ==    c. Prepare the Windows partition =========

                  format quick fs=ntfs label="Windows"

                  assign letter="C"

                  list volume