Good Morning Wireless! SSID: Wal_Classroom Password: nepats.1 1 Windows Server 2012 & Windows Azure Infrastructure Services (IaaS) , MCT, MCSA, MCITP, MCSE… Microsoft – Technology Evangelist http://ITProGuru.com @itproguru CT, MA, ME, NH, VT, NY (upstate) http://blogs.technet.com/DanStolts More Jobs Owner - Bay State Integrated Technology, Inc. (www.BayStateTechnology.com) President - Boston User Groups (www.BostonUserGroups.org) Leader – Cub Scouts Pack 14, Lakeville, MA {LakevillePack14.com) Founder/Chairman - Virtualization Group Boston (www.VirtG.com) @ITProGuru Today’s Agenda IT-Lab (1/2 day) 9:00 - 10:15 – Windows Server 2012 and Windows Azure Infrastructure Services 10:15 - 10:25 – Break 10:25 - 11:45 – HOL - Windows Azure Infrastructure Hands-On 11:45 - 12:00 - “Evaluations and Drawing 3 90-Day Free Trial contains •compute / 750 small compute hours per month •web sites / 10 web sites •mobile services / 10 mobile services •relational database / 1 SQL database •SQL reporting / 100 hours per month •storage / 35GB with 50,000,000 storage transactions •data transfer / unlimited inbound & 25GB outbound •media services encoding / 50 GB (input & output combined) •cdn / 20GB outbound with 500,000 transactions •cache / 128MB •service bus / 1,500 relay hours and 500,000 messages Fundamental gains for server applications SQL transactions/s 4270 (98%) 5000 4315 (100%) 4000 3000 2000 1175 (27%) 1000 0 SMB SMB + DAS Live Migration – Moving a Running VM without Shared Storage standard Ethernet connection 1. Live Migration setup occurs 2. Memory pages are transferred from the source server to the destination server 3. Modified pages are transferred to destination server 4. State is transferred to destination server 5. VM brought online on destination server 6. Network cleanup occurs What is Hyper-V Replica? A virtual machine level replication solution which efficiently replicates data over a LAN/WAN to a remote (Replica) site without relying on software or hardware technologies outside of the Windows Server 2012 operating system New in Windows Server 2012 Hyper-V Role Storage and Workload agnostic Servers can be standalone or members of a Failover Cluster Servers can be members of a workgroup or a domain (same or different); Primary and Replica servers do not need to be in the same domain unless part of a Failover Cluster • Managed locally (Hyper-V Manager) or remotely (Hyper-V Remote Server Administration Tools (RSAT) or System Center Virtual Machine Manager (SCVMM) • 4 Deployment Scenarios • Head Office and Branch Office (HO-BO) • Enterprise Datacenter • Hosting Provider Datacenter • Customer Office and Hosting Provider Datacenter (CrossPremise) • • • • Where are we at today? Cloud Models If deploying an application requires a developer’s involvement, it’s not IaaS Microsoft approach: hybrid cloud Broad & deep array of solutions enables customers to use cloud in their own way, at their own pace Windows Server 2012 Datacenter Windows Server 2008 R2 SP1 SQL Server 2012 SP1 (Std or DC) SharePoint Server 2013 Trial BizTalk Server 2013 and more! openSUSE 12.3 CentOS 6.3 Ubuntu 12.04 Ubuntu 12.10 SUSE Linux Enterprise Server SP2 and more! Virtual Machine Sizes VM Size Extra Small (A0) CPU Cores RAM Bandwidth Shared 768 MB # Data Disks Price Per Hour Price Per Hour (GA Price Starting Jun 1st) (Promotional Price Until May 31st) 1 $0.02 $0.0133 (~$15/month) (~$10/month) $0.09 $0.08 (~$67/month) (~$60/month) $0.18 $0.16 (~$134/month) (~$119/month) $0.36 $0.32 (~$268/month) (~$238/month) Small (A1) 1 1.75 GB 100 2 Medium (A2) 2 3.5 GB 200 4 Large (A3) 4 7 GB 400 8 Extra Large (A4) 8 14 GB 800 16 $0.72 $0.64 (~$536/month) (~$476/month) A6 4 28 GB 1,000 8 (~$759/month) A7 8 56 GB 2,000 16 $1.02 $2.04 (~$1,518/month) N/A N/A Active Directory DC DNS Persistent VM Role SharePoint Persistent VM Role SQL Persistent VM Role Active Directory DC DNS • • • • • • • SharePoint PaaS Roles File Servers Local AD SQL VMs Overview of the Portal When you first login to Windows Azure you have a blank slate to work from. For today’s lab we will be utilizing the Virtual Machines and Network sections of Azure. Building the Storage Account Now we need to create a storage account so that all of our new VMs will share the same container. This makes matters much easier for moving, deprovisioning, and such. Click on Storage, then select New. Click on Quick Create, provide a name for your storage. Geo-Replication has the ability to mirror data to other regions of the U.S. However this costs additional money so for this lab we will uncheck the box, click on the checkmark to finish: Registering the DNS Server First we need to register a DNS Server that our lab will utilize. Register the internal IP address that our domain controller VM will be using for Active Directory-integrated Dynamic DNS services. Registering the DNS Server Provide a name for the DNS server and for this exercise we will use the I.P. address of 10.0.0.4. Be sure that the proper subscription is selected, then click Register DNS Server. Building the Virtual Network Now we will create a virtual network. This virtual network will serve as a subnet that all of our virtual machines will connect to. Building the Virtual Network Provide a name for the virtual network, and also the affinity group unless you have already created one in previous labs. Be sure to select the appropriate region as this impacts where your workloads will run geographically. Click on the arrow to proceed. Building the Virtual Network Select the DNS Server registered in the previous steps. Click on the arrow to proceed. Building the Virtual Network We need to select a proper subnet scheme, for this lab we will be choosing 4096 possible addresses. The CIDR equivalent is 20. Click on the check mark to proceed. Operations Status Notice that during any action sequences in the Azure Portal the operations will show up at the bottom of the screen explaining the progress. When each process is complete you can clear the operation by clicking on the OK checkmark. Minimize this panel and it can be recalled at any time by clicking on the icon at the bottom of the screen. Building the First Virtual Machine Notice there are three sub sections to the Virtual Machines area of the portal. Instances, Images, and Disks. We will select Create a Virtual Machine to proceed Building the First Virtual Machine Select Virtual Machine, and use the “From Gallery” option. Consider the “From Gallery” option as the more advanced or custom option for deploying VMs. Click on the Create A Virtual Machine checkmark to proceed. Building the AD Virtual Machine Select Windows Server 2012 Datacenter Click on the Arrow to proceed. Building the AD Virtual Machine The Version Release Date is a great feature in that you can deploy Windows Server 2012 based on update rollups. So the April 24th selection would include all updates to that point. Choose the most recent version. Provide a machine name, set the Size of the VM to Small, add an admin user account, and password. Note the password must have 8 characters and is utilizing a more secure password(special characters, upper and lower case, numeric) is suggested. Click on the arrow to proceed. Building the AD Virtual Machine Provide a DNS name, this name will be checked to see if it already exists in the DNS database for cloudapp.net. In the event the name of the VM is already in user append a character or modify the DNS name. Select the previously created Storage Account. Select the Virtual Network we previously set up. Check that the subnet looks accurate. Click on the arrow to proceed. Building the AD Virtual Machine We will not be creating an Availability Set in this session so as to keep costs down. Availability Sets are in place to insure that VMs are available in other regions geographically in the event of an outage. Ensure the “ENABLE POWERSHELL REMOTING box is checked. Click on the Check to complete the creation of the VM. Building the AD Virtual Machine Scroll down on the Status screen for the newly created VM. Check to make sure the IP address is 10.0.0.4(this was automatically assigned to the VM.) Notice that the Size is set to Small granting us 1.75 GB of Memory. Adding a Virtual Disk to the AD Machine We need to add a disk to the VMs now, so we will start with the AD controller. Why? Because Azure OS disks have write cache enabled, so in the event of an outage some data might get lost. By adding a new empty data disk, these disks are safe from data loss as the data is written directly to the virtual disk. From the summary page, click on Attach and then select “Attach Empty Disk” Adding a Virtual Disk to the AD Machine Rename the virtual disk by appending data01 in place of the random characters which are normally auto-generated. Make the disk 10GB in size. Select “None” for the Host Cache Preference Click the Check to complete the disk addition. Connecting to the AD server via RDP Now we need to connect to the AD server via RDP to complete the disk addition and kick off the Active Directory role installation. Click on the virtual machine and then click on “Connect” Connecting to the AD server via RDP A RDP file will display at the bottom of the screen. This RDP connection comes preconfigured with the randomized TCPIP port which is now required for security purposes. Click on Open Connecting to the AD server via RDP Select the checkbox to disable this warning if desired. Click “Connect”: Enter the admin credentials which were supplied during the VM creation process and then click OK: Disable the warning if so desired and click “Yes”: Creating the Data Volume on the AD server Once inside Server Manager, go to Tools then select Computer Management. Inside Computer Management select Disk Management. An “Initialize Disk” window will pop up, make sure the new disk is selected and click OK. Creating the Data Volume on the AD server Right click Disk 2 and select “New Simple Volume…” Click Next: Creating the Data Volume on the AD server Change the Volume Label to DATA and click Next: Click Next: The drive letter should be preconfigured to “F”, click Next: Click Finish: Installing Active Directory on the AD Server Jump back into the RDP Session for the AD Server, click on Manage then select “Add Roles and Features”: Click Next: Click Next: Installing Active Directory on the AD Server Notice that the only server displayed is the local server. Later on we will add other servers to manage in this same Server Manager console. Make sure the server is selected and click Next. Select Active Directory Domain Services, the subsequent pop-up window tells us that the management tools will also be installed, click “Add Features” then click “Next”: Installing Active Directory on the AD Server Since no other features are required for this server we will select “Next” to continue: Now we click on “Next” to continue through the Active Directory Domain Services configuration: Installing Active Directory on the AD Server Server Manager will reboot the server automatically if desired selected the checkbox, and click on Yes to the pop-up window. Next click on Install: Be sure that the installation completes then click on Close: Installing Active Directory on the AD Server Server Manager will notify you that there are tasks left to be completed or if errors have occurred via the Flag at the top of the screen. Click on the flag then notice it is prompting us to promote the server to a domain controller. Since DCPromo has been deprecated in Server 2012 we will use this option to move forward: Installing Active Directory on the AD Server Select “Add a New Forest”, enter in a Domain name, for this exercise I use “contoso.com”. Click Next: Enter a Password and then click Next: Installing Active Directory on the AD Server Ignore the DNS error message and click Next: Verify the NETBIOS name and click Next: Installing Active Directory on the AD Server Change the drive path to the F drive for all 3 entries leaving the subfolders path intact. Click Next: Notice that you can view the PowerShell script for this installation by clicking “View script”, otherwise click Next: Installing Active Directory on the AD Server The prerequisites check will display any issues that might need to be addressed. The messages you will see can be ignored during this installation. DNS will be installed automatically. Click Install: The server will automatically reboot when the operation is completed. Building the Web Virtual Machine Select Create a Virtual Machine to proceed: Building the Web Virtual Machine Select Virtual Machine, and use the “From Gallery” option. Consider the “From Gallery” option as the more advanced or custom option for deploying VMs. Click on the Create A Virtual Machine checkmark to proceed. Building the Web Virtual Machine Select Windows Server 2012 Datacenter Click on the Arrow to proceed. Building the Web Virtual Machine The Version Release Date is a great feature in that you can deploy Windows Server 2012 based on update rollups. So the April 24th selection would include all updates to that point. Choose the most recent version. Provide a machine name (xxxxlabweb01), set the Size to Small, choose an admin user account, and password. Note the password must have 8 characters and is utilizing a more secure password(special characters, upper and lower case, numeric) is suggested. Click on the arrow to proceed. Building the Web Virtual Machine Provide a DNS name, this name will be checked to see if it already exists in the DNS database for cloudapp.net. In the event the name of the VM is already in user append a character or modify the DNS name. Select the previously created Storage Account. Select the Virtual Network we previously set up. Check that the subnet looks accurate. Click on the arrow to proceed. Building the Web Virtual Machine We will not be creating an Availability Set in this session so as to keep costs down. Availability Sets are in place to insure that VMs are available in other regions geographically in the event of an outage. Ensure the “ENABLE POWERSHELL REMOTING box is checked. Click on the Check to complete the creation of the VM. Adding a Virtual Disk to the Web Machine We need to add a disk to the VMs now, so we will continue with the Web controller. Why? Because Azure OS disks have write cache enabled, so in the event of an outage some data might get lost. By adding a new empty data disk, these disks are safe from data loss as the data is written directly to the virtual disk. From the summary page, click on Attach and then select “Attach Empty Disk” Adding a Virtual Disk to the Web Machine Rename the virtual disk by appending data01 in place of the random characters which are normally auto-generated. Make the disk 10GB in size. Select “None” for the Host Cache Preference Click the Check to complete the disk addition. Building the File Server Virtual Machine Notice there are three sub sections to the Virtual Machines area of the portal. Instances, Images, and Disks. We will select Create a Virtual Machine to proceed Building the File Server Virtual Machine Select Virtual Machine, and use the “From Gallery” option. Consider the “From Gallery” option as the more advanced or custom option for deploying VMs. Click on the Create A Virtual Machine checkmark to proceed. Building the File Server Virtual Machine Select Windows Server 2012 Datacenter Click on the Arrow to proceed. Building the File Server Virtual Machine The Version Release Date is a great feature in that you can deploy Windows Server 2012 based on update rollups. So The March 26th selection would include all updates to that point. Choose the most recent version. Provide a machine name (xxxxxlabfile01), user account, and password. Note the password must have 8 characters and is utilizing a more secure password(special characters, upper and lower case, numeric) is suggested. Set the size to Small. Click on the arrow to proceed. Building the File Server Virtual Machine Provide a DNS name, this name will be checked to see if it already exists in the DNS database for cloudapp.net. In the event the name of the VM is already in user append a character or modify the DNS name. Select the previously created Storage Account. Select the Virtual Network we previously set up. Check that the subnet looks accurate. Click on the arrow to proceed. Adding a Virtual Disk to the File Machine We need to add a disk to the VMs now, so we will finish with the File controller. Why? Because Azure OS disks have write cache enabled, so in the event of an outage some data might get lost. By adding a new empty data disk, these disks are safe from data loss as the data is written directly to the virtual disk. From the summary page, click on Attach and then select “Attach Empty Disk” Adding a Virtual Disk to the File Machine Rename the virtual disk by appending data01 in place of the random characters which are normally auto-generated. Make the disk 10GB in size. Select “None” for the Host Cache Preference Click the Check to complete the disk addition.