How to improve Virtual Server Performance

Virtual Server provides an excellent solution for many companies today.
To "get more with less" the following article will provide you with guidelines how to improve
Virtual Server so that you can load more applications/users on the same hardware,
without the need to buy extra hardware.

�
Recommended Server Specification:
�

1. Dual - Quad CPU's with Quad Core and Virtualization Technology (VT) support.
   
2. Memory -�8-32 GB RAM.
   

�

• The size of the memory required for the server should be decided after testing in the lab and

�������������� �calculated based on the number of users and the average size of RAM required for a virtual machine.
�
��� c. Optional: DVD + Floppy.
��� d. Backup Battery for Raid Adapter.
��� e. Raid Adapter with at least�512 RAM, that support Raid 1 with Hot Spare disk and Raid 5/6/10.
��� f. Three disks of at least 74 GB Ultra SCSI 3�15000 RPM or 74 GB SAS 15000 RPM (Raid 1 + Hotspare).
�
��������� Note: Its recommended to dedicate a unique Raid 5/6/10 logical disk for hosting the Virtual Machine/s files.
�
���� g. Dual Power Supply.
���� h. Remote Management Adapter.
�����i.�Dual Network Adapter 1-10 GB (Server Adapter) with an option for�"Teaming" (Network Adapters recommended)
������������������ and an option for 802.1Q support.
�
��� �j. Optional (But Recommended) a add on - Dual Network Adapter 1-10 GB (Server Adapter) with an option for "Teaming"
�������������� (Network Adapters recommended) and an option for 802.1Q support - This will allow you to increase the server
�������������� network performance and allow the host server to host a virtual servers from a few VLANS (Virtual LAN).
�
���� k. Optional - A dual port FC (Fiber Channel) HBA (Host Bus Adapter) 4 GB, to allow connection to SAN (Storage Area Network).
�
�
�
How to choose the correct operation system?
�
Most of the new servers today support running Windows 200x 32 Bit and
Windows 200x x64 Bit.
�
The first step is required to choose the runtime environment for�the operating system.
�
�
The recommended�runtime for a host that serve as dedicated Virtual Server host is:
������� �Windows 200x X64 Bit�Edition.
�
�

• Its recommended t verity that you are using the latest operating system version and latest hotfixs/service packs.

�

• Its recommended to update the server drivers and hardware Firmware/BIOS�every three months.

�
�
The second step required is should choosing the correct edition of Windows 200x
�
Compare the Editions of Windows Server 2003
�
http://www.microsoft.com/windowsserver2003/evaluation/features/comparefeatures.mspx#64Terminal%20Services
�
Evaluate the Windows Server 2008 Public Beta today
�
http://www.microsoft.com/technet/prodtechnol/beta/lhs/default.mspx
�
Note: Its recommended to consider using Windows Server 200x with limited extra services.
�
�
The following guidelines should be consider during the design on Virtual Server solutions and
� Virtual Server maintenance:
�

1. Use a dedicated server for Virtual Server tasks.
   
2. Verity that third party products are supported under Virtual Server environment.
   
3. Consider�using "User Profile Hive Cleanup Service":
   

�
����� http://www.microsoft.com/downloads/details.aspx?FamilyID=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
�
��� 4. Consider using a large page file:
�
������ How to overcome the 4,095 MB paging file size limit in Windows

������http://support.microsoft.com/?id=237740
�
�
����� How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
�
����� http://support.microsoft.com/kb/889654
�
��� 5. Go to "Control Panel" -> "System" -> "Advanced" -> and change:
�

1. "Visual Effects" to "Adjust for best performance".
   
2. "Advanced" -> "Adjust for best performance of:" ->
   
3. "Advanced" -> "Memory usage" ->
   

�

• The settings of section "a" and "b" should be tested before applying them to production systems.

���������� �If you not sure if you need to change this settings, leave them with the default settings.
�
�
���� 6. Optimize memory management by editing "boot.ini" file:
�
���� Available switch options for the Windows XP and the Windows Server 2003 Boot.ini files
�
���� http://support.microsoft.com/kb/833721
���

• Changing "boot.ini" settings should be tested in a lab before being implemented on production systems.

����������� If you are not sure if you need to change these settings, leave them with the defaults settings.
�
�
���� 7. Use latest RDP client:
�
�
��������� Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876)
�
��������� http://www.microsoft.com/downloads/details.aspx?FamilyID=26f11f0c-0d18-4306-abcf-d4f18c8f5df9&DisplayLang=en
�
��������� Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 (KB925876)
�
��������� http://www.microsoft.com/downloads/details.aspx?FamilyID=cc148041-577f-4201-b62c-d71adc98adb1&DisplayLang=en
�
����������Windows Vista have a build in Remote Desktop Connection (Terminal Services Client 6.0).

�
���� 8. Design a separate VLAN (Virtual LAN) to host the virtual server.
�
���� 9. Implement QoS (Quality of Services)�to improve the network performance.
�
���� 10. Don�t allow using RDP (Remote Desktop Connection) for regular virtual machine management
������������� Most of the operations can be done from the remote management web site or/and using a
������������� management tools like:
�
������������� Virtual Machine Remote Control Client Plus (VMRCplus)
�
������������� http://www.microsoft.com/downloads/details.aspx?FamilyID=80ADC08C-BFC6-4C3A-B4F1-772F550AE791&displaylang=en).
�
�
���������������Operation Manager 2007, Virtual Machine Manager 2007
�
�������������� www.microsoft.com\virtualization
�
�����11. Design and implement�a hardware limitation for each virtual machine.
�
���� 12. Design and implement a security boundaries, so only one Administrator (or limited Administrators) will have a full control
�����������������on the Virtual Server. A delegate permission per Virtual Machines is recommended.
�
���� 14. In WAN (Wide Area Network) environment consider to deploy�a�traffic compression�device/software.
�
���� 15. Reduce the using of Virtual Server scripts or/and Virtual Machine scripts.
������������� In case that you must use scripts, consider to use WMI/VBS/Power Shell scripts,
������������� instead the old legacy batch scripts.
�
�����16. Disable unnecessary services/option in the user GUI (Graphical User Interface) such as:
�
������������� "Wallpaper", "Active Desktop", "Screen Saver"�etc.
�
����� 17. Eliminate a real time scan and schedule scan of the virtual machine/s files and hosting folder/s.
�
����� 18. Schedule Compact of the VHD's and host disks defrag.
�
����� 19. You can use "Microsoft � Windows Server � 2003 Performance Advisor" to optimize the server performance:
�
��������� Microsoft � Windows Server � 2003 Performance Advisor
�
�������� http://www.microsoft.com/downloads/details.aspx?FamilyID=09115420-8c9d-46b9-a9a5-9bffcd237da2&DisplayLang=en

����� 20. When you create a new virtual machine, use a virtual SCSI Disks and install VM-Additions on the guest machine.
�
����� 21. Consider to use:
�
��������� The Microsoft Windows Server 2003 Scalable Networking Pack release
�
���������http://support.microsoft.com/kb/912222
�
�
�
Further information can be obtain from:
�
Improving performance
�
http://www.microsoft.com/technet/prodtechnol/virtualserver/2005/proddocs/vs_operate_using_perfTune_tune.mspx?mfr=true
�

Using Microsoft Virtualization Technologies: Today and Planning for Tomorrow
�
http://download.microsoft.com/download/6/1/6/6165746e-5740-47ef-ab9f-ea5d30049a64/VirtualizationSeminarZurich.pdf

�

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.