Microsoft Virtual Server 2005 Enterprise

[CriminaL]

http://rapidshare.de/files/36325382/Microsoft_Virtua_Server_2005_Enterprise_Edition.part1.rar

http://rapidshare.de/files/36325379/Microsoft_Virtua_Server_2005_Enterprise_Edition.part2.rar

Password: mcc3k

Virtual Server 2005 runs as a Windows service on a Windows 2003 Enterprise Server box. An administrator then can establish multiple concurrent server environments - called virtual machines - on that single physical server, each with its own limitations in terms of what resources it can access. We suggest multiple CPUs for the hardware and a great deal of RAM (a minimum of 512M bytes per virtualized server plus another 512M bytes as a base).

The Virtual Server 2005 Management Console is a Web-based program, and its real estate is somewhat ugly and poorly managed. Although, the ability to monitor each of the virtualized servers via a Web page simplifies that process a great deal.

There are three ways to build a virtual machine inside a host server. The first is to install the server software onto an allocated virtual machine, which when booted appears as though it is a new server. The second method is to copy resource settings from another already-built virtual machine. These settings, along with loaded application, can be easily replicated to create additional virtual machines. The third way is to migrate a compatible server/application instance to a virtual machine using the migration kit.

After installing Virtual Server 2005, you can either use Microsoft's preset parameters or tap into the GUI to establish your own settings for each virtual machine. Those settings include disk control (size, type of disk, location and allocated space), maximum memory to be used, IP address and operation mode. Each virtual machine can be named and can use network addresses that are internal, external or on a virtual network. These virtual machines also can stand alone and not be connected to a network.

The virtual machines lock host resources - such as CD/DVD players, serial ports, parallel ports and other devices - when they use them so that other virtual machines cannot access those host resources. Other resources may or may not need to be used sequentially. As an example, disk drives can use either shared or privately allocated space but never the same files except as read-only resources. Certain resources such as external USB drives, authentication token or biometric authentication devices cannot be shared devices.

n our tests, we generated and then migrated several server types. The total migration time ranged from just under six hours for MS SQL Server running on NT 4 SP 6 to just more than seven hours for Microsoft Exchange 5.5 running on Windows 2000 Advanced Server SP 3. These measurements include the time it took to build the images, resolve resource settings, install the image onto the virtual server, and restart the server and its applications. Faster hardware certainly helps speed the process, as does close reading of the detailed migration kit documentation.

The migration application and scripts successfully remapped hardware resources. The software also let us remap the Ethernet card media access control address of old cards to new server addresses.[/CODE]

[asustek]

çok teşekkür ederim

[Falcon]

Teşekkür etmek istiyorsanız Butonunu kullanmalısınız.

Gereksiz Post Atmayın...

[OulCidoY]

Microsoft Virtual Server 2005 R2 SP1 - Enterprise Edition

32 bit :

http://download.microsoft.com/download/d/7/2/d7235926-a10d-482c-a2ff-6e0d3130f869/32-BIT/setup.exe[/CODE]

64 bit :

[CODE]http://download.microsoft.com/download/d/7/2/d7235926-a10d-482c-a2ff-6e0d3130f869/64-BIT/setup.exe[/CODE]