Prepare your OS image for layering in Azure 编辑

This topic explains how to prepare a clean OS image for import into a new OS layer. Before you start, make sure that you meet the requirements. While preparing the image, you can Expedite Microsoft Ngen.exe operations, if you think it is taking too long.

If using Windows 10 and not running Citrix Provisioning, machine creation, or View, you can speed up desktop start times by removing Windows 10 built-in applications. However, we recommend removing the apps on a new version of the OS layer, not in the OS image itself.

Note:

Do not use an unattend file with a Machine Creation Services (MCS) Azure connector. The App Layering software removes the unattend file if it is present, because it is not necessary or recommended for an MCS Azure connector.

Install the OS on a virtual machine

1. In the Microsoft Azure portal, create a new virtual machine from the Windows Server Remote Desktop image by selecting: New > Compute > Virtual Machine

2. Complete the Create virtual machine wizard:

   Basics:

   • Name: The name you specify for the new machine must comply with Azure naming conventions.
   • Username and password: The user name and password of the new server machine you specify are used for any packaging machines that are created containing this OS layer.
   • Resource group location: Be sure that the value for the Resource group location matches the Storage account location that you configured in the connector configuration.
3. Select required network settings.
4. Review the summary and create the virtual machine.
5. Log into the new virtual machine, and reboot the machine.
6. Install all important updates. Be sure to reboot the system and check for more updates. Some updates become available only after others are installed.
7. Run Windows Ngen.exe.
8. Remove or rename the Unattend file in C:\Windows\OEM.
9. Clear Windows Automatic Updates by selecting: Control Panel > System and Security > Windows Update > Change Settings
10. Ensure that this machine is not joined to a domain.
11. Enable the built-in administrator and check Password never expires.

12. If this is a server OS, run the following commands in PowerShell:

    Set-ExecutionPolicy Unrestricted
    Enable-PSRemoting
    <!--NeedCopy-->