Hyper-V Labs part 5 Configuring the Replication broker

1.     Configure Replication broker

Introduction:

Windows Server 2012 has introduced a number of new features, Hyper-V replica allows standalone or clustered Hyper-V server to replicate at the VM level to other Hyper-V host regardless of their location and domain membership.  Hyper-V replica takes up to 15 snap shots of 5 minute intervals and replicates the snap shot to another host.

Purpose:

The purpose of this lab will be to configure the replication broker for the Hyper-V cluster to facilitate the replication of your virtual machines to another students cluster.

Estimate time of Lab: 10 minutes

**This lab will only be done by Student A ***

  1. Launch the Server Manager Dashboard
  2. In the top right hand corner of Server Manager select “Tools à Failover Cluster Manager”
  3. Expand TeamX.HVLAB.LOCAL
  4. Select Roles
  5. In the “Actions” pane select “Configure Role”
  6. On the “Before You Begin” page check the box “Do not show this page again” à Next
  7. In the “High Availability Wizard” on the “Select Role” page choose “Hyper-V Replica Broker” à Next
  8. In the “High Availability Wizard” on the “Client Access Point” page input TeamX-Rep in the name field (where X is your assigned team number)
  9. In the “Address field” input the IP address listed in your lab manual page 4 as broker IP in your assigned list à Next
  10. In the “High Availability Wizard” on the “Confirmation” page à Next
  11. In the “High Availability Wizard” on the “Summary” page à Finish
  12. Validate you have a new role called TeamX-Rep that is online
  13. Right click on the TeamX-Rep object and select “Replication settings”
  14. On the “Hyper-V Replica Broker Configuration” check “Enable this cluster as a Replica Server”
  15. On the “Hyper-V Replica Broker Configuration” check the box “Use Kerberos” and validate port 80 is selected
  16. On the “Hyper-V Replica Broker Configuration” under “Authorization and storage” enable “allow replication traffic from any authenticated server” and input c:\ClusterStorage\Volume1 for the default location of the replica files à Ok
  17. On the “Hyper-V Replica Broker Configuration” popup click Ok

Leave a Comment

Hyper-V Labs part 4 Installing Windows Failover Clustering and Cluster Creation

1.     Installing Windows Failover Clustering and Cluster Creation

Introduction:

Microsoft first introduced failover clustering in NT 4.0 and has been improving the viability and feature set of Windows Failover Clustering with each release of Windows Server.  In the past many organizations felt clustering was too complex and difficult to manage. Windows Server 2012 has simplified the installation and build process, making clustering and much less feared solution.

Purpose:

In this lab you will install Windows Failover Clustering on your Hyper-V host and configure a 2 node Hyper-V cluster to allow your virtual machines to be highly available.

Estimated time of Lab: 30 Minutes

*This lab is to be done by both students*

  1. Launch the Server Manager Dashboard
  2. Select Dashboard pane and choose “Add Roles and Features”
  3. On the “Select Installation Type” page select “Role-based or features based installation” à Next
  4. On the “Select destination server ” page select your server (Student X where X is your assigned student number) à Next
  5. On the “Select server roles” do NOT make any changes à Next
  6. On the “Select features” page click “Failover Clustering”
  7. On the “Add Roles and Features” popup windows select “Add features” à Next
  8. On the “Confirmation installation selections” page  à Install
  9. After installation has completed select “Close”

**Only Student A will perform these steps ***

  1. Launch the Server Manager Dashboard
  2. In the top right hand corner of Server Manager select “Tools à Failover Cluster Manager”
  3. In “Failover Cluster Manager”  from the actions pane select “Create Cluster”
  4. On the before you begin page select “Do not show this page again” à Next
  5. In the “Create Cluster Wizard” on the “Select Server” page input StudentX (where X is your assigned student number) à Add  à Next
  6. On the validation warnings page select the radius button “No” à Next
  7. In the “Create Cluster Wizard” on the “Access Point for Administering the Cluster” page under “Cluster Name” input TeamX (where X is your assigned number)
  8. Type the IP address assigned for you cluster in the address field à Next

*This address can be found in Environment information: on Page 6 of the workshop manual*

  1. In the “Create Cluster Wizard” on the “Confirmation” page à Next
  2. In the “Create Cluster Wizard” on the “Summary” page select “view report”. After reviewing the report close the report windows à Finish

