1. Virtualization Infrastructure Administration Hyper-V 2012 R2 Jakub Yaghob

2. Building our own (virtualized) infrastructure – Hyper-V acheron HVADx HVx1HVx2HVx3 virtsan 10.250.x.1 GW: 10.2.0.1 Mask: 255.255.0.0 DNS1: 195.113.19.71 DNS2: 195.113.19.77 10.250.x.210.250.x.3 10.251.x.110.251.x.210.251.x.3 10.251.0.1 10.2.2.x 10.250.x.250 10.252.x.y internet port: 112x HVSCMx 10.250.x.249

3. W2012R2 installation for AD Deploy template HVAD VM name HVADx Start HVADx Install W2012R2 (std+GUI) Install VMware tools (Guest->Install …) Typical Restart Setup the network cards Network “Kralicek azurit” has IP 10.2.2.x, Mask 255.255.0.0, GW 10.2.0.1, DNS1 195.113.19.71, DNS2 195.113.19.77 Network “Virt mgmt” has IP 10.250.x.250, Mask 255.255.255.0 Use MAC for network detection Enable remote access Access from anywhere using RDP to acheron.ms.mff.cuni.cz:112xx (e.g. 11203) Make updates

4. W2012R2 installation Add role “Active Directory Domain Services” Installs DNS server Promote server to the domain controller Create a new forest All DNS for all NICs will be set to 127.0.0.1 DNS server must forward foreign queries to the original DNS (195.113.19.71, 195.113.19.77) Check internet connectivity Add features “Failover clustering”, “Hyper-V management tools” Add role “Remote Access” Configure router for NAT from 10.250.x.0 to 10.2.2.x Update Hyper-V core servers

5. Hyper-V core server installation Deploy template HVcore VM name HVxy Start HVxy Install Hyper-V Install VMware Tools D:\setup64 Set computer name to HVxy Configure all NICs “Network settings” Use “ipconfig /all” for detecting MAC/IP pairs All NICs have static IP “Virt mgmt” - 10.250.x.y, mask 255.255.255.0, GW 10.250.x.250, DNS 10.250.x.250 “Virt SAN” - 10.251.x.y, mask 255.255.0.0 “Virt vmotion” - 10.252.x.y, mask 255.255.255.0 Join the domain Set the time zone Configure iSCSI Run “iscsicpl” “Discovery” ->”Discover portal” -> 10.251.0.1 “Targets” -> “Connect” (add to favorite targets) “Volumes and devices” -> “Auto Configure”

6. Failover cluster Running on HVADx Add HVxy servers Add feature “Failover clustering” to all HVxy Set iSCSI disks for HVxy Select HVx1, bring online both disks, initialize (remove VMware GPT), format (no letter assigned) Bring online both disks on all other HVxy Failover cluster manager “Validate configuration” Add HVxy servers Go through validation Create cluster Creates another virtual network card, IP 10.250.x.100 Mark the small disk as “Witness in Quorum” (cluster context menu→Configure cluster quorum settings) Mark the big disk as “Cluster shared volume”

7. Hyper-V manager Running on HVADx Configure Hyper-V for each node HVxy Enable “Live migration” Add incoming live migrations IP 10.252.x.y, mask 255.255.255.0 Create virtual switches Failover cluster manager “Roles” -> “Virtual machines” -> “New VM” Set VM location to the clustered big volume Set remaining VM attributes Manage clustered VM from “Failover cluster manager” of from “Hyper-V manager”

8. Hyper-V system center manager – preinstall Deploy template HVSCM VM name HVSCMx Start HVSCMx Install W2012R2 Install VMware tools (Guest->Install …) Setup the network cards Network “Virt mgmt” has IP 10.250.x.249, Mask 255.255.255.0, GW 10.250.x.250, DNS 10.250.x.250 Update windows Add the server to the domain Login as domain admin Download and install Windows Assessment and Deployment Kit http://go.microsoft.com/fwlink/?LinkID=302319 Only “Deployment tools” and “Windows PE” required Install SQL Server 2012 [CX-slow-small] ISO/VI/en_sql_server_2012_standard_edition_with_service_pack_2_x86_dvd_46 89483.iso

9. Hyper-V system center manager – base install Create new administrative users in domain scm-admin scm-adder Set scm-admin account as local administrator for HVSCMx Set both accounts as local administrators for HVxy Restart HVxy Create a new container for distributed key management in domain Use ADSI Edit VMMDKM, full access for scm-admin, scm-adder Mount DVD with SCM [CX-slow-small] ISO/VI/ mu_system_center_2012_r2_virtual_machine_manager_x86_and_x64_dvd_2913737.iso Install SCM VMM Use scm-admin as a “Run As” service user Use VMMDKM as distributed keys container CN=VMMDKM,DC=dom2,DC=dom1 Run the VMM console Add Hyper-V hosts Use cluster IP/name Use scm-adder as a “Run As” user