May 2008 - Posts
So Hyper-V is in RC1 and it is available as a public download for all, in total there are four files that you should know of.
Install, update the existing installation (RC0) but please beware that you should:
- Shutdown all the guests, do not use the save state feature. That is NOT supported. All the child needs to be shut down...
- Delete all snapshots and snapshot trees. They can not be used anyway
- All IC's are on the IC ISO, including support for W2K8 (last time the W2K8 was a download from Microsoft)
- If you are running BETA of Hyper-V you need to recreate the child configurations but not the VHD file.
Then you upgrade the parent and then all the child. Improvements in RC1 is (really hard to guess) performance, stability, security, user experience, new programming model, forward capability. Most stuff you don't see or feel, except for the user experience part and the performance :-)
Mikael Nystrom
MVP Windows Server - Setup/Deployment
| Yes, this is going to "sound" a little bit strange, I'm fully aware of that. But the story goes like this. Long time ago I heard about something called "Centro", it was way back in time at a partner conference and the first thing that popped up in my mind was. That is something I want to be a part of, I want to play in the "band" you could say. I tried to pull every string I had, calling, mailing to the folks at MS and the most common answer was "What???". Finally I got contact and I managed to get in to the PV-TAP for "Centro". Suddenly I was working with the greatest team at Microsoft. At During the night I was trying to install and configure and at the same time banging my head every time I it did not work the way I thought it should do :-) . But it was so fun. I spend a couple of times over in Redmond at different conferences, airlifts and other stuff. Every time I was over there i tried to get meetings with the people in the team to discuss solutions, customer demands and my own "wish" list. During that time I worked hard on connect to give the team feedback and during the TAP Airlift for RC0 we had a couple of weeks ago the reward was given to me. Apparently I have been bashing most bugs on the BETA2 platform and the reword for that is a signed electric guitar, A signed guitar... |  |
So, thank you, Mike, Don, Chuck, Steve, Bjorn, Christer and the rest of the team (I'm sorry I dont remeber all the names)
By the way, If the next top price is a piano, could you please help my by letting me know before :-)
Mikael Nystrom
MVP Windows Server - Setup/Deployment |  |
It took a while, but I finally discovered that the error occurs when you want to use VLAN tagging on the child partitions (guests) and the default VLAN Id for the physical NIC is set to 0 (or empty), the physical NIC needs to have something. My guess is that doing that enables the VLAN feature on for the NIC and that makes it possible for the Hyper-V networking components to use VLAN correctly.
Mikael Nystrom
MVP Windows Server - Setup/Deployment
You are not alone, there is a problem with some models of HP's "HP Network Configuration Utility" and when removing or adding the Hyper-V role. The problem is that when adding/removing the Hyper-V role on the RC0/RC1/RTM (According to HP this is going to be solved) release of Hyper-V it tries to modify network settings and the cpqteam.dll does not respond correctly to that kind of call. The result is an endless wait for the configuration to end, and that will never happen so you are "toasted". So to avoid the problem simply uninstall "HP Network Configuration Utility" before adding/removing Hyper-V.
And how do you do that, you may ask, well it is much easier than you think. Go to Network and Sharing Center", Manage "Network Connections", select your network adapter, select properties, find the HP tools in the list of services and protocols, select it and then click "Uninstall". Done
If you already ended up with a rebooting server that get stuck on 78% and never passes that there is a way.
- Shut it down
- reboot on a WinPE cd/dvd (You can use the install DVD and select recover/repair to get a CMD prompt)
- Find the folder for that app (C:\Program files\HP\NCU]
- Rename the cpqteam.dll to cpqteam..dll.pleasemakethiswork
- Reboot
- Change the name of the dll back to the previous name
Mikael Nystrom
MVP Windows Server - Setup/Deployment
You might ask "why", well it is a very simple answer to that, In some scenarios the product key wont work anymore, yes, I know its weird but its true.
The slipstream function does for some reason behaves differently and the result sucks, no keys work on that machine when doing a fresh install. In XPSP3 they have changed the default behavior in a way that makes it possible for a user to install without any key and have trial period of 30 days, for some reason all that is broken when doing the slipstream on a Windows Vista or a Windows Server 2008 machine, The problem was discovered in RC1 of SP3 but for some reason this issue has not been addressed. So the only solution is to slipstream on a Windows XP/Windows Server 2003 box.
Mikael Nystrom
MCP, MCDST, MCT, MVP Windows Server - Setup/Deployment