For those who are going to install the Windows 8 Release Preview. You cannot upgrade from Windows 8 Customer Preview. Same for the Windows Server 8 beta to Windows Server 2012 Release Candidate.
With Windows Server 2012 Microsoft released a new Virtual Disk Format called VHDX. VHDX improves the Virtual Disk in a lot of way.
Back in October I wrote a blog post on the improvements of the VHDX Format in the Windows Server 8 Developer Preview. Back then VHDX supported a size of 16TB, with the release of the Windows Server 8 Beta (Windows Server 2012 beta) the new Maximum size changed to 64TB.
Some of the VHDX improvements:
You can download the VHDX Format Specification.
To use this new features you have to convert your existing VHDs into the new VHDX format. You can this do in two different ways, with the Hyper-V Manager or with Windows PowerShell.
To convert a VHD to a VHDX with Windows PowerShell you can use simple this PowerShell command:
|
1 |
Convert-VHD TestVHD.vhd -VHDFormat VHDX -DestinationPath C:\temp\VHDs\TestVHDX.vhdx -DeleteSource |
Of course you can convert the VHDX back to a VHD using the following command:
|
1 |
Convert-VHD TestVHDX.vhdx -VHDFormat VHD -DestinationPath C:\temp\VHDs\TestVHD.vhd -DeleteSource |
Same as with the PowerShell command, you can also convert a VHDX to a VHD. But you have to make sure that the VHDX is not bigger than 2TB.
Aviraj Ajgekar already did a post on this TechNet blog about how you can convert a VHD to VHDX via Hyper-V Manager.
Microsoft worked hard on the management of the new Windows Server 2012. In Windows Server 2008 R2 you had to choose during the Installation if the Server is a Windows Server Full Installation (with GUI) or a Windows Server Core Installation (without GUI). In Windows Server 2012 you can add and remove the GUI from the server.
On a Core Server you can add the with the following PowerShell command
|
1 |
Add-WindowsFeature Server-GUI-Shell |
After the Installation you have to restart the server
|
1 |
Restart-Computer |
There are two ways you could do that, first via Server Manager remote the GUI feature:
Or via Windows PowerShell
|
1 |
Remove-WindowsFeature Server-GUI-Shell |
It is also important that you understand that Windows Server 2012 has three different GUI options.
So if you activate the GUI you do not get all of the Management tools automatically. You have also to activate the “Management tools GUI”.
If you are working a lot with Hyper-V and Hyper-V Clustering you know that something that takes a lot of time is configure the Hyper-V Host Network Adapters. First because most of the time you have a lot of NICs build into your host for the different Hyper-V and Cluster networks and secondly Windows names the NICs in a random way and this makes it hard to find out which network card is the right one. Maybe your first NIC on your Hyper-V Host01 is called “Local Area Connection 2” and on your second Hyper-V Host with the same hardware configuration the “same” NIC is called “Local Area Connection 3”. One of the possibilities to find out which network card is the right one is to check the MAC address of the network adapter. But for this you still have to know which MAC address is on which network adapter port.
Another way to do it is to plug in the network cables one by one. So you can see which port is active and then you can rename the network adapter. Now some times this one is one of the only solutions, but it takes a lot of time to do this on every host. And if you build Clusters up to 16 Hosts you really don’t want to do that.
Now there is a solution, you can sort your NICs by PCI bus and PCI slot. Maarten Wijsman did a blog post how you can do this on the Hyper-V.nu blog. With this knowledge you can start to automate this very easy.
I have created two Windows PowerShell scripts which make my life a lot easier.
First I configured the first Hyper-V host and renamed all the Network adapters. If you have a GUI server you could do that via GUI or if you have a Windows Server Core or Hyper-V Server you can do this via netsh.
|
1 |
netsh interface set interface "Local Area Connection 2" newname="Management" |
If I have done that I use my Windows PowerShell script called Get-NICInformation.ps1 to get the information about the network adapters.
This gives me a lot of information about the NICs in my first hosts. But the important part is the order of the NICs. In my example I know that the order is this:
Since my other hosts have the same hardware they will have the same PCI Bus order.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 |
# ---------------------------------------------------------------------------------------------- # # Powershell Get-NICInformation $Rev: 748 $ # (c) 2011 Thomas Maurer. All rights reserved. # created by Thomas Maurer # www.thomasmaurer.ch # www.itnetx.ch # last Update by $Author: tmaurer $ on $Date: 2012-02-24 14:07:36 +0100 (Fr, 24 Feb 2012) $ # ---------------------------------------------------------------------------------------------- # #region [INFO BLOCK] # INFO Write-Host " " -BackgroundColor Black -ForegroundColor White Write-Host " PowerShell Get-NICInformation " -BackgroundColor Black -ForegroundColor White Write-Host " " -BackgroundColor Black -ForegroundColor White Write-Host " by Thomas Maurer " -BackgroundColor Black -ForegroundColor White Write-Host " www.thomasmaurer.ch " -BackgroundColor Black -ForegroundColor White Write-Host " " -BackgroundColor Black -ForegroundColor White #endregion $adapters = Get-WMIObject Win32_PNPSignedDriver | Where-Object { $_.DeviceClass -eq “NET” -and $_.HardWareID -like “*PCI*” } | Sort-Object location foreach ($adapter in $adapters ) { $adapterName = Get-WMIObject Win32_NetworkAdapter | Where-Object { $_.PNPDeviceID -eq $adapter.DeviceID } $adapterConfiguration = Get-WmiObject Win32_NetworkAdapterConfiguration | Where-Object { $_.index -eq $adapterName.Index } Write-Host ‘Adapter Name :’ $adapterName.NetConnectionID Write-Host ‘PCI BUS :’ $adapter.Location Write-Host ‘MAC Address :’ $adapterName.MACAddress Write-Host ‘GUID :’ $adapterName.GUID Write-Host ‘Adpater Index :’ $adapterName.Index Write-Host ‘Hardwarename :’ $adapterName.Name Write-Host ‘DHCP enabled :’ $adapterConfiguration.DHCPEnabled Write-Host ‘IP Address :’ $adapterConfiguration.IPAddress Write-Host ‘Subent :’ $adapterConfiguration.IPSubnet Write-Host ‘Default Gateway :’ $adapterConfiguration.DefaultIPGateway Write-Host } |
For the next step I go to my second host. There I have my other Windows PowerShell script (Set-IPAddressfromXML) and a XML file (networkconfig.xml).
I edit the networkconfig.xml file with the correct network information. Important here are the id=”” parameters. They are showing the order of the NICs so with Get-NICInformation I can see the Management interface is the first one, so it gets id=”1″, VMNET is the second one it gets id=”2″ and so on. You also set the correct IP Address information for the second host. Most of the time you just have to change the last number.
You can also set non static IP Addresses (DHCP), in my case I did this for the VMNET adapter which will be used by the Hyper-V Virtual Switch and does not need a IP address.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
<?xml version="1.0" encoding="utf-8"?> <config> <networkadapters> <nic id="1" name="Management" static="true" ip="10.0.20.1" subnet="255.255.0.0" gateway="10.0.0.1" /> <nic id="2" name="LiveMigration" static="true" ip="192.168.21.1" subnet="255.255.255.0" gateway="" /> <nic id="3" name="CSV" static="true" ip="192.168.22.1" subnet="255.255.255.0" gateway="" /> <nic id="4" name="TeamedAdpater01" static="false" ip="" subnet="" gateway="" /> <nic id="5" name="TeamedAdpater02" static="false" ip="" subnet="" gateway="" /> <nic id="6" name="TeamedAdpater03" static="false" ip="" subnet="" gateway="" /> <nic id="7" name="ISCSI01" static="true" ip="10.10.21.1" subnet="255.255.255.0" gateway="" /> <nic id="8" name="ISCSI02" static="true" ip="10.10.22.1" subnet="255.255.255.0" gateway="" /> </networkadapters> </config> |
After you have done this, you can now simply run the Set-IPAddressfromXML script. This will use the Information from the networkconfig.xml file and will rename all network adapters and will set the correct IP addresses.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 |
# ---------------------------------------------------------------------------------------------- # # Powershell Set-IPAddressfromXML $Rev: 748 $ # (c) 2011 Thomas Maurer. All rights reserved. # created by Thomas Maurer # www.thomasmaurer.ch # www.itnetx.ch # last Update by $Author: tmaurer $ on $Date: 2012-02-24 14:07:36 +0100 (Fr, 24 Feb 2012) $ # ---------------------------------------------------------------------------------------------- # #region [INFO BLOCK] # INFO Write-Host " " -BackgroundColor Black -ForegroundColor White Write-Host " PowerShell Set-IPAddressfromXML " -BackgroundColor Black -ForegroundColor White Write-Host " " -BackgroundColor Black -ForegroundColor White Write-Host " done by Thomas Maurer " -BackgroundColor Black -ForegroundColor White Write-Host " www.thomasmaurer.ch " -BackgroundColor Black -ForegroundColor White Write-Host " " -BackgroundColor Black -ForegroundColor White #endregion #region [CONFIG BLOCK] # Get XML Information [Xml]$global:xmlData = Get-Content ".\networkconfig.xml" # Set NIC number starting value [int]$global:nicNumber = "1" #endregion #region [MAIN BLOCK] #Get NIC list $Adapters = Get-WMIObject Win32_PNPSignedDriver | where { $_.DeviceClass -eq “NET” -and $_.HardWareID -like “*PCI*”} | Sort-Object location foreach ($Adapter in $Adapters ) { # Get Adapter Info $AdapterName = Get-WMIObject Win32_NetworkAdapter | where { $_.PNPDeviceID -eq $Adapter.DeviceID } $nic = $xmlData.config.networkadapters.nic | Where-Object {$_.id -eq $nicNumber} # Write NIC Info Write-Host ‘Adapter Name :’ $AdapterName.NetConnectionID Write-Host ‘PCI BUS :’ $Adapter.Location Write-Host ‘MAC Address :’ $AdapterName.MACAddress Write-Host ‘GUID :’ $AdapterName.GUID Write-Host ‘New Name :’$nic.name Write-Host # Change NIC Name Invoke-Expression ('netsh interface set interface `"' + $AdapterName.NetConnectionID + '`" newname=`"' + $nic.name + '`" | out-null') Write-Host ('netsh interface set interface "' + $AdapterName.NetConnectionID + '" newname="' + $nic.name + '"') -BackgroundColor Green -ForegroundColor Black # if true set IP Address if ($nic.static -eq "true"){ Invoke-Expression ('netsh interface ipv4 set address `"' + $nic.name + '`" static ' + $nic.ip +' ' + $nic.subnet + ' ' + $nic.gateway + ' | out-null') Write-Host ('netsh interface ipv4 set address "' + $nic.name + '" static ' + $nic.ip +' ' + $nic.subnet + ' ' + $nic.gateway) -BackgroundColor Green -ForegroundColor Black } else { Write-Host "No IP set" -BackgroundColor Green -ForegroundColor Black } # Count +1 for next Adapter $nicNumber++ } #endregion |
I can now copy the Set-IPAddressfromXML.ps1 and the networkconfig.xml to each Hyper-V hosts and edit the IP Addresses in the xml file, run the PowerShell file and I am done.
Lets recap:
I hope this will make life easier 🙂
You can download the Scripts from my Skydrive
Some other things:
Last year I created a Windows PowerShell script for System Center Virtual Machine Manager which checks all the Virtual Machines for Snapshots and if you have any it will send you an E-Mail and it will remind you about that.
It were just some small changes from the SCVMM PowerShell cmdlets to the Windows Server 2012 PowerShell cmdlets.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 |
# Get Snapshots $snapshots = Get-VM | Get-VMSnapshot # Check for existing Snapshots if ($snapshots.count -gt 0){ # Create the List of Snapshots $info = $snapshots | Format-Table VMName, Name -auto | Out-String # Mail Configuration # ================== # Configuration $emailSubject = "VM Snapshot Reminder" $emailMessage = "You have still some snapshots: `n `n" + $info + "`n Greetings your Hyper-V Server" $smtpServer = "mail.server.com" $smtpUserName = "username" # This could be also in e-mail address format $smtpPassword = "password" $smtpDomain = "" # SMTP Object $smtp = New-Object System.Net.Mail.SmtpClient($smtpServer) $mailCredentials = New-Object System.Net.NetworkCredential $mailCredentials.Domain = $smtpDomain $mailCredentials.UserName = $smtpUserName $mailCredentials.Password = $smtpPassword $smtp.Credentials = $mailCredentials # Send E-Mail $smtp.Send($emailFrom, $emailTo, $emailSubject, $emailMessage) } |
Over the weekend I was Setting up my lab for the RTM of System Center 2012. I created some Windows Server 2008 R2 Virtual Machines on my Windows Server 2012 beta Hyper-V server. After I had created all VMs and installed them, I realized I forgot to configure the limit for Dynamic Memory for the Hyper-V Virtual Machines.
Now here the new PowerShell module for Hyper-V which comes with Windows Server 2012 helped me save some time.
First I check the Dynamic Memory Maximum value for all my System Center 2012 Virtual Machines.
|
1 |
Get-VM -Name SC2012* | ft Name, MemoryMaximum |
After that I changed the value from all my System Center 2012 Virtual Machines to 8GB
|
1 |
Get-VM -Name SC2012* | Set-VM -MemoryMaximumBytes 8589934592 |
btw. if you don’t know that 8GB are 8589934592 Bytes PowerShell can help you, check this out:
|
1 |
Get-VM -Name SC2012* | Set-VM -MemoryMaximumBytes 8GB |
Ben Armstrong, Virtualization Program Manager, did also a blog post on performing bulk configuration changes in Hyper-V via Windows PowerShell on his blog.
There is a new feature coming with Windows Server 8 called Consistent Device Naming (CDN) which should make life in the datacenter a lot easier.
It allows to hardware vendors to consistently name NICs in the BIOS which means the Windows Server 8 can read this information and name NICs the same.
That means that the name of the NICs on the chassis can be the same name on the NICs in the OS.
If you have ever worked with Hyper-V Clusters you are going love this feature.
My Name is Thomas Maurer. Microsoft MVP. Work as a Solutions Architect and Technology Lead for itnetX, a consulting and engineering company located in Switzerland. I am focused on Microsoft Technologies, especially Microsoft Cloud & Datacenter solutions based Microsoft System Center, Microsoft Virtualization and Microsoft Azure.
