Innovative Technology Weblog

A few months ago my beloved colleague Walter gave me the Beta version of System Center Virtual Machine Manager. Unfortunately I haven’t had the time to play with it until now. While most people enjoy their well earned vacation, I’m playing around with SCVMM.

There are definitely things to be excited about:

• Ability to manage both Hyper-V and VMware farms
• Migrate virtual machines between Hyper-V hosts (maybe not a live migration, but a migration none the less! )
• But the main thing to be excited about is the future integration within the System Center family.

And their are also some irritating things:

• Hyper-V has just RTM’ed and SCVMM is still in beta. This means you got to install update after update to make everything work.
• When I try to install the integration services on Windows Vista it comes with the message: “Unsupported Guest OS – An error has occurred: The specified program requires a newer version of Windows.” Unfortunately I’m not yet in the possession of Windows 7… 
• I created a new library share. But when I try to mount an ISO file to my virtual machine it fails and the only thing you can do with your virtual machine from that point is remove it and repair it. Through the repair option you can save him by the way.

I properly can go on and on with these things but I can rather posts these on connect.microsoft.com. It is still a beta and I believe eventually these ‘minor’ issues will be solved.

There is one very interesting feature I found in SCVMM and I’m still not sure if it’s a brilliant or stupid thing. When you create a new virtual machine you got to choose your processor type. Not just the number of virtual processors or the clock rate, no actually the processor type. Like the 1.2 Ghz Athlon, the 3.0 Ghz Pentium 4 (HT Technology) or the 2.8 Ghz Xeon MP.

It states that it uses this info to determine the processor requirements of the virtual machine. That’s being used when calculating host ratings and when setting CPU resource allocations.
You can view the host rating when you create a new virtual machine. The host rating helps you to choose the best host for your virtual machine. Based on free resources.
CPU resource allocation is something we know from VMware ESX. VMware uses shares to do this. A plain number like 1000 or 2000. The virtual machine with 2000 shares gets twice the amount of CPU cycles (when needed) in comparison with the machine that has 1000 shares.

I understand that SCVMM should use his own system that can be plotted on all the different virtualization platforms it’s going to manage (Hyper-V, XEN, ESX). But I don’t understand how a 2.4 Ghz Opteron relates to a 2.4 Ghz Xeon.
So if I just want my production server to have a 50% preference over my test server which should I choose? And what’s worse, if I’m in doubt with this option, how about a self service user that’s got the option to create a new virtual machine? I can imagine it would properly mean that this user got the advise to skip it.

But there is one more thing confusing about this. When you use the Virtual Machine Manager snap in, there is another way to set the processor weight and you can use a simple number!

So if I change the processor type in SCVMM of a virtual machine, you would suspect something to change within this screen. But it doesn’t… Neither does it the other way around.

I’m going to investigate some more but if you got some tips or hints, please post them!

I have had a love/hate relationship with the VMWare Server 2 beta for the last couple of months and today, I’m sorry to say we have parted ways. First up, my quarrel is not with VMWare products as a whole (I still love Workstation and ESX) but frankly with the poor interaction you get with VMWare in their own beta programs. It really is a far, far cry from the type of interaction and feedback you get in the Microsoft beta programs…

I would have been able to live with the lack of interaction if I weren’t having any major problems with the product. But as such things go, I ran into one showstopping problem… It turns out that on my hardware (which is a big, tricked out server that cost a small fortune and which I am not replacing) VMWare Server 2 had major issues correctly virtualizing Windows Server 2008 x64. Just that one OS. Everything else worked fine: Windows 2003 x86 & x64, even Windows 2008 x86 ran without a hitch. It has to be said that this is not a generic problem, since most others either don’t run into the problem (on a HP nx6325 laptop I also have no issues whatsoever), or they just don’t understand why things are breaking. But I’m certainly not the only one, judging from the replies and the 300+ views on the thread I posted in the VMWare Server 2 beta 2 community.

Now, I could manage without Windows 2008 x64 servers for a good while, since Exchange 2007 also runs on Windows 2003 (or if you’re really nuts like me, you can hack the x86 version on Windows 2008 into production ). But now that I’m participating in the Exchange ‘14’ TAP, I just have to have a Windows 2008 x64 machine. Either that or just don’t bother at all.

