تنظيمات Virtual server

**moh6717** · 2010-05-23, 07:28 PM

با سلام به دوستان
اگه در مورد تنظيمات Virtual server راهنمايي كنين ممنون ميشم

موضوعات مشابه:

**patris1** · 2010-05-23, 10:27 PM

کد:

http://articles.techrepublic.com.com/5100-10878_11-6144897.html?tag=rbxccnbtr1

Takeaway: Instituting virtual servers on your network can help you squeeze more performance out of your hardware investment. Here's how you install Microsoft's virtual server solution: Virtual Server 2005 R2.
This article is also available as a TechRepublic download. Virtual Server 2005 R2 (VS2005 R2) gives network administrators an easy way of consolidating multiple servers and operating systems onto a single computer. Instead of using a dedicated server for every application and service you require, you can run the applications and services on virtual server instances. This allows you to continue to isolate applications and services while making better use of existing hardware. If you've decided that server virtualization is ideal for your environment, here is the gist of what you need to know to install VS2005 R2.
Author's note

In this article, I'll outline the hardware and software requirements that must be met prior to installing VS2005 R2. I'll also discuss how to install VS2005 R2, as well as how to install a guest operating system.
System requirements

First, the computer that you are installing R2 on -- also referred to as the host computer -- must meet a set of minimum hardware and software requirements. The minimum hardware requirements include:

550-MHz processor with L2 cache (1 GHz is recommended)
CD-ROM or DVD drive
Super VGA or higher
256 MB of RAM (512 MB is required if you are running SBS 2003 Premium Edition or Windows Server 2003 Datacenter Edition)
2 GB of free disk space (4 GB is required if you are running SBS 2003 Standard or Premium Editions)

If your computer has multiprocessors, you should be aware that Microsoft has not yet addressed the issue of multiprocessor use in VS2005 R2.
R2 comes in two editions: Standard and Enterprise. The Standard edition can make use of up to four system processors, whereas the Enterprise flavor supports more than four physical processors. However, unlike VMWare's GSX and ESX offerings, guest operating systems running inside a R2 virtual machine cannot use more than a single processor, effectively eliminating VS2005 for high-end use until this is addressed.
So how does this affect your deployment? Before you proceed with deploying an application on a R2 server, ask yourself if the application can run smoothly on a single processor. If not, leave the application on a multi-processor server until Microsoft releases a version of Virtual Server in which guest operating systems can use symmetric multiprocessing (SMP).
The host operating systems that Virtual Server 2005 R2 can be installed on include:

Microsoft Windows Server 2003, Standard Edition
Microsoft Windows Server 2003, Enterprise Edition
Microsoft Windows Server 2003, Datacenter Edition
Microsoft Windows Small Business Server 2003
Microsoft Windows XP Professional

Note: The host operating system must be using NTFS.
You also need to consider the guest operating systems that you can actually run inside a virtual machine. VS 2005 R2 supports most versions of Windows, including all versions of Windows Server 2003 and Windows 2000 Server, with the exception of the Datacenter varieties, and Windows NT 4.0 SP6a.
Finally, if you plan on running the Administration Web site on the computer, you are also going to have to install Internet Information Services (IIS).
Installing Virtual Server 2005 R2

There are a few different scenarios for installing R2, each of which will be discussed in more detail. You can proceed with a new installation or, if you are running Virtual Server 2005, you can upgrade directly to R2. You can also install the Virtual Server service on one computer but run the Administration Web site on a separate computer, or have both components run on a single computer.
Performing a clean installation

Assuming that the computer meets all the hardware and software requirements, you can proceed with the installation steps described below. Completing these steps will install both the Virtual Server service and the Administration Web site.

Insert the Virtual Server CD-ROM to launch the Setup Wizard. The wizard can also be started manually using setup.exe.
Click through the wizard until you reach the Setup Type page.
Select Complete as shown in Figure A. This installs Virtual Server using the default configuration. Click Next.Figure A
The easiest way to install VS R2 is to do a full installation.
On the Configure Components page, either accept the default Web site port of 1024, or type in a new port number. Click Next.
Accept the default option to Configure The Administration Web site to always run as the authenticated user, or select Configure The Administration Web site to always run as the Local System account. Click Next.
Click Enable Virtual Server exceptions in Windows Firewall if users will access the virtual server through Windows Firewall. Click Next.
Click Install.
Click Finish when the Setup Complete page appears.

Upgrading to Virtual Server 2005 R2

If you need to upgrade an existing version of Virtual Server, you can follow the same steps described in the previous section for performing a clean installation. The only difference is you must first complete these preliminary tasks to prepare the computer for the upgrade:

Turn off all virtual machines
Perform a backup of all Virtual Server files
Stop the Virtual Server and Virtual Help Services

You can now proceed with the numbered steps described in the section entitled "Performing a Clean Installation".
Installing Virtual Server 2005 and the Administration Web site on separate computers

You can separate the Virtual Server service from the Administration Web site and run them on separate computers. You may be wondering why you would want to implement this configuration. Aside for the performance and security purposes, if you are running multiple virtual servers, you may only want IIS to be installed on one computer.
The first step in implementing this configuration is to install the Virtual Server service on the host computer(s). The process is similar to the one described earlier, only this time you need to perform a custom setup instead of a complete setup.

