- #How to how to clone uefi disk using symantec ghost 11.5 drivers
- #How to how to clone uefi disk using symantec ghost 11.5 driver
- #How to how to clone uefi disk using symantec ghost 11.5 windows 10
- #How to how to clone uefi disk using symantec ghost 11.5 trial
- #How to how to clone uefi disk using symantec ghost 11.5 Pc
#How to how to clone uefi disk using symantec ghost 11.5 trial
The Ghost solution suite 3.2 Trial version has WIN-PE 5.1 installed and incorperated from the ADK ( C:\Program Files (x86)\Windows Kits), as linked in the built in help guide.
#How to how to clone uefi disk using symantec ghost 11.5 Pc
The senario is in a corperate domain enviroemnt, we have a Windows 7 computer with the Ghost solution suite 3.2 Trial version on (including the RU1 patch) and a Windows 7 client PC what serves the purpose as a disater recovery PC, what requires to be imaged and and. Hi all, I am trialing the Ghost solution suite 3.2 at my workplace, however I am having some very odd issues with it. THNSN5256GPUK Toshiba 256GB NVME PCIe 3.0 x4 SSD I would hang at the end of the second cycle in "loading windows". I then replaced the WIM into the installed folder on the desktop. I then did a test boot with the Thumb drive and successfully loaded into the automation. So to save some time during the exparement I pushed the automation to a usb stick. I did most of these tests without loading most of the drivers. So with WinPE 3.1 and WinPE 4 they will go through the loading Windows and hang at the very end. I get an error that the drive is not accessable.ĭoing some VM testing from that point I figured out that UEFI boots with Windows 7 wouldn't work with WinPe 10 or even 5. As soon as the it boots to Automation and starts loading Windows.
#How to how to clone uefi disk using symantec ghost 11.5 driver
This didn't work out loading just about every driver from the Dell Driver pack and from their WinPE driver packs. Which as a side comment, I am doing an automation boot and not PXE, I am not against using PXE but I really don't have a good starting place experience wise. So I started by trying to use WinPE 10 for the automation. I got this setup so our SATA desktops can image. I have spent weeks and countless hours trying to get this GSS 3.2 (and 3.1 before the update) figured out and I keep hitting roadblock after roadblock. Realized today that originally posted this in the wrong area of the forum. Do also let me know if you want any more info. I have allready tried things like disabling UEFI boot in the BIOS, making sure the DR PC is using the MBR partitioning system, trying multiple times, etc.Īny ideas how to resolve the issue or what could be causing it? I have attched the GhostServers log as well as a couple of pictures of the above errors that I mention. "Usage Error 635: No Formatted partitions were found on the source drive." When I execute a GhostCast server task from the ghost server to create a non-syspreped image of the new DR PC, I get the follwoing once the new DR PC has rebooted into Win PE 4.0: Now regading to the main purpose of this thread, I would like some advice on what could be causing my current error when trying to capture and image the new DR PC.
#How to how to clone uefi disk using symantec ghost 11.5 drivers
I should also mention that Win PE 2.0 what comes by default with Ghost Solution Suite 2.5 has no NIC drivers for this PC, so out DR facility had to send us thier Win-PE. The modern Win 7 DR PC is a HP EliteDesk 800 65W G2 Desktop Mini PC. This ghost image is then sent to our DR facility where it is then mass deployed in the event of a majour disater or during a DR disater drill. wim and PC does not boot at all.ĭear sysmantic comunity, on behalf of a medium sized orgnization that I work for, I have been given the task of uisng our XP SP3 Ghost server with Ghost Solutuion Suite 2.5 on (Ghost server version is 11.) to backup and create a ghost image of our Distater Recovery PC what is a modern Windows 7 X64 PC provided by our DR facility. Of course, there is no partition left to apply the EFI. When schedule Distribute Disk Image job to apply the W10.wim, it erases my GPT structure and recreates the MBR from scratch. In fact, the only token I use in my answer file is the computer name: %COMPNAME%
Now my goal is to to apply the EFI.wim image to S: drive and the W10.wim to C: drive using my tokenized answer file, the same I do for Windows 7. Now I trying to apply them on the test PC.īefore I run the Distribute Disk Image job, I run the script that exactly matches the GPT partition structure on reference PC. To begin with, I captured 2 images in UEFI mode on reference PC. It has become a business requirement now.
#How to how to clone uefi disk using symantec ghost 11.5 windows 10
Windows 10 offers new security features that works only in UEFI mode. For years we have happily used DS6.9, re-branded to Ghost Solution.Until now we deployed a single image captured on MBR partition and deployed for pcs running in BIOS legacy mode.