Ghost Solution Suite

 View Only
  • 1.  Reserved and recovery getting drive letters

    Posted Feb 19, 2019 05:32 PM

    So win 10 creates two hidden partitions when you install it, a 499 reserved and 500 mb recovery, these don't have drive letters which is great, but when I capture the image and then redeploy it I'm getting three drives C: E and F, C is the main one and e and f are the drives above. Is there anyway to keep these drives from getting letters after ghost restores them? We use Altiris 8.5 but that forum is pretty much dead and the 1st level support person I had said I need to delete those partitions from my win 10 image but that seems risky from what I have read and if we do in place upgrades down the road.



  • 2.  RE: Reserved and recovery getting drive letters

    Posted Feb 20, 2019 07:57 AM

    What method are you using to capture the image?



  • 3.  RE: Reserved and recovery getting drive letters

    Posted Feb 20, 2019 10:04 AM

    We use MDT to load the  windows iso and install the altiris agents. We then use the capture image job that is within altiris Create Image, Source disk -SRC is set to 1



  • 4.  RE: Reserved and recovery getting drive letters

    Posted Mar 18, 2019 12:43 PM

    Use Diskpart to either create the partitions and mark them as hidden before restoring images, or do it afterwards, esnuring that drive letters are removed and that the correct partition(s) are marked as C: etc.  The bottom line is that the partitions you don't want to see need to be marked as hidden.



  • 5.  RE: Reserved and recovery getting drive letters

    Posted Mar 29, 2019 11:23 AM

    They where marked hidden, the issue was due to the VM that got created was using bios and the new devices coming in are using UEFI, would have thought this would have broken imaging but it did not, just messed up the drives. Set the VM to EFI, recreated the image and now everything is working



  • 6.  RE: Reserved and recovery getting drive letters

    Posted Mar 29, 2019 11:57 AM

    Cody thanks for looping back around to post what you found.   

      I have run into a hand full off oddities when moving from BIOS to UEFI but not noticed that one but enough oddities that I don't recomend BIOS to UEFI conversion.   It sounds like it wasn't an intentional conversion and in the end you are avoiding the oddities by going UEFI to UEFI.    

    Good work identifying where the behavior was coming from and resolving it.  

     

    Cheers.