** Only Student B will perform these steps once the previous steps have been completed by Student A  ***

  1. Launch the Server Manager Dashboard
  2. In the top right hand corner of Server Manager select “Tools à Failover Cluster Manager”
  3. In the Actions pane select “Connect to a cluster”
  4. In the “Select Cluster” windows under cluster name input TeamX (where X is the assigned team number) à Ok
  5. Expand the Node TeamX.HVLAB.LOCAL à Select Nodes
  6. In the actions pane select “Add Node”
  7. In the “Add Node” window on the “before you begin” check the box “Do not show this page again” à Next
  8. In the “Add Node Wizard” on the “Select Server” page input StudentX (where X is your assigned student number) à Add  à Next
  9. In the “Add Node” wizard on the “Validation warning” enable “no” à Next
  10. On the “Add Node wizard” on the confirmation page uncheck “Add all eligible storage to the cluster” à Next
  11. On the “Validate a configuration wizard” on the “Summary” page select “view report”
  12. Close the report à Finish
  13. Expand TeamX.HVLAB.LOCAL cluster
  14. Expand storage and select “Disks”
  15. Minimize Failover cluster manager
  16. Launch Server Manager
  17. In the top right hand corner of Server Manager select Tools à Computer Management
  18. Expand storage
  19. Select Disk Management à Right click  Disk2  (**Note this will be the 150GB disk) àOnline the disk
  20. Right click disk 2 (**Note this will be the 250GB disk) à Initialize disk (If you do not have this option skip to step 44)

*Since the storage is reused from previous workshops this step many not be required

  1. On the Initialize disk wizard validate disk 2 is selected and leave the defaults à OK
  2. Right click on the unallocated space à Select “New simple volume”
  3. On the New simple volume wizard à Next
  4. On the specify volume size leave the default settings à Next
  5. Select the radius button “do not assign a drive letter or drive path” à Next
  6. On the Format volume wizard leave the defaults à Next
  7. On the New simple volume wizard à Finish
  8. Close Computer Manager
  9. Maximize Failover cluster manager
  10. Right click TeamX.HVLAB.Local and select validate cluster
  11. On the Validate configuration wizard check “Do not show this page again” à Next
  12. On the Testing Options page select “Run only tests I select” à Next
  13. On the Test selection page uncheck all options except storage à Next
  14. On the Confirmation page à Next
  15. On the Summary page à Finish
  16. Under storage select disks
  17. In the “Actions” pane select “Add disk”, in the “Add disk to cluster”  validate the cluster disk is selected à Ok
  18. Right click on “Cluster disk 1” and select “Add to Clustered Shared Volumes”
  19. Right click Teamx cluster and select “More actions” à Configure cluster quorum settings”
  20. In the “Configure Cluster Quorum Wizard”  on the “before you begin page” check the box “do not show this page again” à Next
  21. In the “Configure Cluster Quorum Wizard”  on the “Select Quorum configuration options” select “Advanced quorum configuration witness selection” à Next
  22.  In the “Configure Cluster Quorum Wizard”  on the “Select voting configuration” validate “All Nodes” is selected à Next
  23. In the “Configure Cluster Quorum Wizard”  on the “configure quorum management” validate “allow cluster to dynamically manage the assignment of node votes” is selected à Next
  24. In the “Configure Cluster Quorum Wizard”  on the “Select Quorum Witness” page select “Configure a file share witness” à Next
  25. In the “Configure Cluster Quorum Wizard”  on the “Configure File Share Witness” input \\HVLABDC\FSW\TeamX where X is your assigned team number à Next
  26. In the “Configure Cluster Quorum Wizard”  on the “confirmation” page à Next
  27. In the “Configure Cluster Quorum Wizard”  on the “Summary” page à Finish

Leave a Comment

Hyper-V Labs Part 3 Working with Server Manager

1.     Working with Server Manager

Windows Server 2012 has dramatically changed the way in which Server Administrators can manage the infrastructure. The new Server Manager UI allows an administrator to install roles and features on remote systems, create dashboards and holistically managed the Server infrastructure.

1.1             Creating a Server Group

Introduction:

Server Manager has been dramatically changed in Window Server 2012 and will be become an integrated part of any Server Administrators management process.

Purpose:

In this lab you will create a custom server group consisting of your server

Estimated time of Lab: 5 minutes

*This lab is to be done by both students*

  1. Launch the Server Manager Dashboard
  2. In the middle pane under “Configure this local server” select  “create server group”
  3. In the “Create Sever Group” dialog box under “Server Group Name” input StudentX (where X is your student number)
  4. In the “Create Sever Group” dialog box select  StudenX (where X is your student number) and click  the arrow to move your server to the assigned column à Ok
  5. On the Server Manager Dashboard you will now see a new group called StudentX (where X is your student number) select the group StudentX

 

1.2             Managing a Server Group

Introduction:

Server Manager offers a number of rich enhancements that will allow a Server Administrator to easily get enhanced data about that system you manage.

Purpose:

In this lab you will edit a number of settings in Server Manager to enable BPA scan, performance monitoring, and custom event views.

