Virtual Server 2005 -The product you are all now evaluating!

Hey, I really enjoyed the presentation last night… I hope you all did as well! You all seem very enthusiastic about  Virtual Server 2005.

I really do want to thank you for all of your questions as whilst I ran over a little last night, I hope you enjoyed the opportunity as much as I did to talk about Virtual Server 2005.

I would really appreciate your feedback on this blog though (it keeps my boss and I  happy to find out that you enjoyed the session and found it useful)

For all of those who have yet to download Virtual Server 2005, here are the links to the main resources:

Here is the main Microsoft Site for Virtual Server 2005:

You can download the evaluation kit from here (if you have MSDN see the next link):

MSDN Subscribers from the subscription site:

Many of you asked about the migration tool kit, so I can confirm that it currently supports virtualising Windows NT 4.0 Server SP 6a (Standard and enterprise), Windows 2000 Server SP4 or later (Standard and Advanced) and Windows 2003 Server (Standard and Enterprise). This is a beta, so you will need to register to download it:

Another question asked was whether or not sysprep could be used with SBS 2003. Unfortunately sysprep doesn’t support domain controllers and therefore the answer is normally no (unless you are using an OEM version of SBS 2003 and use Sysprep -dc -reseal).

I look forward to seeing you all at the next presentation, if not before!

Comments (2)

  1. Neal says:

    I thought the presentation was very well done and Microsoft Virtual Server seems like a very usefull tool

  2. Ken Tse says:

    Hi Bruce,

    Have you tried to migrate an VMWare GSX instance using the toolkit to Virtual Server 2005? The documentation mentions this as a feature but there is no mention on how to do it.

    The documentation merely mentions the setup and deployment for a physical which will require a reboot.

    Or when they mean it will migrate a VMware GSX instace you’re basically deploying the ads agent to the vmware instance itself?

Skip to main content