Difference between revisions of "Azure"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
= Not supported roles and services = | = Generalising Windows before creating an image = | ||
# Create Windows VM | |||
# Baseline your VM by RDPing and installing software | |||
# Generalise your system using sysprep to create System Out-of-Box Experience (OOBE) | |||
## Win+R, type sysprep, it will take you to <tt>C:\Windows\System32\Sysprep</tt> and run <tt>sysprep.exe</tt> | |||
##* System Cleanup Action: Enter System Out-of-Box Experience (OOBE) | |||
##* Generalize: Yes (tick) | |||
##* Shutdown Options: Reboot | |||
## Optional run: <code>C:\Windows\System32\Sysprep\sysprep.exe /oobe /generalize /shutdown /mode:vm</code> | |||
## You will be disconnected from RDP but the instance still run generalising and will stop once done | |||
= Not supported server roles and services = | |||
This section has been updated on 26/09/2018, for upto date information see [https://support.microsoft.com/en-us/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines 1]. | This section has been updated on 26/09/2018, for upto date information see [https://support.microsoft.com/en-us/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines 1]. | ||
Revision as of 14:57, 6 October 2018
Generalising Windows before creating an image
- Create Windows VM
- Baseline your VM by RDPing and installing software
- Generalise your system using sysprep to create System Out-of-Box Experience (OOBE)
- Win+R, type sysprep, it will take you to C:\Windows\System32\Sysprep and run sysprep.exe
- System Cleanup Action: Enter System Out-of-Box Experience (OOBE)
- Generalize: Yes (tick)
- Shutdown Options: Reboot
- Optional run:
C:\Windows\System32\Sysprep\sysprep.exe /oobe /generalize /shutdown /mode:vm
- You will be disconnected from RDP but the instance still run generalising and will stop once done
- Win+R, type sysprep, it will take you to C:\Windows\System32\Sysprep and run sysprep.exe
Not supported server roles and services
This section has been updated on 26/09/2018, for upto date information see 1.
The following roles are not supported on Microsoft Azure virtual machines:
- Dynamic Host Configuration Protocol Server
- Hyper-V (Hyper-V role is supported in Azure Ev3, and Dv3 series VMs only)
- Rights Management Services
- Windows Deployment Services
- Windows Server features
The following significant features are not supported:
- BitLocker Drive Encryption (on the operating system hard disk, may be used on data disks)
- Internet Storage Name Server
- Multipath I/O
- Network Load Balancing
- Peer Name Resolution Protocol
- RRAS
- DirectAccess
- SNMP Services
- Storage Manager for SANs
- Windows Internet Name Service
- Wireless LAN Service
Azure for AWS Administrators
Resources
- What is and can't be suppoerted on Azure Windows systems
- Minimum version support for Linux and Windows virtual machine agents in Azure Linux systems