Estimated time of Lab: 10 minutes

*This lab is to be done by both students*

  1. Launch the Server Manager Dashboard
  2. Select the Server Group “StudentX” (where X is your assigned student number)
  3. Scroll down to the “Best Practice Analyzer” section
  4. In the “Best Practice Analyzer” section select  task  à start BPA scan
  5. Review the BPA results
  6. Scroll down to the “Performance”
  7. In the “Performance” section  select task à “configure performance alerts”
  8. On the “Set performance alert threshold” change the CPU % = 70 and the Memory = 3
  9. On the “Set performance graph display  period” change the drop down to 2 à Save
  10. In the “Performance” section  select  your server StudentX (where X is your assigned student number)
  11. Right click  StudentX (where X is your assigned student number) à “Start Performance Counters”

*Note it will take a few minutes to aggregate the server data, continue the lab and you can review the data at a later time *

  1. Scroll to the “Events” section of your server group
  2. In the “Events” section select  task à “Configure event data”
  3. At the bottom of the “configure event data” window select the drop down menu for “get events from the following event log files”
  4. Scroll down and select all options that contain “Microsoft –Windows-Hyper-V”  à Ok
  5. Review any event logs listed

Leave a Comment

Hyper-V Labs Part 2

Install Hyper-V and Configure Hyper-V

 

Introduction:

Installing and configuring Hyper-V is the first step in your organization to building and deploying Microsoft’s hypervisor.

Purpose:

In this lab you will install Hyper-V on a Windows 2012 Server and make basic configuration changes that will allow the Windows Server to host virtual machines.

Estimated time of Lab: 30 minutes

*This lab is to be done by both students*

  1. Launch the Server Manager Dashboard
  2. Select Dashboard and choose “Add Roles and Features”
  3. On the “Installation Type” page select “Role-based or features based installation” à Next
  4. On the “Server Selection” page select your server (Student X where X is your assigned student number) à Next
  5. On the “Select server Roles” page  check the box labeled “Hyper-V”
  6. On the popup window “Add Roles and Features” select “Add Features”
  7. On the “Select server Roles” page check  the box labeled “Remote Desktop Services” à Next
  8. On the “Select Features” page accept the defaults à Next
  9. On the “Hyper-V” page à Next
  10. On the “Create Virtual Switch” page under Network Adapters select the adapter labeled MGMTà Next
  11. On the “Virtual Machine Migration” do NOT make any changes à Next
  12. On the “Default Stores” page do NOT make any changes à Next
  13. On the “Remote Desktop Services” page à Next
  14. On the “Select role services” check the box “Remote Desktop Virtualization Host
  15. On the popup window “Add Roles and Features” select “Add Features” à Next
  16. Check the “Restart destination server automatically if required” box
  17. Click “Yes” on the popup window to confirm the auto restart for the installation à Install

*Note: the Physical host will reboot 2 times to install the hypervisor this will take approximately 10 minutes *

  1. On the “installation progress” page select “close”
  2. Close all open windows expect for Server Manager
  3. In the top right hand corner of Server Manager select “Tools à Hyper-V Manager”
  4. In Hyper-V Manager select your Server “Student X” (where X is your assigned student number)
  5. In the Actions pane on the right select “Virtual Switch Manager”
  6. Under “Virtual Switches”  select the “Broadcom Netextreme” virtual switch
  7. On the “Virtual Switch Properties” page in the “Name” section change the name of the virtual switch to be “TeamX-VS” where X is your assigned team number

*Note use exact name with capital T and VS

  1. On the “virtual switch” properties  select “Yes”

Leave a Comment

Hyper-V Labs part 1

In the following series I will be posting labs that you can walk through to assist virtualization administrators in learning Hyper-V. To follow the labs you will need two machines capable of running Windows Server and Hyper-V and some shared storage. Note Windows can act as an iscsi san.
Workshop Setup

The environment also hosts 3 additional VMs running the following services: 1. RDS Web 2. RDS Connection broker and 3. VMM 2012 Sp1. These additional servers will be key components to facilitate VDI and Virtual Machine Management Labs.

Environment information:

Student/Username           Student assignment              Host Name               Team Number          Host IP          Cluster IP         Broker IP
Student 1                               A                                             Student1                             1                            x.x.x.50          x.x.x.52             x.x.x.53
Student 2                               B                                             Student 2                           1                            x.x.x.51           x.x.x.52             x.x.x.53

Active Directory Configuration
A single Domain Controller running Windows Server 2012 and host the additional roles of DHCP and File Server.
Active Directory Domain Controller Logon Password DC IP Shares DHCP Scope
HVLAB.LOCAL HVLABDC Administrator Pass@word1 x.x.x.10 FSW X.X.X 180- X.X.X 200

