AOMEI Image Deploy

Creating Images


Recommended to use only when 4-5 or more computers need to be imaged.

AOMEI requires a .adi file extension, so you cannot use Acronis images

Before booting, make sure BitLocker/Device encryption is off & secure boot + legacy boot is disabled

Use the AOMEI Backupper USB and boot into it

Once inside follow these instructions:
  1. Backup
  2. Disk backup
  3. Select source (C drive or Disk 0)
  4. Change the destination to be the external drive
  5. Start backup
  6. Once finished, click exit
  7. Rename the image later (You cannot change the name beforehand to my knowledge)



Deploying Images


Make sure secure boot/legacy boot is off and PXE boot/IPv4 boot is enabled (it should be automatically) as well as device encryption is off (it should be off automatically unless you are reimaging)

Make sure the server computer with AOMEI Image Deploy is connected to the switch and all the computers to have an image deployed to are connected before turning them on

Run AOMEI Image Deploy
  1. Select “Create bootable WinPE ISO or WIM automatically”
  2. Check "Enabled DHCP" box and continue
  3. Once the PXE service has started, boot the target computers into IPv4 boot
  4. Wait for the files to download, usually takes about 6-10 minutes.
  5. Once the target computers have loaded and appear online on Image Deploy, click the “I confirm all the client computers which need to be deployed are online” box and click next
 6. When selecting the file, click browse and enter the file address by using "\\Server IP\folder name". Uncheck the anonymous box and enter the username and password of the computer.
      Note: the Server IP is the IP given by DHCP of the computer that Image Deploy is running on
 7. Select the image file and confirm the computers to be imaged
 8. Select destination disk as 0 and select the number of computers being deployed
 9. Start the deployment

Note: You will have to enable secure boot again once this is finished, images do not copy over BIOS settings


Troubleshooting tips


Some models may require specific drivers to be installed to work properly, like ethernet drivers. You will have to get the .inf file of the drivers and add those while using a WIM PE file to boot. This is done in the first screen of Image Deploy.

If you are getting different IPs, you may have two DHCP servers running, and will need to remove the extra one.

If image files are splitting, make sure the drive you are using to store them is NTFS formatted.

The firewall may have to be disabled on the server computer in order to connect.

The switch should have no VLANs.


Most other issues are either due to secure boot or legacy boot being enabled or device encryption still being on.
Creation date: 4/16/2026 12:40 PM (goslee@southern.edu)      Updated: 4/16/2026 12:44 PM (goslee@southern.edu)
get help Get help for this page