3 Replies Latest reply on Nov 1, 2015 9:24 AM by JoeDrwiega

    Provisioning Agent Stalls after CTOS


      We've been trying to get Windows 10 Enterprise to image unsuccessfully for a few weeks now.  The problem we're having is that after the OS boots up and auto logs in with a local administrator account, the provisioning agent would stall/not resume.  I had opened a support case and was told that our unattend was invalid and to try a generic one from LANDESK https://community.landesk.com/support/docs/DOC-32344 (Winx64Unattend.xml).  That seems like it worked, as it will initially resume provisioning and join the domain.  The next action in the template was to reboot after joining the domain.


      Now I'm back where I started.  I see the C:\ldprovisioning directory and I've attempted to run ldprovisioning.cmd manually, but the agent isn't starting up.


      Has anyone had this problem?


      We are running LDMS 9.6 SP2 with a component patch for Windows 10 support.

      The target OS is Windows 10 Enterprise 64bit with legacy BIOS imaging.


      Thanks for any help in advance.


      Message was edited by: Kevin Beattie Modified title to include "after CTOS"