Deploying an Administrative Image
This article will walk you through the steps to Deploy your Admin Image once you have created and set it up.
After you've created and set up your Admin Image, the last step is to deploy it. There are two different methods to select for deployment: Manually and Automatically
Deploy Manually
Within the Administrative Image Option Editor, the Deploy Manually tab will present an option to send an email containing a link to the StartSWInstall.hta file inside the root image folder.


To help minimize network bandwidth, it is best to schedule availability to the image.

Also, unless 'Run as a different user' was selected earlier under Administrative Options, then the client user account must have full administrative permissions.
Most importantly, Ensure the user has Read permissions to the entire admin image folder structure on the server. Read/write permissions may be required to [Image folder]\x64\logs if the option to create diagnostics logs was enabled earlier.
Deploy Automatically

The automatic deployment process uses Microsoft Task Scheduler to run the installation with the 'LocalSystem' account. To do this, requires client credentials with administrative permissions. On the network, the account will be represented as a computer security principle. The following accesses will be required for the computer security principle:
- Read access to the Admin Images folder
- Read and write access to the Admin Images folder\x64\logs folder\
When you add a computer to a group of a Shared Folder in the Active Directory, be sure to select Object Types and Computers.
Also, the computer serving serving the admin image and the client machines must both be members of the same Active Directory domain.
Same as the Manual Deployment, installation time can be scheduled for network bandwidth control.