Assumptions:
1. You have already setup active directory
2. You have 2 physical machines that have Windows Server 2012 (r2) installed

Converting a Windows 2012 Server to Core
In the past Windows Server Core provided a limited set of functionality however in Windows Server 2012 Server Core has been enhanced and provides administrators with the ability to move between Server Core and a GUI based Windows Server. Windows Server now provides 3 modes: GUI, Core, and Core with management tools.

Introduction:
Windows Server 2012 now provides the flexibility to move between Windows Server core and a Windows GUI environment. This allows an administrator who may not be as familiar with powershell and command lines to add a GUI back to a server to perform task and then remove the GUI.

Purpose:
In this lab you will remove the graphical user interface from your Windows 2012 server and then add it back.

Estimated time of Lab: 20 minutes

1. Launch the Server Manager Dashboard
2. In the top right hand corner select Manage “Remove roles and features”
3. On the “before you begin” page check the box “Skip this page by default”  Next
4. On the “Server Selection” page select your server (Student X where X is your assigned student number)  Next
5. On the “Select server Roles” page  Next
6. On the “Remove Roles and features” scroll down to “User interfaces and infrastructure”
7. Remove the check box for “Server Graphical shell”  Next
8. On the “Confirm Removal Selections” check the box “Restart destination server automatically if required”
9. On the popup window click “Yes” to allow the restart  Remove
*Note: the server will reboot
10. Once you logon you will now be presented with a command window and Server Manager
11. Minimize server manager to see the command window and type “Powershell” 
12. In the command window type “Add-WindowsFeature Server-GUI-Shell” 
13. After the feature is installed we will need to reboot the machine, type “Restart-Computer” 

Leave a Comment

Microsoft release native RDP 8.1 client for IOS and Android

If you have not seen it a big announcement got slipped into a Microsoft press release this week that many may have overlooked.

Microsoft unleashes fall wave of enterprise cloud solutions
Oct. 07, 2013

http://www.microsoft.com/en-us/news/press/2013/oct13/10-07hybridcloudpr.aspx?wt.mc_id=PR_Blog

Towards the bottom is this paragraph.
Further, with Windows Server 2012 R2 Microsoft is introducing the Microsoft Remote Desktop app, available for download in application stores later this month, to provide easy access to PCs and virtual desktops on a variety of devices and platforms, including Windows, Windows RT, iOS, OS X and Android.

Now that Microsoft has the RDP client available they have a true VDI solution to compete with Citrix and VMware that is native to the Windows Server OS

Leave a Comment

VMM 2012 & Managing VMware

Below is a video talking about how Microsoft’s Virtual Machine manager 2012 can manager Hyper-V, VMware, and Citrix Xen.

Leave a Comment

Windows 2012 and VDI

The below video shows how easy it is to setup VDI with Windows Server 2012 which is just another native capability of Windows Server!

Leave a Comment

Hyper-V replica script

Windows 2012 Hyper-V has a wonderful new feature called Hyper-V replica that will allow a Hyper-V host to replicate on a per Vm basis from one host to another providing an out of the box DR solution.  There are a number of way to enable replication on each VM either in Hyper-V manager or from powershell however if you have a large number of VMs manually can be a task.

The below script can be run to grab all the VMs on a host that does not have VM replication enabled and configure the replication

————————————————————————————————————————————–

#This script will read in a number of inputs and then configure hyper-v replication for VMs that currently do not have replication enabled

#Note this script assumes you have already enable Hyper-V replica on the servers

 $Replica = read-host “Enter Hyper-V replica destination server name”

$Port = read-host “Enter the replication port”

$HVhost = read-host “Enter Hyper-V source server name”

$Auth = read-host “Enter replication auth method of Kerberos or Certificate”

 

$alldisalbed = get-vm -ComputerName $HVhost | where {$_.replicationstate -eq ‘disabled’ }

#This will display all VMs that are about to be enabled for replication

write-host “The following VMs will be enabled to replication to $replica”

$alldisalbed

foreach ($VM in $alldisalbed) {

 enable-VMReplication $VM $Replica $Port $Auth

Set-VMReplication -VMName $VM.name  -ReplicaServerName $Replica -ReplicaServerPort $Port -AuthenticationType kerberos -CompressionEnabled $true -RecoveryHistory 0 -computername $HVhost

Start-VMInitialReplication $VM.name  -ComputerName $HVhost

}

Leave a Comment

Exchange 2010 SP3 release

Microsoft has released Exchange 2010 SP3 which will allow  integration with Exchange 2013  http://blogs.technet.com/b/exchange/archive/2013/02/12/released-exchange-server-2010-sp3.aspx

Leave a Comment

css.php