I'm trying to deploy my new windows 10 image to one of our laptops, but every time it comes down and begins startup, it goes through the Device Settings part and then starts a loop of startup/shutdown. I'm not sure what the issue is. Drivers are being deployed correctly by KACE. Any ideas on what might be causing this?

UPDATE: Something must be happening during sysprep. I just let the VM run through setup (we usually sysprep and then revert it back to a snapshot) and the VM is acting the same way - it won't get past setup. Somehow, sysprep is breaking the image (which doesn't really surprise me). Any ideas on HOW sysprep is breaking, though?
Answer Summary:
Cancel
2 Comments   [ + ] Show Comments

Comments

  • hello,

    what happen if you deploy the same image to a virtual machine? Same behaviour?
    Is the system image made of a single partition or more than one? (system partition + data partition)
    Kind regards,
    Marco - StockTrader
    • I've deployed to another VM with the same issue. It has a system partition and a data partition (on which the OS resided).
      • Ok, so have you captured both of the partitions? In the pre-installation phase have you added a job to create 2 partitions and one to format both of them?
        There are some explanations here: https://support.software.dell.com/k2000-systems-deployment-appliance/kb/113970
        Kind regards,
        StockTrader
  • @StockTrader I do all of that already. It seems to me that Sysprep is the problem.
Please log in to comment

Answer Chosen by the Author

2
you most likely have something wrong in your answer file if the master exhibits that behavior.  Can you email me or post your answer file?

I have my win10 ans file posted here

http://www.itninja.com/blog/view/windows-10-deployment-re-adds-bloatware-tips-and-tricks-to-help-get-rid-of
Answered 02/04/2016 by: SMal.tmcc
Red Belt

  • I suspected that too, so this morning I sysprepped the vm without an answer file and it booted up into the oobe. I then created a new answer file that is a bit more basic, and tested that on the master - that worked as well. I'm now in the process of uploading the freshly sysprepped image to KACE, and I'll try to deploy it on a physical machine once that's done (I suspect I won't run into issues with that). Once I confirm it's working, I'll be sure and come back to mark your answer as the best answer.
    • from experience it is a bad line. When that happens boot to the win DVD or KBE and go to the c: drive and there are sysprep logs that list the section/line that failed.
      • I wasn't able to track down the specific line (which doesn't help anyone else, sorry) but I took out a few options that were hiding some of the screens in setup. I had originally set all of them to "false" but this time I left all blank and just set the "oobe" screen and the network screens to "false" - that seemed to do the trick.
Please log in to comment

Answers

Answer this question or Comment on this question for clarity
Five Easy Steps to Smarter Systems Imaging
With traditional methods for systems imaging, each image captures a particular hardware and software configuration at a specific moment in time—static, unchanging, unmanageable.

Share