- home
- over wortell
- onze mensen
- werken bij
- oplossingen
- referenties
- blog
- TechReady
RT @IrisVink: Luc in de belangstelling op #WortellTR3 http://t.co/DYGLVLrS
RT @anoukvanh: Tijd voor de prijzenslag #wortelltr3 http://t.co/VOcaj7i8
Ook prijzen van onze sponsoren #polycom #quest en #jabra worden verloot! #Wortell #Techready LOTING kan elk moment beginnen #WortellTR3
Alle sessies zijn klaar! Techready 3 was weer een succes! Nu borrel en een verloting… er worden o.a. #Nokia #Lumia’s verloot…#WortellTR3
When doing a deployment of a Hyper-V cluster consequently configuring the networking can be a pain in the you know what. Different vendors or changing hardware layouts are only two examples that can make automated deployment challenging. This blog will explain how you can collect information about which network adapter is located at what PCI bus with Powershell. This information you can then later use to rename network adapter, teaming, changing network adapter settings etc etc.
Let first start by collecting some information of the present network adapters. The Powershell command to do this is something like this:
| Get-WMIObject Win32_PNPSignedDriver | where { $_.DeviceClass -eq “NET” -and $_.HardWareID -like “*PCI*”} |
The result will look something like shown below:
In the output we can find the location of the network adapters. You probably can imagine when having 12 network adapters in your server this isn’t very useful. So lets only collect the PCI bus information by adding | ft Location to the Powershell command.
Read the complete article here.
Yes, this article is about yet another script that will let you check the Integration Components version of your Hyper-V node and all of the VM’s on it.
On this blog there are already two (2) articles about checking the Integration Components version. Peter Noorderijk has an very useful and excellent version here. I have one here.
WHY ANOTHER ONE THEN! Sorry, I had to make another one! The other day I ran in to an issue with my own script which wouldn’t let me check the Integration Components versions of nodes and virtual machines running Windows Server 2008 RTM. So I created one that does both RTM and R2. This script works when you have an mixed environment of Hyper-V running on Windows Server 2008 RTM or R2 AND you have virtual machines running both flavors.
Continue reading here …
Microsoft has today, July 12, 2011, released an hotfix rollup for Microsoft System Center Virtual Machine Manager 2008 R2 (SCVMM 2008 R2) Service Pack 1 (SP1).
More info here: SCVMM 2008 R2 SP1 hotfix rollup
This article describes recommended updates to install to address issues when you are managing hosts or are performing a physical-to-virtual (P2V) conversion by using Microsoft System Center Virtual Machine Manager 2008 R2.
Use the information in the “More information” section to help you determine whether a particular hotfix or update applies to your environment.
Recommended updates for the Virtual Machine Manager (VMM) Server and Admin Console
System Center Virtual Machine Manager 2008 R2 Service Pack 1
For more information on how to obtain and upgrade to Service Pack 1, please reference the following site: http://technet.microsoft.com/en-us/library/gg318082.aspx (http://technet.microsoft.com/en-us/library/gg318082.aspx)
When a Vailidation Test is performed in an production environment with the configuration that uses Hyper-V with Cluster Shared Volumes chances are that the Storage tests will not finish successfully. The reason for conducting a Validation Test may be expanding the Failover Cluster with an additional node or for troubleshooting purposes.
