Q: Does AOMEI Image Deploy support UEFI boot machines?
A: The AOMEI Image Deploy does not support booting UEFI machines currently. This feature may be achieved in future versions.
Q: How to solve the SID related issue when you deploy a system image to different computers in the same domain.
A: To solve the problem, you can first run the Sysprep command to remove the SID information from a computer you wish to create a deployment image from and then deploy that image to multiple computers using the AOMEI Image Deployment tool. Please check the instructions here.
Q: Why the “Local IP” and the “Server IP” showed in client computer have different network segment and also the connection status is “None”?
A: Maybe there are multiple DHCP servers in the LAN. Please just keep one DHCP server and Disable others.
Also, maybe there is no network card driver, or the network card driver on the client computer is not recognized.
We advise you to open the image deploy tool, click the “Create bootable WinPE manually” button and add some necessary drivers and retry.
Q: Why you get the message “Restored failed (error code:32781)” when you deploy images?
A: Maybe there is no network card driver or the network card driver on the client computer is not recognized.
Please open the Image Deploy tool, click the “Create bootable WinPE manually” button and add some necessary drivers. And then, please retry to deploy the image again.
Q: Why you can just restore one disk of the backup image which has several disks?
A: If the one disk backup image has multiple disks, the software just supports to restore the first one of that disk backup image.
Q: Why the disk format of the client computer sometimes is changed from GPT to MBR or from MBR to GPT after restore?
A: When you restore the backup image to the client computer, the software will delete all the data in the destination and then change the disk format of the client computer to be the same as the disk format of the backup image. For example, if the disk is MBR in the backup image but the target disk is GPT in the client computer when the software does the restore, the disk in the client computer will be changed to MBR. If the disk format is the same, the software will directly continue to create the partition to do the restore. Therefore, the disk format of the client computer must be the same as the one in the backup image. If not, the software will change it automatically.
Q: How to ensure that the client computer is bootable after restoring the system image or disk backup image?
A: 1. Please check if the boot mode in BIOS is consistent with the restored disk or system. If the restored disk is GPT, the boot mode must be EFI/UEFI. If the restored disk is MBR, the boot mode is legacy.
2. Please ensure that the computer name and the IP address you set for the client computer are not used by another computer in the same LAN. If they are used by another computer and this computer is on, when you boot the client computer you will get the error message that the computer name and the IP address conflict with another computer which is in the same LAN.
Q: Why the Windows PE ISO made with the AOMEI Backupper cannot be used by the AOMEI Image Deploy software to deploy the system?
A: Because that only the Windows PE made with AOMEI Image Deploy software can communicate with the AOMEI Image Deploy server. Please use the AOMEI Image Deploy to do the Windows PE ISO file. In addition, the AOMEI Image Deploy cannot recognize the Windows PE ISO made with other software.
Q: Why the server shows that the client computer information is that “Respond to boot request” and the client computer is stuck on this page that “PXELINUX 6.03 lwIP Copyright (c)1994-2014 H.Peter Anvin et al -” all the time?
A: Usually, you encounter this problem because you use the “Enable DHCP” feature but the IP address of client computer allocated by the DHCP server is same with (conflicts with) the one of another computer which is running in the same LAN. We advise you to turn off that running another computer or change the IP address of that computer. Then please reboot the client computer to do the operation again.