Difference between revisions of "Azure"
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
		
	
| Line 46: | Line 46: | ||
*Wireless LAN Service  | *Wireless LAN Service  | ||
= Azure tools =  | |||
* blob storage  | |||
* Powershell AZModule to copy files  | |||
* Powershell DSC Desired State Configuration system  | |||
* VMagent custom script extension - runs on Azure VMs, allows to run one-off scripts   | |||
= Resources =  | = Resources =  | ||
*[https://support.microsoft.com/en-us/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines What is and can't be suppoerted on Azure] Windows systems  | *[https://support.microsoft.com/en-us/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines What is and can't be suppoerted on Azure] Windows systems  | ||
Revision as of 09:35, 6 November 2018
Generalising Windows machine before creating an image
- Create Windows VM
 - Provision/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
 - Go to Azure portal and click on Capture to create an image now
 - You find new image in Images service where you can create new VM from
 
Generalising Linux machine before creating an image
- Create Linux VM
 - Provision/baseline your VM by SSHing to provisioning your software
 - Generalise your system using Azure Linux Agent - waagent
sudo waagent -deprovision+user- account you are currently logged in will be completly deleted including home
 - Linux system does not neet to be shut
 
 - Go to Azure portal and click on Capture to create an image now
 - You find new image in Images service where you can create new VM from
 
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 tools
- blob storage
 - Powershell AZModule to copy files
 - Powershell DSC Desired State Configuration system
 - VMagent custom script extension - runs on Azure VMs, allows to run one-off scripts
 
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
 
- Azure for AWS Administrators