In my experience with Microsoft Technology Adoption Programs, Microsoft usually goes above and beyond to help their customers if they run into a blocking problem with the product, even if you are the only customer experiencing the problem. The experience with VMWare was pretty much the opposite, unfortunately. I have filed not one but two Support Requests and never have gotten more interaction than the support engineer asking me to run their support-info-gathering script (vm-support.vbs) and attaching the output to the Support Request. After that, either the support engineers go deaf or they just can’t help me anymore

So now I have grown tired of waiting for information that won’t come and I have decided to uninstall VMWare Server 2 and install VMWare Workstation 6 instead. I would’ve installed Hyper-V, but alas my 1st gen AMD Opterons don’t support the CPU Virtualization extensions needed for Hyper-V…

I’m actually quite sad to see VMWare Server 2 go, because I really liked the way you could manage VMWare Server 2 via the standard VMWare Virtual Infrastructure Client, even over the internet. I liked where VMWare Server 2 was going but it seems it was just to immature for my bleeding-edge needs…

Anyway, Workstation 6 has taken over now and my first Exchange ‘14’ server is (virtually) buzzing with a large grin

That’s a dozen more mailboxes to add to the running-Exchange-‘14’-in-production-count, DavidEsp!

Last month me and some collegues went to MMS2008 in Las Vegas were I saw a cool demo of Group Police Preferences. The name Group Policy Preferences did ring a bell with me and suddenly I remembered. A few weeks before MMS I saw a Windows Update that was called Group Policy Preferences Client Side Extensions, but I did’nt know what it was.

So now that I’m a few weeks back home I finaly had some time to play with it on my Demo Domain that I setup last week using CoreConfigurator. To use Group Policy Preferences you must have a few things in place:

• A Windows Server 2008 or Windows Vista SP1 machine (only needed for managing Group Policy Preferences)
• RSAT Installed on the management machine
• Deployed the Group Policy Preferences Client Side Extensions to your Desktops/Servers (XP SP2 or higher)
• Active Directory

Note : You don’t need a 2008 DC or Windows Vista SP1 client to use Group Policy Preferences !!

On the left screenshot you can see all the different options that can be managed using Group Policy Preferences. There ar too much settings to show them all on this blog, but I realy like to show you some nice things. I made some screenshots of some common things you normaly do in loginscripts or kix scripts, but that are now possible in Group Policy. (click on the images to see it full size)

With Group Policy Preferences it is easy to map networkdrives. Not only you can map a drive for all users in a generic user policy, but it is also  possible to target this mapping to no more then 27 targeting rules. (Image on the right)

Most common is to map a network share based on group membership or IP subnet. This way way it is possible to map a share witf for example application data to a server that is on the same geographical location as the user without the need of using DFS or site loginscripts.

An other example is setting up how users (or administrators) see their files in Windows Explorer. In this screenshot I set it up so that the user will see the file extentions for known files and also shows hidden & system files, this is a setting that most admins will set if they logon to a new machine. This is also the power of Group Policy Preferences, the most settings an administrator will have to manualy do if he is building a new image for deployment can be managed by Group Policy Preferences.

As you can imagine there are hundreds or maybe thousends of possibilities that you use in solving those anoying problems you usely have to solve using scripts or other tools.

Next thing I have to do is migrating my loginscript at home to Group Policy Preferences.

Have fun with it.

Erik Luppes

I actually ran into more problems with the PKI after the installation. Although SCCM detects your Site Server Signing certificate during setup, the process of dragging and dropping the certificate from the current user branch to the local machine branch may (not sure if there are situations where this does not happen) corrupt the private key in the certificate. To fix this, you have to change the template for the Site Server Signing certificate. On the ‘Request Handling’ tab, check ‘Allow private key to be exported’. Then go through the process of requesting the certificate as usual, and don’t drag and drop as I described in my previous post, but export from the current user certificates and import in the local machine certificates. That should fix the Site Server Signing certificate.

I also had a problem with the Web Server certificate, don’t know if it’s related to having a Windows Server 2008 Certificate Authority or not. In the Microsoft walkthrough they tell you to duplicate the normal Web Server template. When I did this, SCCM kept reporting the Management Point giving problems; a test http request would return an error. After a little Googling I found the solution: on the new template (I named it SCCM Web Server) add Client Authentication on the ‘Extensions’ tab. Don’t forget to re-enroll and re-assign the certificate to your website.

I hope that’s all I have to say about this.