To install the Virtual Server service:

Insert the Virtual Server CD-ROM to launch the Setup Wizard. The wizard can also be started manually using setup.exe.
Click through the wizard until you reach the Setup Type page.
On the Setup Type page, select Custom. Click Next.
Click Virtual Server Web Application, and select This Feature Will Not Be Available, as shown in Figure B. Click Next.
Click Install.
Click Finish when the Setup Complete page appears.
Repeat these steps on each additional computer that you want to install R2 on.

Figure B

You can install the Virtual Server service and Administration Web site on separate computers. Your next step in this process is to install the Administration Web site. Keep in mind that the computer hosting the site must be running IIS.
To install the Administration Web site:

Insert the Virtual Server CD-ROM to launch the Setup Wizard. The wizard can also be started manually using setup.exe.
Click through the wizard until you reach the Setup Type page.
On the Setup Type page, select Custom. Click Next.
Click Virtual Server Service, select This Feature Will Not Be Available, and click Next.
On the Configure Components page, either accept the default Web site port value of 1024, or type a new value for the port.
Select Configure The Administration Web site to always run as the Local System account. Click Next.
Click Install.
Click Finish when the Setup Complete page appears.

Virtual Machines

Now that you've installed Virtual Server 2005 R2, you're ready to move onto the next steps which are to create a virtual machine, install a guest operating system, and install the Virtual Machine Additions.
Adding a New Virtual Machine

To create a new virtual machine, start the VS2005 R2 administrative interface. You can either browse for it on the Start menu, or browse to http://FQDN:1024/VirtualServer/VSWebApp.exe. Log in as an administrative user and follow the procedure below.

In the navigation pane, under Virtual Machines, click Create.
In Virtual Machine Name, type a name for the virtual machine. If you do not want the virtual machine configuration (.vmc) file to be created in the default virtual machine configuration folder, specify a fully qualified path to the location where you want to create the virtual machine.
In Virtual machine memory, specify the amount of RAM (in megabytes) used by the virtual machine.
In Virtual hard disk, do one of the following:
- Select "Create a new virtual hard disk". Next, to set the size of the virtual hard disk, specify a value in Size, and then select either MB for megabytes or GB for gigabytes.
- Select Use An Existing Virtual Hard Disk. If the virtual hard disk (.vhd) file is located in a folder whose location is specified in Virtual Server Search Paths, you can select the .vhd from Location. Otherwise, in File name (.vhd), type the complete path to the location of the .vhd file.
- Select Attach A Virtual Hard Disk Later to create a virtual machine without a virtual hard disk.
Under Virtual Network Adapter, in Connected To, select a networking option from the drop-down menu.
Click Create.

Installing a Guest Operating System

Earlier in this daily drill down, I provided you with the list of guest operating systems supported by VS2005 R2. If the guest operating system is supported, there are a few different ways that it can be installed. You can use a startup CD or image file, or you can use a startup disk.
If you are using a startup CD or image file, open the Administration Web site, point to Configure under Virtual Machines, and click the appropriate Virtual Machine. In Configuration in the lower part of the page, click CD/DVD, do one of the following, and then click OK:

Insert the startup CD for the operating system into the CD drive on the physical computer running the Virtual Server service. Next, click Physical CD/DVD drive, and, if necessary, select the corresponding CD or DVD drive letter from the drop-down menu.
Click Known Image files. If the ISO image (.iso) file containing a startup CD image is located in the default folder (\Documents and Settings\All Users\Documents\Shared Virtual Machines\), it is available from the drop-down menu. Otherwise, in Fully Qualified Path To File, type the complete directory path to the image file.

In Status, point to the virtual machine name, and then click Turn On. Once the virtual machine is turned on, point to the virtual machine name, and then click Remote Control.
Once you are connected to the virtual machine, you can proceed with the installation of the operating system.
Installing from a startup disk is a slightly different process. When you reach the Configuration pane, click Floppy Drive, and do one of the following:

If you have a system floppy disk, insert it into the floppy disk drive, click Physical Floppy Drive, and if necessary, from the drop-down menu select the corresponding floppy drive letter.
If you have an existing virtual system disk located in the default directory (\Documents and Settings\All Users\Documents\Shared Virtual Machines\), it is available from the Known Floppy Disks drop-down menu. Otherwise, in Fully Qualified Path To File, type the complete directory path to the .vfd file.

Installing the Virtual Machine Additions

Finally, you need to install the Virtual Machine Additions on each virtual machine. This component includes features designed to improve the integration and performance of a virtual machine. A guest operating system can not be used efficiently until the Virtual Machine Additions is installed. Since it is not installed by default when you install R2, you must do so afterwards using the process outlined below.

Open the Administration Web site.
In the navigation pane, under Virtual Machines, point to Configure, and click the appropriate virtual machine.
In Status, point to the virtual machine name, and click Turn On.
Once the virtual machine has started, point to the virtual machine name, and click Remote Control.
Log on to the virtual machine using an account with administrative privileges.
Once the guest operating system is loaded, press the HOST KEY to release the mouse pointer, and then in the lower-left corner, under Navigation, click Configure virtual_machine_name.
In Configuration, click Virtual Machine Additions, and click Install Virtual Machine Additions. Click OK.
Under Status, point to the virtual machine name and click Remote Control.
Click in the Remote Control window to return to the guest operating system. The Virtual Machine Additions installation wizard will start. Proceed through the wizard.
Once the wizard is complete, you will be prompted to restart the virtual machine to complete the installation.

You'll now have a fully functional VS2005 R2 server, and a virtual machine running inside of it

**patris1** · 2010-05-23, 10:30 PM

کد:

http://articles.techrepublic.com.com/5100-22_11-5412043.html

Takeaway: Microsoft Virtual Server 2005 gives network administrators an easy way to consolidate multiple servers and operating systems on one computer. But in order to use it, you must know how to configure virtual servers. Here's how it's done.
Is your data center getting hot and crowded? Do you have older servers running legacy applications? Would you like to be able to remove some older hardware from expensive maintenance contracts? Do you want to make full use of the power of your new hardware?
If you answered yes to these questions, consider virtualizing some of your physical servers. Rather than have a separate physical server for every small application and service, run lighter-load services on virtual server instances. This lets you maintain the isolation of an application while making better use of your existing hardware. Microsoft's answer to creating virtual servers is to use its newest entry in the virtual server market: Microsoft Virtual Server 2005 (VS2005). Here's how to provision and deploy virtual servers inside VS2005.
Author's note

In the article "Preparing to deploy Microsoft Virtual Server 2005," I discussed deployment planning for the actual VS2005 installation. In this section, I'll go over some things you should consider as you begin to deploy virtual machines on your VS2005 server.
Deployment planning

First, keep in mind the systems that you can actually run inside VS2005. Most versions of Windows are supported as guest operating systems. All versions of Windows Server 2003 and Windows 2000 Server, with the exception of the Datacenter varieties, are supported, as is Windows NT 4.0 SP6a.
You might be wondering if you can run the latest version of Red Hat or SuSE under VS2005. From a technical perspective, there's no reason that various flavors of Linux can't run inside VS2005. However, Microsoft doesn't support this scenario, so you're on your own if you try it.
Limitations

Clients running inside VS2005 have some limitations that are important to understand. On the memory front, each client is limited to 3.6 GB of RAM, no matter how much RAM is in the host server. The VS2005 server as a whole can support up to 64 GB of RAM.
One area that is confusingï¿?and an area where Microsoft is lagging behind industry frontrunner VMWareï¿?is processor use. VS2005 comes in two editions: Standard and Enterprise. The Standard edition can make use of up to four system processors, whereas the Enterprise flavor supports up to 32 physical processors. However, unlike VMWare's GSX and ESX offerings, clients running inside VS2005 cannot use more than a single processor, effectively eliminating VS2005 for high-end use until this situation is corrected. Plans to address this shortcoming are on the slate.
Some people think that the whole of VS2005 can't use more than a single processor. In reality, the VS2005 installation can use every processor in the system, but the individual clients will never see more than a single processor.
Before you deploy an application on a VS2005-hosted client, ask yourself if the application can run smoothly on a single processor. If not, leave the app on a multiprocessor server until Microsoft releases a version of VS2005 in which clients can use symmetric multiprocessing (SMP).
Storage considerations

In your calculations, make sure to consider disk space, although you'll quickly find that there are few limits to the different ways by which virtual servers can access storage. A virtual server can have up to four IDE devices (a combination of CD-ROM drives, VHD, or virtual hard disk files, pointers to ISO image files).
VHD files are where the meat of the virtual server resides. An IDE-based VHD file can be up to 127 GB. If you install a virtual SCSI adapter in your virtual machine, you can add up to seven SCSI-based VHD files, each up to 2 terabytes. You can install up to four SCSI adapters inside a virtual server, providing a total of up to 28 SCSI devices in the virtual machine. You don't actually need a real SCSI adapter, either. You can store the SCSI-based VHD file on a NAS unit on the network or on a fibre channel array. Or, you can actually hang a huge SCSI storage unit off the VS2005 server and use it for your VHD files.
Licensing

For licensing purposes, consider any virtual servers to be real, deployed servers on your network. Just as you need a Windows license for a new physical Windows server on your network, you also need a license for any virtual Windows servers you deploy. Don't forget about the VS2005 server itselfï¿?it also needs a valid Windows license. So, if you have four virtual Windows servers on your VS2005 server, you'll actually need five Windows server licenses: four for the virtual servers and one for the VS2005 server.
Virtual machine creation

To create a new virtual machine, start the VS2005 administrative interface (Figure A). You can either browse for it on the Start menu, or browse to http://{your VS2005 server}:1024. Log in as an administrative user.
Figure A

The VS2005 administrative interface Click Create under the Virtual Machines heading in the left-hand part of the administration window. This brings up a form you need to fill out with the details for the new virtual server. The form shown in Figure B is completed, but I'll go over all of the options. Table A contains virtual server creation information.
Figure B

Create a new virtual machine.

Virtual server creation information After you've filled in the fields, click the Create button at the bottom of the form. You'll get an overview of the system's configuration. If you don't get an overview, select Configure | { your virtual server } from the Virtual Machines menu option. Either way, you'll get something similar to the screen shown in Figure C.
Figure C

Virtual server configuration overview Decide on a CD-ROM device

This is an area where you'll need to make more decisions. If your VS2005 server has only a single CD-ROM drive, and you have your Windows Server CD in hand, you can most likely just pop the CD into the VS2005 system's CD-ROM drive and be on your merry way. However, you might have a VS2005 server with multiple CD-ROM drives, or you might have only an image (an ISO file) of a CD-ROM drive handy. In these cases, you might need to decide how you want the virtual server to handle CDs.
To look at your options, click the CD/DVD option on the virtual machine configuration. The screen shown in Figure D pops up.
Figure D

Virtual machine CD/DVD management On this screen, you can add or remove a virtual CD/DVD device to or from a server. You can also dictate which virtual IDE channel a device should be connected to. In addition, you need to decide how you want media to be made available to the virtual server's CD device.
To remove a CD/DVD device, check the box marked Remove and then click OK. To add a CD/DVD device, click the button labeled Add CD/DVD Drive. When you click the Add button, another entry will appear on the screen with a new label. If you add a second CD drive, for example, you'll see two device entries with the second name being Virtual CD/DVD Drive 2.
For each CD/DVD drive, you need to tell the virtual machine which IDE connector the device is attached to. Just like a physical server, your choices are IDE 1 (Primary) and IDE 2 (Secondary). For each IDE channel, you can have up to two devices, numbered channels 0 and 1. You cannot add CD/DVD devices to a virtual SCSI bus in VS2005, so you're limited to four such devices per virtual server. When you click the selector button next to the Attachment option, channels that are occupied by other virtual hardware are marked "in use."
Finally, provide your new virtual server with details on how it should load media into the virtual CD/DVD drive. Here you have three options: Don't put any media in the virtual drive (No media); attach a physical CD/DVD drive to the virtual drive; or point the virtual drive at an ISO file residing on the VS2005 server (known image files). If the ISO you want to add doesn't show up in the list, type the ISO file's path in the appropriate box at the bottom of the window. In any case, click OK when you're done. For this article, I have a physical Windows Server 2003 CD that I've put into my VS2005 server's CD-ROM drive.
Networks

During the process, you told your virtual machine which physical network adapter it should use. After it starts up, your new virtual machine will use this adapter for all communication, including DHCP requests. The traffic over this link can't be intercepted at the VS2005 server and is completely isolated.
To just get up and running, this is all you need to do. Later on, you can do things such as create networks for virtual machines to communicate with one another. This could be useful if you need private communication between virtual servers. You can find steps to set up private networks for use by virtual servers in the VS2005 Help.
Enable VMRC

Before you get to the business of finally installing an OS inside your virtual server, you should start the Virtual Machine Remote Control (VMRC) client. VMRC is a protocol developed by Microsoft to manage virtual machines. The protocol is used by the Web-based administrative tools as well.
To enable VMRC, go to Virtual Server | Server Properties | Virtual Machine Remote Control (VMRC) Server. Figure E shows the configuration screen.
Figure E

The VMRC configuration screen Check the Enable box at the top of the window. To get started, that's all you need to do. Obviously, if you begin to use VS2005 in a production environment, you should consider installing an SSL certificate in order to protect the management traffic. If you don't enable VMRC, you won't be able to interact with a running virtual machine.
Installing an operating system inside your VM

At this point, you've created your virtual server. You now have a computer set up and ready to go, but it doesn't have an operating system. If you try to boot this OS-less system, you'll receive the typical "non-system disk" or "disk error" message that you'd see if you tried to boot a regular computer with no OS. The solution: Install an operating system.
Power up the virtual server

Before you proceed, make sure that your CD device is set up correctly and that installation media is present. To turn on your virtual server, choose { your virtual server } | Turn On from the Master Status screen, as shown in Figure F. Next, click the little thumbnail picture of your server's console.
Figure F

The master status screen provides a snapshot of all virtual servers. From here, install the server operating system just as you would for a regular physical server. You'll be able to interact with your server just as if you were sitting at the console. The screen in Figure G shows a fully loaded Windows Server 2003 installation being used via a Web browser and running inside the VS2005 server.
Figure G

The VS2005 remote control window One important note: While you're loading the operating system, your mouse pointer will be captured each time you do something inside the virtual server. To release the mouse pointer back to the host system, press the right [Alt] key. The left [Alt] key will not release your pointer. To send a [Ctrl][Alt][Del] to a virtual machine, press [Right Alt][Del]. Don't use [Ctrl][Alt][Del] because this keystroke will be captured by the host system.
Install Virtual Machine Additions

After you've loaded your operating system, you'll probably notice that it looks pretty bad. The resolution will most likely be low, and you'll eventually get annoyed that your mouse pointer is continually captured by the virtual machine. Fortunately, all of this can (and should) be fixed with the installation of the Virtual Machine Additions. The Virtual Machine Additions do the following:

Install a virtual SVGA driver that enables higher resolution.
Integrate the mouse pointer better. You no longer have to release the mouse pointer to use it between the virtual server and the management station.
Allow time synchronization between the host server and the virtual machine.
Provide increased performance for the virtual machine.
Provide heartbeat capability for improved virtual machine monitoring.

The Virtual Machine Additions work only for Windows virtual machines. To install the Virtual Machine Additions, make sure your virtual server is turned on and you're logged in as an administrator and sitting at the desktop. Next, from the management features beneath the server desktop, click Configure { your virtual machine }. In Configuration, click Virtual Machine Additions, click Install Virtual Machine Additions, and then click OK.
Now, go back to your virtual server's console and follow the steps in the wizard. After you install the Virtual Machine Additions, you'll have to restart your virtual server. You'll now have a fully functional VS2005 server and a virtual machine running inside of it

**patris1** · 2010-05-23, 10:35 PM

کد:

http://articles.techrepublic.com.com/5100-22_11-5427402.html?tag=rbxccnbtr1

Takeaway: Virtual Server 2005 gives network administrators a new tool to consolidate multiple servers running various operating systems on a single machine. Here's how you administer the VS2005 using its Web administration tool to get the most out of the product.

If you've installed Virtual Server 2005 and successfully gotten a virtual machine up and running, you're probably starting to see the power, flexibility, and cost-savings potential for virtual machine technology. As with the introduction of any new technology, Virtual Server 2005 brings with it a learning curve and a new administration tool to handle.
Web administration

The most obvious VS2005 administration tool is the Web front end, shown in Figure A.
Figure A

The Virtual Server 2005 Web administration tool There are three panes in this window. In the left pane is the menu bar, which I'll discuss in more detail later. On the right are two windows stacked on top of each other. The top window provides a quick status for all running virtual machines, including a thumbnail screen shot, a shortcut menu, and a CPU usage graph. Below that is the VS2005 event log.
The main menu

Outside of actually administering a virtual server itself, a lot of your administration duties will be accomplished using the menu options on the left side of the VS2005 administration window. Table A provides a high-level overview of each major functional area.
Table A

Virtual disks

The concept of a virtual disk can create a lot of confusion. It doesn't help that VS2005 offers several kinds of disks. After you read this section, you'll probably see why there are so many choices available in this area and how each one can be beneficial.
There are four types of virtual hard disks available:

Dynamically expanding virtual hard disk: A dynamically expanding hard disk file is only as large as the entire contents of the virtual hard drive. For example, if you have a single virtual disk assigned to a virtual machine, and the operating system installation takes 2.5 GB, the size of the file will be 2.5 GB until you add more contents. This type of disk expands only to the maximum size specified when you created the virtual hard drive. If you need more space, you can add it later.
Fixed-size virtual hard disk: A fixed-size virtual disk is created in a way similar to that of a dynamically expanding disk, except that the associated VHD file is created at the final size. For example, if you create a 16-GB fixed-size disk, the VHD file on the host will always be 16 GB, regardless of what is stored on the virtual disk. Be careful with these, since increasing the size after the initial creation can be difficult.
Differencing virtual hard disk: This is probably the most confusing type of virtual disk available. A differencing hard disk basically lets you have multiple, different instances of virtual machines all using the same disk. However, in these cases, the virtual machine actually uses two virtual disks: a parent dynamic or fixed virtual hard disk and this differencing virtual disk. Any changes made to the parent disk are written to the differencing disk rather than being recorded in the parent's VHD file. A differencing disk is particularly useful if you want multiple and similar server configurations, or if you want to maintain the base image for testing.
Linked virtual hard disk: If you have a physical hard drive that you want to convert to a virtual disk, you can link that particular physical drive to a new fixed virtual disk with this option. (You can't link using a dynamic disk.) You can't use a linked disk for a virtual server's startup volume. Further, you can't use a differencing disk in association with a linked disk. Finally, if the physical disk exceeds 127 GB, you can't attach it to a virtual IDE controller. Instead, attach it to a virtual SCSI controller, which supports volumes of up to 2 TB.

Virtual disk actions

To manage virtual disks, choose the Inspect option in the left-hand menu bar. Select a virtual disk to inspect and click the Inspect button. You'll see the screen shown in Figure B.
Figure B

Select a virtual disk to manage. The number of options you'll see on the next screen depends on the type of disk you're inspecting. If the selected disk is dynamic, you'll have two optionsï¿?Convert and Compactï¿?as shown in Figure C. The third option, Merge, is available only for differencing virtual disks.
Figure C

Management options for a dynamic virtual disk If you select a dynamic or fixed virtual disk type, you can convert between the two typesï¿?from fixed to dynamic and vice versa. This is useful if you want to expand the size of a fixed virtual disk. This option is not available for a differencing virtual disk.
For dynamic disks, you'll also see a Compact option that lets you squeeze empty space out of a dynamic virtual disk. I recommend that you make sure your host has sufficient disk space for the maximum size of dynamic disks rather than have to do this.
Finally, a third option, Merge Virtual Hard Disk, is available for differencing disks. This management option lets you do one of two things: (1) write the contents of a differencing disk back into a parent and delete the differencing disk; or (2) write the data from both the parent and the differencing disk into a new file and leave both original disks intact.
Virtual networks

Virtual networks provide many ways to connect your virtual servers to the network. In a previous article in this series, you might have read that you can attach your virtual server's network adapter directly to a physical network adapter, but you can also do a lot more.
Keep in mind that all virtual networks are separate from one another. If you have a single VS2005 server, and all of your virtual servers have IP addresses from different subnets, you'll need a router in order to establish communications between the different servers.
Each virtual network can also have a DHCP server. This isn't an Active Directory-integrated DHCP server, but it does provide an address to clients on the virtual network. To configure DHCP services for a particular virtual network, select Virtual Networks | Configure from the left-hand menu, and select the virtual network you want to configure. Next, from the virtual network configuration page, click DHCP Server. A page like the one shown in Figure D will appear.
Figure D

The virtual network DHCP server configuration page From this page, make the appropriate changes to the virtual DHCP server configuration, and click OK when you're done. The Virtual Networks configuration comes in handy when you want to connect virtual servers to different networks or when you want to establish a virtual DHCP server on a virtual network.
Virtual Server configuration

The last major item I'll cover in the Web GUI is the configuration of the Virtual Server product itself. This part of the configuration lets you determine how the overall product actually operates, including who is allowed to administer virtual servers. Obviously, this is an area you'll want to pay attention to.
The first entry in the Virtual Server section, Server Properties, is where most of the configuration options are located. This screen, shown in Figure E, also provides you with details about your Virtual Server installation, such as the uptime for the host, the versions of VS2005, and the administration Web site that you're running.
Figure E

Overall VS2005 configuration At the bottom of the screen, you'll notice a number of configurable properties. These are all important, but the one you should focus on is the Security option. By default, members of the Administrators group are allowed to administer VS2005 virtual servers. If you want to add other administrators, click Virtual Server Security and add entries to the screen, as shown in Figure F.
Figure F

These users can administer VS2005. Permissions

Notice the different permission levels that can be assigned to different administrators. If you want to limit someone to a "look, but don't touch" capability, then provide View access only. To completely remove an administration user or group, select the Remove check box and then click OK. To add a new security entry, click Add Entry.
Other items

The next two items, Scripts and Search Paths, can make life easier as your virtual server infrastructure begins to grow. Now, rather than manually intervening when certain events take place, you can script the resulting actions using cscript, the command-line version of Windows Scripting Host. You can write scripts that take action in any of the following cases:

Virtual Server starts
Virtual Server stops
Any virtual machine is turned on
Any virtual machine is restored
Any virtual machine is turned off (saved)
Any virtual machine is turned off (not saved)
Any virtual machine is turned off within the guest environment
Any virtual machine is reset
No heartbeat is detected for any virtual machine
Any virtual machine experiences a guest processor error
Any virtual machine receives a warning due to low disk space on the physical computer
Any virtual machine receives an error due to low disk space on the physical computer

For example, you might want to be notified via a pop-up or an e-mail if a physical computer is running low on disk space or if a heartbeat is not detected for a particular virtual server. In either case, the risk of downtime is probable if you don't take immediate action, so being notified early is important.
Search paths provide VS2005 with places to look for .vmc (virtual machine configuration) files; .vhd (virtual hard drive) files; .iso (CD-ROM image files), and .vfd (virtual floppy drive) files. By default, only a single location is used by VS2005: C:\Documents and Settings\All Users\Documents\Shared Virtual Machines\. You can add search paths to make other locations available. For example, maybe you want to store all .iso files in C:\cdimages. If you don't add that location to this page, you won't be able to easily make use of the resource.
Allocating resources to virtual machines

One drawback to the use of virtual servers is taking a chance that a single virtual server could swipe all of the host's resources, effectively bringing down the entire virtual machine structure for that host server. If you have multiple virtual servers hosted on a physical server, you can see why this is a concern.
Fortunately, in the design of VS2005, Microsoft considered this potential and built a mechanism that prevents this from happening. This mechanism also allows you to weigh different virtual servers separately; you can basically assign a priority to a virtual server to make sure it gets host resources when needed.
To allocate resources to virtual machines, go to the Resource Allocation section in the Virtual Server configuration. You'll get a screen like the one shown in Figure G, but the percentages will be different, unless you've already adjusted resource allocation.
Figure G

CPU resource allocation for virtual machines Notice the different categories available for each server: Relative Weight, Reserved Capacity, and Maximum Capacity. In most cases, if you just want to prioritize one virtual server above another, give it a higher relative weight using a number anywhere between 1 and 10,000. When a virtual server with a higher relative weight needs more resources, they are made available at the expense of virtual servers with lower weights, so be careful with this option.
The other two fields, Reserved Capacity and Maximum Capacity, allow you to specifically allocate a percentage of a single host CPU to a particular virtual server, ensuring that the virtual server always has at least that much capacity. The Maximum Capacity setting allows you to provide maximum resource consumption (a percentage of a single host CPU) to a virtual server, ensuring that it will never run away with 100 percent of the host's resources.
After you make changes to these fields, you'll notice that blue lines appear in the CPU Usage graph, indicating these thresholds

**patris1** · 2010-05-23, 10:37 PM

کد:

http://articles.techrepublic.com.com/5100-10878_11-6155520.html

Takeaway: Virtual Server 2005 can be a powerful tool, but it doesn't always work properly. Here are some of the common problems you'll face with VS2005 R2 and how to deal with them.
This article is also available as a TechRepublic download. Virtual Server 2005 R2 (VS2005 R2) gives network administrators an easy way of consolidating multiple servers and OSs onto a single computer. Instead of using a dedicated server for every application and service you require, you can run the applications and services on virtual server instances. This allows you to continue to isolate applications and services, while making better use of existing hardware.
However, as with every piece of software that you install on a computer, there are potential problems that can arise; some easier than others to troubleshoot and resolve. Problems can occur in a number of different areas, including: networking, installing the Virtual Machine Additions component, starting virtual machines, and so on. In this article, I will outline some of the common problems that can occur with VS2005 R2, and how you can fix them.
Virtual machines and guest OSs

One of the first problems you might see when running VS2005 R2 is with the right Alt key. By default, this is the Host key; and, on some keyboards, the keystrokes used to access menus (Host Key + [Alt] + keyboard shortcut) do not work. The workaround for this problem is to designate another key as the Host Key.
To change the Host key through the Administration Web site:

Open the Administration Web site.
Under Virtual Machines, point to Configure and select the appropriate virtual machine.
From the Status page, point to the virtual machine name and press Turn On.
Press Remote Control once the virtual machine is turned on.
Press Remote Control and then press Set Host Key.
Select the option you want to use and press OK.

If your virtual machine will not start, this may be due to over-allocated CPU resources. In other words, some virtual machines have been assigned more CPU resources than others. Since only those virtual machines you have permissions for appear on the CPU Resource Allocation page, it is easy for someone to mistakenly over-allocate CPU resources to the virtual machines listed. This can prevent other virtual machines from turning on. The solution is to have a Virtual Server administrator open the CPU Resource Allocation page to verify the CPU allocation for all the virtual machines.
Hard disk problems

If your virtual machine will not start and you are using linked disks, verify that the physical linked disk is not being used. A virtual machine that uses a linked disk will not start if the linked physical disk is already in use.
When you attempt to start a guest OS from a virtual disk, you might receive the following error message:
Stop 0x0000007B
In such cases, you have more than likely installed the virtual disk on the incorrect type of controller. You can correct the problem by reattaching the virtual disk to a different type of controller. For example, if the virtual disk is currently attached to a virtual IDE controller, attach it to a virtual SCSI controller instead.
Renaming VMs

You may also encounter problems with a virtual machine after renaming it. For example, if you rename a virtual machine through Windows Explorer, the name change will not appear on the Administration Web site. The solution to this is to use the Administration Web site, instead of Windows Explorer, to rename your virtual machines.
Administration Web site

One of the most common problems people encounter after install VS2005 R2 is that they are unable to open the Administration Web site. More than likely, Internet Explorer is preventing the site from being displayed. The solution is very simple: add the URL of the site to the list of trusted sites in Internet Explorer. You can do this from the Security tab within the Internet Options dialog box, as shown in Figure A.
Figure A

Type in the URL for the Administration Web site and press Add. If you attempt to connect to a Virtual Server using Remote Desktop Connection, you may see the error "The page cannot be displayed." To resolve the problem, you need to connect Remote Desktop Connection as a console session. This can be done using the following command:
Mstsc /v:server_address /console
Another method for resolving this problem is to configure Internet Explorer to prompt for a username and password, as described below.

Within Internet Explorer, select Internet Options from the Tools menu.
Press the Security tab.
Select Trusted Sites and press the Custom Level button.
Under User Authentication, select Prompt for user name and password, as shown in Figure B.
Press OK.

Figure B

Configure Internet Explorer to prompt for a user name and password. A handy tip to keep in mind if you encounter any other error messages: Virtual Server uses the Windows event log to record errors. You can use Event Viewer to review the event log when troubleshooting any Virtual Server related errors.
Virtual Machine Additions

The Virtual Machine Additions includes features designed to improve the integration and performance of a virtual machine. A guest OS cannot be used efficiently until Virtual Machine Additions is installed. Since it is not installed by default when you install VS2005 R2, you must do so afterwards.
The installation process is very straightforward and there are very few problems that you will run into. If you are unable to install this component, check that you have the proper permissions. In order to run the Virtual Machine Additions Setup program, you require full administrative control on the guest OS.
Connectivity issues

People often run into connectivity problems with the guest OS when running any type of virtualization software. To successfully network a guest OS in VS2005 R2, the network adapter for the guest OS must be assigned the correct IP address.
The IP address of the virtual machine network adapter must be on the same physical subnet as the physical computer's network adapter. Also, verify that you have created a virtual network and assigned it to the Microsoft Loopback Adapter. The Microsoft Loopback Adapter provides the network connection between the guest OS and the host OS.
Finally, you may also see networking problems between guest OSs on the same network. Any virtual machines on the same network that have the same Media Access Control (MAC) address will not recognize each other. The solution is to configure the network adapter for each guest OS with a unique MAC address.
You can configure the MAC address using the steps described below.

Open the Administration Web site.
Under Virtual Machines, point to Configure and select the appropriate virtual machine.
Select Network Adapters.
In the Connect To section for the appropriate network adapter, select the virtual network that you want to connect the network adapter to.
In the Ethernet (MAC) address section, select Static and type in a unique MAC address.

Final thoughts

As you can see, there are a handful of common problems that can occur when you are running VS2005 R2, most of which are relatively easy to resolve. The majority of these problems can be avoided by paying close attention to installation requirements and directions. If you are unable to resolve the problem using the recommendations described throughout this article, you have probably encountered a more uncommon problem; one that will require a little research to find a solution

**patris1** · 2010-05-23, 10:39 PM

کد:

http://articles.techrepublic.com.com/5100-10878_11-6155924.html

Takeaway: Virtual Server 2005 R2 allows you to host other operating systems on your server. Things get tricky when you want to run multiple virtual machines. Here's what you'll encounter.
This article is also available as a TechRepublic download. Virtual Server 2005 R2 (VS2005 R2) gives network administrators an easy way of consolidating multiple servers and OSs on to a single computer. Instead of using a dedicated server for every application and service you require, you can run the applications and services on virtual server instances. This allows you to continue to isolate applications and services while making better use of existing hardware.
VS2005 R2 can support up to 64 virtual machines (VMs) on a single host. In reality, however, the number of VMs you can successfully run on one host will depend on the physical hardware -- specifically the amount of RAM and available hard drive space. In this article, I'll talk about some of the aspects you need to consider when deploying multiple VMs under VS2005 R2. I'll also discuss any requirements unique to running multiple VMs.
System requirements

The number of VMs you plan to run simultaneously on a host will have an impact on the host computer's system requirements -- specifically on the amount of RAM and hard drive space required.
Memory

Memory is critical to successfully run multiple VMs on a single host. The minimum requirement to install VS2005 R2 is between 256 and 512 MB, depending on the host platform you are running. These values, however, are just starting points. If you plan to run more than one guest OS simultaneously, you need to begin increasing the RAM. A general guideline to follow is to add an additional 32 MB of RAM for each VM.
Note: When calculating the amount of RAM, don’t forget to factor in the RAM required to run host OS.
Disk space

Adequate disk space is just as important as adequate RAM, since each VM will have its own page file and dynamically expanding virtual hard disk. Additional space may be required on top of this if you plan to put your VMs into a saved state. VS2005 R2 requires a minimum of 2 GB free disk space. This amount will therefore need to be adequately increased for each VM you plan to install.
Multiple processors can improve the performance of the host OS and Virtual Server 2005. However, guest OSs themselves can not take advantage of multiple processors.
VM settings

If you are running a single VM on your host, you don’t have to be too concerned about the settings. It's when you get into a multiple VM configuration that you need to start thinking about them, because some of the settings can affect all the VMs running on a host, not just one. Let’s take a look at some of the settings you need to pay close attention to.
File name

When you create a new VM, you are prompted to provide a file name. This is the name assigned to the VM configuration (.vmc) file. This file name can not exceed 150 characters and if you are running multiple VMs, each one must have a unique file name.
CPU Resource Allocation

You need to pay close attention to the CPU Resource Allocation settings when running multiple VMs. For example, if one of your VMs will not start, it may be due to over-allocated CPU resources. In other words, some VMs have been assigned more CPU resources than others.
Since only those VMs that you have permissions to appear on the CPU Resource Allocation page, it is easy for someone to mistakenly over-allocate CPU resources to the VMs listed. This can prevent other VMs from turning on or affect the performance of VMs running in the background.
Virtual hard disks

Each VM uses a virtual hard disk (.vhd file). This is where a VM will store files and install programs -- the same way that the host OS uses a physical hard disk. When you are running multiple VMs on a host, remember that a virtual hard disk can only be used by one VM at a time. Therefore, if you plan to run two VMs simultaneously, you will require two virtual hard disks.
Video settings

Since each guest OS runs independent of each other, each one can be configured with different video resolution settings. This will have a slight impact on performance as you switch between VMs running simultaneously. It will take a few seconds for Virtual Server to change to the correct resolution settings as you switch between VMs.
COM and parallel ports

Any devices attached to the host's COM port are accessible under a guest OS. If you plan to run multiple VMs, keep in mind that any device attached to a COM port is only accessible to one VM at a time. If you want to use the device under another guest OS, the other VM must first release the COM port (you can accomplish this by shutting the VM down).
As with COM ports, any devices that are attached to the parallel (LPT1) port is only accessible by one VM at a time. No other guest or host OS will be able to use the device until the VM is shut down.
Floppy drives

Each VM is configured with a single floppy drive. You can configure a VM’s floppy drive to either use a physical floppy disk drive or a virtual floppy disk (.vfd) file.
A virtual floppy disk file can be shared between multiple VMs if the file has been marked as read-only. In the case of a physical floppy disk, this can only be used by one VM at a time.
If you have multiple VMs that are configured to start automatically, consider altering the properties of each one to stagger the start times. By configuring the Seconds to delay automatically starting a VM option, you can prevent the VMs from starting at exactly the same time and thereby reduce the demand placed on the host computer’s physical resources.
Networking your VMs

Multiple VMs can be connected to the same virtual network. Assuming you have already created a new virtual network through the Virtual Server Administration Web site, you can the virtual network adapter for any VM to the virtual network.
You can do this by editing the configuration of a VM via the Administration Web site. Open the Network Adapter properties for the appropriate VM and select the virtual network that you want to connect the virtual network adapter to. There is no limit to the number of VMs that you can connect to a virtual network.
Switching between VMs

Finally, you should know how to actually switch from one running VM to another. Switching between VMs that are running simultaneously is quick to do. You can use the Host key, which by default is the right Alt key. If you have installed the Virtual Machine Additions for each VM, you can switch between them by using your mouse

موضوع: تنظيمات Virtual server

پیوند

ابزارهای موضوع

نمایش