Last week I published a script to create a converged fabric clustered host. I wrote that script using the beta of Windows Server 2012 (“8”). But since then, the release candidate has come out. And wouldn’t you know it, some of the PowerShell cmdlets in the RC have changed.
Here’s a summary of the changes:
- When you create a NIC team in the GUI, the device name now matches the NIC team local area connection name. That’s a good change. I hated that the local area connection name was tucked away in the advanced settings and threw in a “default” into the name.
- The cmdlet to set the IP address of the NIC is different. We used to say –IPv4Address to specify the address. Now we use –IPAddress.
- By default, the new virtual NIC took on a meaningless “Wired Ethernet Connection” label for the Local Area Connection name. I had to rename it to something meaningful, like “Host-Parent”. Now, the new virtual NIC takes on a meaningful name, such as “vEthernet (Host-Parent)”, so I can delete the cmdlet to delete it. At first I didn’t like this, but after talking to Hans Vredevoort last night, he changed my mind.
- I have found that a new management OS virtual NIC can take over 20 seconds to initialise. That means that any attempt to configure the IP address straight away will fail. Therefore I’ve moved all the IP config cmdlets to the end of the script, and they only run after a 30 second sleep.
I have updated the original script to reflect these changes.
After some testing I found that I had to add a sleep cmdlet before configuring the IP addresses of the virtual NICs.