philipnet

Virtual Server 2005

We've installed MS's Virtual Server at work which I'm using a build up a small virtual SMS test lab. It's not too bad, and I only have two issues with it:

1. If a virtual host POSTS but doesn't find and then load an OS, it won't idle on the processor time and MSVS will let it use a good proportion of the whole systems CPU time just sitting there, waiting.
2. MSVS will kick off my remote connections to the virtual hosts if the host is doing a fair bit of network activity. It did this whilst installing AdminStudio (SMS Edition) and it was so bad during the installation of WUS that I copied it to the local HDD of the virtual host.

We are going to have to see how it plays during normal use.

A handy hint for those using Window 2000 and Virtual Server 2005

If you try to install MSVS on Windows 2000 it will complain and fail to install stating that the OS is not supported. But if you just want the remote connection software then the program you need is
  C:\Program Files\Microsoft Virtual Server\VMRC Client\vmrc.exe
just run it or copy it to your local PC from an XP or 2003 Server machine and create a desktop shortcut Easy as pie.

Windows Update Services

I'm also exploring WUS on this test virtual lab. It's main advantage over SMS is the supposedly easy deployment of driver updates. Whether this is as easy as it seems remains to be determined. Either way, I think that there is scope for both SMS and WUS in a production environment - whenever WUS is deemed stable enough.