Microsoft



MSI 20 LAB NOTESThe labs associated with the MSI20 session can be completed in a trial Azure subscription and optionally add on-premises servers. LAB DEPLOYMENTIntroduction. With these preparation steps, you will deploy the necessary environment that will allow you to perform the demo exercises present in the MSI20 video.RequirementsYou will need to have a Windows Admin Center installation and a Hyper-V server for the Azure Site Recovery Demo (DEMO 1) and additional file servers for Azure File Sync (DEMO 3). For the rest of the demos you can also use a Windows Admin Center server deployed In Azure. You can deploy the File servers as well the Hyper-V server for ASR in Azure. In this case the Azure VM running Hyper-V will use nested virtualization ().When signed in to a newly created Azure subscription, create the prime.admin account. Assign this account global administrator permissions. Make a note of the yoursubscription. suffix and substitute where appropriate when running the setup code below.Navigate to portal. and sign into the demo Azure tenancy with the prime.admin@yoursubscription. account.If you don’t have a Windows Admin Center (WAC) server on-premises, you can deploy a WAC server in Azure. To create the Windows Admin Center VM used in this session’s labs, open Cloud Shell (PowerShell) and enter the following commands at the prompt, pressing Enter after each line:cd ~# Navigate to your home directorycd ~ # Download fileInvoke-WebRequest -Uri -OutFile Deploy-WACAzVM.zip # Expand Zip fileExpand-Archive ./Deploy-WACAzVM.zip # Change Directorycd Deploy-WACAzVM# Deploy WAC$ResourceGroupName = "demo-wac-rg"$VirtualNetworkName = "wac-vnet"$SecurityGroupName = "wac-nsg"$SubnetName = "wac-subnet"$VaultName = "wac-key-vault"$CertName = "wac-cert"$Location = "westeurope"$PublicIpAddressName = "wac-public-ip"$Size = "Standard_D4s_v3"$Image = "Win2019Datacenter"$Credential = Get-Credential $scriptParams = @{ResourceGroupName = $ResourceGroupNameName = "wac-vm1"Credential = $CredentialVirtualNetworkName = $VirtualNetworkNameSubnetName = $SubnetNameLocation = $LocationSize = $SizeImage = $ImageGenerateSslCert = $true}./Deploy-WACAzVM.ps1 @scriptParamsIn the Azure Virtual Machine blade you can now connect to your wac-vm1-OPTIONAL: You can also expose port 443 from that VM so you can access it via the browser.Register your gateway with Azure. The first time you try to use an Azure integration feature in Windows Admin Center, you will be prompted to register the gateway to Azure. You can also register the gateway by going to the Azure tab in Windows Admin Center Settings. The guided in-product steps will create an Azure AD app in your directory, which allows Windows Admin Center to communicate with Azure.Additional Documentation and ResourcesMicrosoft Docs: Deploy Windows Admin Center in Azure : Deploy Windows Admin Center in Azure Microsoft Docs: Connecting Windows Server to Azure hybrid services Docs: Configuring Azure Integration : Register Windows Admin Center with Azure and Videos: How to configure Azure Hybrid Services in Windows Admin Center 1: Azure Site RecoveryDemo Requirements:1 Windows Admin Center server1 Hyper-V server2 Virtual Machines running on the Hyper-V serverIntroduction. In this demonstration, you will show the replication of a Hyper-V virtual machine to Azure.Open the Windows Admin Center portal and connect to the Hyper-V server.Got to the Virtual Machine extension in the menuClick on Virtual Machine Inventory, here you can see a list of virtual machines running on this Hyper-V server.Select the first virtual machine. This virtual machine has no ASR configuredClick on more and click on Protect VMIn the sidebar you can show the subscription, resource group, Azure recovery vault and storage account.Close the blade by clicking on cancel.Select the second virtual machineShow that the virtual machine is protected.Click on the Protected link which opens the Azure portal.Here you can see the virtual machine which is replicated.Review the state of the virtual machine which should healthy and protectedClick on the virtual machine and review the overview pageClick on additional setupReview the settings for the additional setup, like computer name, vm size, resource group and virtual networkClick on back to go back to the virtual machine overviewShow the Failover options (Test Failover, Failover, Planned Failover)You can keep the browser windows open for the next demosDEMO 2: Azure Update ManagementDemo Requirements:1 Windows Admin Center server1 Azure VM which is already joined to Azure Update Management1 Secondary VM in Windows Admin Center which is already joined to Azure Update ManagementInstalled Azure Update Management in Azure with a Log Analytics Workspace and Automation Account.A previous update deployment job from the past to review at the end of the demo.Introduction. In this demonstration, you will view and set up Azure Update Management by using Windows Admin Center and show that you can asses and deploy updates to Azure and non-Azure VMs.In the Azure Portal, open up the Automation account in the Azure Portal which you use for update management.Show that you already have an Azure VM managed by this Automation accountShow that you can add additional Azure and non-Azure VMs directly from the portalOpen Windows Admin Center and click on the machine you want to add to Azure Update ManagementIn the extension menu, go to UpdatesHere you can click on Update Now to set up Azure Update ManagementIn the Blade configure the Subscription, Resource Group, Log Analytics Workspace and Automation account.Click ok, to add the serverThis will take a couple of minutes, why you already have a second server joined to Azure Update Management in advanceOpen the Azure Portal with the Update Management solution in the Azure Automation account.Show that you have an Azure and a non-Azure VM in the portalYou can show that the non-Azure VM is not compliant with the update policy. If both VMs are not compliant this is also great.Click on Schedule Update Deployment and configure the update deploymentEnter a name for the Update DeploymentSelect Windows Select the machine you want to add to the update deployment. You can add the Azure and the non-Azure VMClick saveSchedule the Update Deployment for a time in the future. Show that you also have a recurring option.Review the reboot optionsSchedule the update deployment.You can now review the history tap, where you can see past update deployments.Click on one of the update deployments and show the machines and updates which were affected by this deployment.DEMO 3: Azure Update ManagementDemo Requirements:1 Windows Admin Center server2 File Servers, one of the File Server is already configured with Azure File SyncAzure File Sync service and an Azure File ShareIntroduction. In this demonstration, you will view and set up Azure File Sync and show how files can be synced between a file server and a Azure File Share. You will also add a second server to the file sync service.Connect to FS01 (File Server 1) using RDPShow the files on the fileshare of FS01Open the Azure PortalOpen the Azure File Sync service you have createdShow the Cloud Endpoint (Azure File Share) and the server endpoint FS01 listed in the Azure portal.Open the Storage account and the Azure File Share in the Azure PortalReview the Files stored on this Azure File Share. They are the same files as on FS01.Open FS01 again and create a new Folder called Folder1 in the file share folderSwitch back to the Azure portal and review the Azure File Share, it will now have the new folder1 syncedConnect to FS01 (File Server 2) using RDPShow the empty file shareOpen Windows Admin Center and select Azure File Sync from the extensions menuClick on Setup Azure File SyncInstall the Azure File Sync agentRegister the server to the Azure File Sync service.Select the right subscriptionResource Group Sync serviceClick on register server.Switch back to the Azure PortalAdd a server endpoint to the sync service.Select FS02 and add the local file share of FS02.Configure Cloud TieringClick save.Review the newly added server endpoint in the Azure Portal File Sync service. You will now see the Cloud endpoint with the Azure File Share and two server endpoints, FS01 and FS02.Review the state of FS02 that it is healthyConnect again to FS02 using RDPReview the file share on FS02. It will now show all the files.Create a new folder called Folder2Open the Azure Portal and switch to the Azure File Share.Review the Azure File Share, it will now also show Folder2Open the RDP connection to FS01Review the file share on FS01, it will now also show Folder2 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download