Image Management Wizard

Image Management Wizard

  • This feature is accessible in the left-hand side navigation panel of the new web console.
  • Here is the landing page for the new wizard:


  • This section corresponds to Collections of the golden image type in the previous Login AM 2016 UI
  • Select an existing Recipe or create a new one, then click the Next button
  • Now click the Import SCCM button in the Package List section

Am17 packagelist.png

Am17 importsccm.png

  • Input the server address and service account details
  • Upon connection, if there are no packages to convert, or if they have already been converted, you'll be presented with the following message:

Am17 sccmnonetoimport.png

  • If there are packages available to convert, they'll show as follows:

Am17 availablesccmpackages.png

  • You can drag any ready-to-convert packages to the column:

Am17 readytoconvertpackages.png

  • Then, in the Package List tab of the Image Management Wizard, you can drag the available package to the Recipe Packages column.

SCCM Import1.png

  • Packages already converted, show as follows in the Package List:

Am17 alreadyconvertedpackages.png

  • After selecting your chosen package, click on Connect (in the Target Platform section). This will retrieve the back-end environment information.


  • This displays the Virtual Machine section. You can select different specifications for the VM you want to deploy, as follows:


  • You can configure both vCPU and vMemory, as well as host, storage, network and template resources
  • When everything is configured correctly, click Next
  • You will then will be taken to the Credentials section:
  • Please enter your Active Directory Service Account details in the relevant fields.
    • The Service Account is used to add the machine to the domain in the specified Root OU. You must create the Root OU in Active Directory yourself with the appropriate permissions for the Service Account.
  • Please also enter the fully qualified domain name, e.g.
  • The template local credentials are used for the initial configuration steps inside the VM operating system.
  • When ready, click Connect.


  • You will then will be taken to the Image Capture section:


  • Sealing configuration here depends on the underlying technology in use
  • Default methods are available in the drop-down box
  • If you choose to Run a custom seal command, use the following fields to enter the necessary information: Seal command / Seal command arguments
  • Up next is the Overview section
  • Here you can review the configuration / metadata
  • If everything is correct, click Deploy
  • Up next is the Deployment section:

Image Management Progress1.png

  • This process utilizes both IIS and PowerShell. Underneath each task you can see its status, along with any error handling messages (if applicable)
  • The PowerCLI is utilized during deployment
  • You should be able to see the VM cloning in progress in vSphere now
    • You can find the prerequisites to configure a VM for cloning on our documentation site. Remote PowerShell must be enabled, but the VM doesn’t have to be domain-joined.
  • After cloning, the VM will start and be automatically assigned with an IP, so DHCP must be enabled in the environment
  • The VM will then be connected to AD, utilizing the Login AM service account (so this account must have the necessary rights)
  • After this, the VM will be initialized in terms of Login AM readiness
  • Then the packages will be installed after initialization and whatever else is configured (e.g. Windows updates)
  • Then the VM is sealed and shutdown