Ghost Solution Suite

 View Only
  • 1.  Windows 10 won't boot after imaging

    Posted Apr 25, 2017 02:12 PM

    I'm using GSS 3.1 MP5. When using peer-to-peer Multicast for "distribute disk image" task the Windows 10 sysprepped image deploys and boots up normally.

     

    I switched to using GhostCast Server for the "distribute disk image" task and now the image lays down normally but won't boot to production. I get a black screen with ">>checking media presence...... >>media present..... >>Start PXE over IPv6." Nothing else changed.

    When checking the BIOS boot sequence, there is no "Windows boot manager" option.

     

    So, then in the "distribute disk image" task I unchecked "Automatically perform configuration task after completing this imaging task". Same problem.

    Can you help resolve this problem?

     

    Thanks,

    Shauna



  • 2.  RE: Windows 10 won't boot after imaging
    Best Answer

    Posted Apr 25, 2017 03:18 PM

    Shauna,

     

    It sounds like the boot partition may not be imaging correctly.. You can try adding -IB switch on the creation job and the -NTEXACT switch on the deployment job.

    Also.. Is the source machine Legacy or UEFI bios? Legacy uses MBR partition tables and UEFI uses GPT tables, this can cause issues if you are trying to deploy an Legacy to UEFI and vice versa.



  • 3.  RE: Windows 10 won't boot after imaging

    Posted Apr 25, 2017 04:27 PM
      |   view attached

    With peer-to-peer I was using the following switches-

    -IB -NTIL -Z9 -NTEXACT -AUTO -FDSP

    Since changing to GhostCast I removed those switches and now the deployed image is booting into production.

    I have another question now. There are several tasks in the imaging job. The next task is to "modify configuration" to name the computer and join the domain. The client never gets that task after booting into production.

    In the distribute disk image task I have tried checking and unchecking the "automatically perform configuration task after completing this imaging task". Either way, the modify configuration task never runs.

    I've attached a screenshot of the distribute image task that lays down the image and boots into production but does not go to the next task in the job.

    Thanks for the help.



  • 4.  RE: Windows 10 won't boot after imaging

    Posted Apr 25, 2017 04:38 PM

    Shauna,

     

    You will want to create a new forum post for the new query you have... however, normally with configuration the agent must be on the image that way after deploymnet the client will check in with the console and finish the deployment task.



  • 5.  RE: Windows 10 won't boot after imaging

    Posted Apr 27, 2017 06:03 PM

    Shauna,

     

    Do you require further information about this issue? If not can you please mark the most relevant answer as the solution.



  • 6.  RE: Windows 10 won't boot after imaging

    Posted Apr 28, 2017 09:28 AM

    No further action required at this time. No resolution at this time.



  • 7.  RE: Windows 10 won't boot after imaging

    Posted Apr 28, 2017 12:17 PM

    were you not able to resolve the issue with the image not laying down correctly?



  • 8.  RE: Windows 10 won't boot after imaging

    Posted Apr 28, 2017 03:08 PM

    Not via the console "distribute disk image" task when using GhostCast Server. The image lays down fine but it won't boot to production. Checking the BIOS reveals that there is no Windows Boot Manager present as a boot option. The BIOS is set correctly for UEFI boot.

    When using a USB boot drive and the standard GhostCast Server (not via the console) the image lays down and boots to production just fine.

    Both the USB boot drive and the Automation Folder are created from the same WinPE configuration.

    The school district is moving from Windows 7 and legacy BIOS to Windows 10 and UEFI BIOS. The WinPE configuration startup.bat contains commands, using the Dell Command Configure tool to change the BIOS, and DiskPart to clean the disk. This works over and over again from the USB boot drive.

    Tech support tells me this is a known issue and they will get back to me.

    Hoping it is fixed soon as we will be imaging 9500 desktops and laptops over the summer and we really need a zero touch solution.



  • 9.  RE: Windows 10 won't boot after imaging

    Posted May 08, 2017 10:30 AM

    We have the EXACT same issue. We have to wipe the PC before deploying in order for it to take the Windows 10 image. Imaging from a USB is fine.

     

    Shauna, did they ever reply to you? I'd love to hear the outcome of this.

     

    Thanks.