The infrastructure requirements are a bit heavy, I have to say. Not exactly suitable for a consultant wanting to take away a customer's network-in-a-bottle. On Mon, 08 Nov 2004 15:54:04 -0500, Matt Kosht <matt.kosht@xxxxxxxxxxxxxx> wrote: > Cool. I can finally get rid of those dang NT 4.0 servers! > > >>> jimkenz@xxxxxxxxxxxxxx 11/8/2004 10:54:26 AM >>> > > > I wanted to pass this information on. Microsoft Virtual Server 2005 now > available has released a toolkit to "migrate" a physical server to become a > virtual server. > > This will be the must have product until the next MS OS upgrade! > > I have heard rumblings that MVS 2005 pricing will change and be much more > expensive along the lines of VMWare. Now would be the time to pick it up > while the price is "CHEAP". > > Get the migration kit at: > http://www.microsoft.com/windowsserversystem/virtualserver/evaluation/vsmt.mspx > > A free, downloadable tool for Virtual Server 2005, Virtual Server Migration > Toolkit (VSMT) simplifies the migration of an operating system and installed > applications from a physical server to a server running within a virtual > machine that is provided and managed by Virtual Server 2005. With Virtual > Server 2005, you can set up multiple virtual machines running different > operating systems and applications on the same physical computer. > > You can use VSMT to create images of physical computers and deploy them in > virtual machines running on Virtual Server 2005. With VSMT, you can migrate > source computers running the following operating systems to virtual machines > in Virtual Server 2005: > * > Windows NT 4.0 Server with Service Pack (SP) 6a, Standard and Enterprise > Editions > * > Windows 2000 Server SP 4 or later > * > Windows 2000 Advanced Server SP 4 or later > * > Windows Server 2003, Standard Edition and Enterprise Edition > > Note: VSMT is intended to be used by IT professionals and consultants and > requires use of a combination of native and add-on tools for Windows Server > 2003. Users of VSMT should have proficiency with Dynamic Host Configuration > Protocol (DHCP), PXE, and Windows Server 2003 Automated Deployment Services > (ADS). Additionally, you must have knowledge of the operating system that you > are migrating, some scripting knowledge, and knowledge of the legacy hardware > environment from which you are migrating. > > Regards, > Jim Kenzig > > http://thin.net > > > ******************************************************** > This Weeks Sponsor Emergent Online ThinCity Conference > Join us at ThinCity 2004: The 1st Annual Emergent OnLine Technology Conference > http://www.ThinCity.com > ********************************************************** > Useful Thin Client Computing Links are available at: > http://thin.net/links.cfm > *********************************************************** > For Archives, to Unsubscribe, Subscribe or > set Digest or Vacation mode use the below link: > http://thin.net/citrixlist.cfm > -- -------------- 'The difference between theory and practice is larger in practice than it is in theory.' ******************************************************** This Weeks Sponsor Emergent Online ThinCity Conference Join us at ThinCity 2004: The 1st Annual Emergent OnLine Technology Conference http://www.ThinCity.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm