Project Virtual Reality Check (VRC) is a joint venture of Log•in Consultants and PQR, who have researched the optimal configuration for the different available hypervisors (hardware virtualization layers). The project arises from the growing demand for a founded advice on how to virtualise Terminal Server and Virtual Desktop (VDI) workloads. Through a number of researches, Log•in Consultants and PQR show you the scaling possibilities for Terminal Server environments as well as Virtual Desktops.
We invite you to download our whitepapers and draw your own conclusions from the different research results. After registration you have acces to all documents. You can of course also set up your own research environment and see which environment best suits your situation.
VMware Update Manager (VUM) provides a patch management framework for VMware Virtual Infrastructure. IT administrators can use it to patch VMware ESX, Windows, and certain versions of Linux virtual machines. As data centers get bigger, performance implications become more important for patch management. This study covers the following topics:
More and more organizations are choosing VMware Infrastructure to virtualize their mission‐critical applications (Active Directory, Exchange, SharePoint, SQL Server) to create a flexible, easily administered virtual infrastructure. Virtual machines (VMs) and any applications they contain must be protected against failure. Typically, in the virtual world, this is done by performing an image‐level backup of the whole machine (for instance, using VMware Consolidated Backup). This method results in what is known as a crash‐consistent image. Restoring a crash‐consistent image is essentially equivalent to rebooting a server after a hard reset. For operating systems, this has not been an issue, since they can easily handle this type of activity. For database applications as well as for applications featuring replication, however, such a restore will often result in lost data, data corruption, or application failure. To illustrate this concept, let’s review the consequences of using different VM disaster recovery methods for one of the most common mission‐critical applications: a Microsoft Active Directory domain controller (DC). Depending on the solution used, the following results will be achieved:
De jongens van XtraVirt hebben hun guide over VI in a Box bijgewerkt.
In 2007, like others in the global VMware community, Xtravirt developed a common methodology to install and run VMware ESX 3.x on VMware Workstation 6 together with a shared storage solution based upon an iSCSI software target. We called it ‘VI3 in a box’.
This allowed users and professionals in the IT community to create simple and cost effective VI3 infrastructures to test, learn about and demonstrate these environments.
Upon the release of VMware ESX 3.5 we found that this methodology did not continue to hold true. Although still possible to install ESX 3.5, when attempting to start a nested Virtual Machine on the ESX VM, the ESX VM panics, and a stop message appears.
However, with the release of VMware Workstation 6.5, build release 99530, a revised solution now exists.
This white paper documents the process to install and configure ‘VI3.5 in a box’.
VMware® VirtualCenter uses a database to store metadata on the state of a VMware Infrastructure environment. Performance statistics and their associated stored procedure operations constitute the largest and the most resource‐intensive component of the VirtualCenter database. Hence the performance of your VirtualCenter database depends upon the frequency at which you collect performance statistics and the level of detail of the statistics you store. VirtualCenter 2.5 features a number of enhancements that are aimed at greatly improving the performance and scalability of the performance statistics operations in the VirtualCenter database. The purpose of this study is to present the performance results of tests we conducted to validate these performance enhancements and to provide best practices information for configuring a VirtualCenter database. The study also provides information for sizing the server you use to host the VirtualCenter database based on these performance results. Although the new features in VirtualCenter 2.5 benefit users with any of the supported databases, the examples and performance data presented in this study are specific to Microsoft SQL Server and the paper assumes that you have a working knowledge of SQL Server.
This study covers the following topics:
“VirtualCenter 2.5 Database Overview” on page 2
“Performance Statistics Collection in VirtualCenter” on page 2
“Performance Statistics Database Operations and Their Effects on Performance” on page 3
“Performance Enhancement in VirtualCenter 2.5” on page 3
“Performance Tests” on page 4
“Performance Results” on page 5
“Sizing the VirtualCenter Database Server” on page 7
“Performance Best Practices” on page 8
“References” on page 9
“Appendix A: Configuring Performance Statistics Levels and Rollups with VirtualCenter” on page 10
“Appendix B: Configuring Memory Size for SQL Server” on page 11
There are numerous ways to apply a configuration or security setting onto a group of servers within a Presentation Server environment. Because policies are so unique, diverse and customizable, there is no single, correct method toward policy design. However, this document will give the key areas to consider when deciding on the appropriate approach to implementing a setting using a policy. This design consideration will look at the following types of policies and the common practices associated with them:
Citrix Presentation Server policies: These policies are defined within the management console on Presentation Server and only apply to connections using the Citrix ICA protocol but not the Microsoft RDP protocol. Presentation Server policies also allow for the configuration of Presentation Server-specific options like Session Printers and Progressive Display. The power of these policies is that they have the ability to be filtered based on users, location and even the method for launching the published applications. Many of these filters are only available within Presentation Server.
Active Director y policies: These policies are configured within Active Directory. They are applied to organizational units (folders), domains, sites, etc. within the Active Directory structure. A single Active Director y policy can consist of a computer policy and a user policy. A computer policy consists of settings that affect the physical computer and impact all users logging onto the computer while a user policy affects the user and is applied on all system s the user logs on to. Local server policies and custom policies are type s of Active Director y policies and are described as:
Local Server Policies and Settings: Local Server policies are similar to Active Directory policies, except they are managed on a server-by-server basis and configured locally on that specific server, where Active Directory policies are managed centrally and can impact hundreds or thousands of users or computers with a single application of a policy.
Custom Active Directory Policy Templates: Custom ADM templates, like the Citrix icaclient.adm template, are Active Directory or Local Server policies used to make configuration settings. They can be custom registry settings or simply standard policies re-organized as two examples. The concept of custom templates is supported, but depending on the author of the custom template, supportability by either Citrix or Microsoft might not be available. Organizations will have to verify the supportability of custom ADM templates. Also, any custom template used might already have settings configured, potentially causing issues with the environment. It is highly recommended to test custom policies in a test environment before implementing in production.
The following five areas are the basis f or the design decisions for an enterprise deployment of Presentation Server. These types of policies will be impacted by the following design areas: