MEDIA BACKGROUNDER

VMware View 4.5 Advances Enterprise End-User Computing Model Overview: Announced Aug. 31, 2010 at the VMworld 2010 conference in San Francisco, VMware View 4.5 is a complete, virtual desktop solution that enables enterprises to improve security, lower operating costs, and simplify desktop administration and management by establishing a modern, end-user computing architecture. By breaking the bonds between the physical desktop and the associated OS, applications and end-user profiles, VMware View creates a rapidly deployable private desktop cloud. The result is a more flexible computing model that provides IT with greater control and end users with access to their desktop from any device. Built on VMware vSphere, the industrys most widely deployed virtualization platform, VMware View 4.5 takes advantage of a unique Cloud Computing architecture to deliver unsurpassed quality of service for desktop users. Centralized, automated desktop management provided by VMware View 4.5 enables the scalable management of tens of thousands of desktops through a single console and is proven to reduce operational costs by as much as 50 percent while increasing security and compliance levels far beyond levels of traditional PCs. VMware View 4.5 Features and Benefits: VMware View 4.5 delivers new innovations, expanding the value of desktop virtualization to the enterprise: Rapid, Cost-Effective Windows 7 Migration VMware View 4.5 fully supports Microsoft Windows 7 while providing a model for enterprises to significantly reduce the cost and time required migrating from legacy operating systems. Customers who combine VMware View 4.5 with VMware ThinApp for application virtualization can realize even more benefits, reducing the time and cost of Windows 7 migration by 50 percent. Customers can calculate their expected savings by visiting VMwares ROI calculator. Offline Desktop Access VMware View Client with Local Mode, the industrys first integrated offline virtual desktop solution, enables users to access their virtual desktops even while disconnected from the network. In addition to offline requirements, VMware View Client with Local Mode delivers solutions to enable use cases such as Bring Your Own PC (BYOPC) and contractor owned IT. Innovative management provides enforcement of consistent security and compliance policies across connected and disconnected virtual desktops. Expanded Administrative Capabilities At the core, VMware View Administrator has been enhanced from the ground up to deliver new levels of scalability and efficiencies for IT organizations. With the addition of role-based administration, monitoring dashboards, simplified reporting and support for third-party tools VMware View Administrator continues to drive simplification of virtual desktop management through a single administrative interface. Integrated Application Assignment VMware View 4.5 simplifies the delivery of virtualized applications to end-users through integration of application assignment with the VMware View Administrator console. Integration enables VMware ThinApp applications to be centrally managed and easily delivered to pools or individual desktops. Improved User Experience With enhancements to optimize delivery of virtual desktops to endusers on the LAN and across the WAN, VMware View 4.5 continues to improve the end-user experience and to address new use cases. Enhancements to the PCoIP protocol in the VMware
View 4.5 release include expanded support for authentication mechanisms, improvements to zero client capabilities and optimized interaction for end-users over wide area links. Reduced Solution Cost With the introduction of tiered storage, VMware View 4.5 helps reduce the cost of storage by enabling customers to take advantage of multiple storage tiers, including high performance and locally attached storage. This helps to not only optimize performance but also allows organizations to reduce the cost associated with storage requirements for virtual desktop environments. In addition VMware has worked with partners such as Dell, HP, Cisco, NetApp and EMC to provide prescriptive reference architectures, which enable customers to deploy a desktop virtualization solution that is both scalable and cost effective. Finally, through integration with vSphere 4.1, a key component of the VMware View solution, customers benefit from increased desktop VM consolidation to improve server utilization and further optimize solution costs. Enhanced Security Features Improved security management and security card support in VMware View 4.5 enables secure access to virtualized desktops while protecting sensitive data. Enterprises can now deliver a secure, consistent desktop environment for remote and branch offices, mobile workers, and outsourced and contract business models. VMware View 4.5 also supports the FIPS 140-2 U.S. Federal Government Security Compliance, enabling protection of sensitive and secure data for U.S. Federal Government agencies. Flexible Device End-Points View delivers a personalized, uncompromising desktop experience across nearly any end-user device, including Microsoft Windows and Mac devices, Zero Clients, Thin Clients, Kiosks and new computing platforms such as the Apple iPhone and iPad as well as Android devices. This capability enables new flexible desktop models, supporting contractors and employees leveraging their own endpoint devices. It provides enterprises and users increased flexibility to choose from new device types while ensuring each system remains managed, secure and compliant. To see a complete list of VMware View Ready clients, visit http://www.vmware.com/resources/compatibility/view Optimized Anti-Virus Protection Integration of VMware vShield Endpoint enables the centralization of anti-virus and malware scanning to optimize virtual environment performance, simplify AV management and improve desktop security.

Pricing & Availability: Available in the coming weeks, VMware View 4.5 is a family of products: VMware View 4.5, Enterprise Edition: includes VMware vSphere 4.1 for desktops, VMware vCenter 4.1 and VMware View Manager 4.5, a flexible desktop management server enabling IT administrators to quickly provision and tightly control user access. VMware View 4.5, Premier Edition: includes VMware vSphere 4.1 for desktops, VMware vCenter 4.1, VMware View Manager 4.5, View Client with Local Mode, VMware ThinApp 4.6, VMware View Composer and VMware vShield Endpoint 1.0 to enable integration of offline capabilities, image management optimization, application virtualization and centralized anti-virus protection with virtual desktop delivery and management.
VMware View 4.5 Enterprise Edition is priced at $150 per concurrent connection and VMware View 4.5 Premier Edition is priced at $250 per concurrent connection. For more information, go to https://www.vmware.com/products/view/.
VMware Professional Services: VMware Professional Services offers on-site, end-to-end consulting services to help customers who are interested in beginning the journey to a more modern, user-centric application and data delivery model. For organizations looking to get started with VMware View 4.5, the company offers three core assessment services -- a Desktop Infrastructure Virtualization Assessment to identify both the users and desktops that are the best candidates to move into a virtual desktop environment; an Application Virtualization Assessment to identify which applications are the prime targets for virtualization and a Desktop Virtualization Strategy Assessment, which combines both the Infrastructure and Application Assessment with a Strategic Workshop to help organizations prepare and proactively manage for the successful adoption of this technology. For more information, visit VMware.com. Enterprises today are facing an ongoing desktop dilemma between the needs of IT (control) and end users (freedom), said Raj Mallempati, director of product marketing, End-User Computing, VMware. VMware View 4.5 is the only end-to-end solution that establishes a modern end-user computing model, enabling a personalized user experience and flexible access to data and information across any device. This provides the scalable management, rich user experience, and common virtualization platform you need to energize your business by delivering desktops in an IT-as-a-Service model. Industry and Customer Support: AMD With VMware View 4.5, VMware has enabled a truly robust virtual desktop experience. AMD has a long history of collaboration with VMware in virtualization and cloud computing. We are excited to see the culmination of VMware View 4.5, a next-generation managed desktop virtualization solution ideally suited to take advantage of systems powered by the AMD Opteron 6000 and 4000 Series platforms to enable a secure, flexible user experience. Margaret Lewis, director, Software Solutions Marketing, AMD Cisco "In support of VMware View 4.5 and the PCoIP display protocol, Cisco offers integrated unified fabric switching and unified computing solutions that provide an ideal infrastructure for virtual desktop environments by delivering higher virtual machine density and performance and improved security. Soni Jiandani, vice president of marketing, Server Access and Virtualization Technology Group, Cisco Dell As a core component of the Dell Virtual Remote Desktop (VRD) solution, the latest release of VMware View 4.5 furthers customers ability to standardize, simplify and automate desktop IT. Our unique partnership provides customers with complete virtualization solutions from the datacenter to the desktop via a managed service or private cloud customer-hosted implementation. Steve Lalla, vice president and general manager, Commercial Client Product Group, Dell EMC The two things VMware View 4.5 is focused on achieving is providing a better user experience and lowering the cost of desktop virtualization. EMC is extending the value of VMware View through technology features such as FAST Cache and compression that control costs and enhance performance and the integration of EMCs deduplication software and security products to provide a more recoverable and more secure environment. To help remove the risk of deploying a virtual desktop strategy EMC has developed a comprehensive portfolio of service offerings and has jointly developed reference architectures and whitepapers that bring the total cost of storage to $38 per client. Chad Sakac, vice president, VMware Technology Alliance, EMC Corporation

F5 "With the newest version of VMware View 4.5, F5 offers support for the PCoIP display protocol through the BIG-IP Edge Gateway to enable secure access, single-sign-on and high performance, providing joint customers with a robust security and scalability offering. The collaboration between VMware and F5 improves the end user experience over the WAN, maximizes the value gained from desktop virtualization initiatives, reduces costs and improves flexibility." Erik Giesa, vice president of product management and marketing, F5 Fujitsu "Fujitsu welcomes the release of VMware View 4.5. Leveraging the strong relationship with VMware, we have been providing virtualization solutions to our customers on our PRIMERGY industry-standard servers. With improved customer benefits in PC client management, including cost reductions, security improvements, and Windows 7 support as desktop virtualization OS, we have the ability to provide a complete and effective managed infrastructure in conjunction with our PRIMERGY server line, ETERNUS storage systems, Systemwalker Desktop series and PCs." Yoichi Hori, president, Platform Software Business Unit, Fujitsu Limited HP Clients need a more reliable, secure and manageable client infrastructure to achieve lower, more predictable costs and desktop virtualization delivers this. HPs thin client solutions and reference architectures provide a simple way to adopt desktop virtualization based on VMware View 4.5. Paul Miller, vice president, Solutions and Strategic Alliances, Enterprise Servers, Storage and Networking, HP Imprivata "VMware View 4.5 is great news for technology users, particularly in the healthcare industry where there is a heavy reliance on roaming sessions and shared workstations. Imprivata OneSign's architecture is ideally-suited for tight integration with VMware View, taking full advantage of its features. The result is a comprehensive solution for simplifying and securing access to patient data, enabling true one-touch, location-aware 'follow-me' clinical desktops." Geoff Hogan, senior vice president, Business Development and Product Management, Imprivata, Inc. Samsung Samsung is excited about the launch of VMware View 4.5. End users will greatly benefit from both the new features of VMware View 4.5 and our all-in-one monitor solutions. Samsungs integrated thin client monitors provide excellent performance and value for desktop virtualization customers. JinHwan Kim, vice president, Visual Display Division, Samsung Teradici Teradici continues to work closely with VMware to enable full interoperability of the PCoIP display protocol in both hardware and software implementations to enhance and extend the capabilities of the VMware virtual desktop platform in VMware View 4.5. Our close collaboration with VMware has enabled broad adoption of desktop virtualization by providing an optimal desktop experience for a wide range of users. Dan Cordingley, president and CEO, Teradici Corporation ThinPrint "We are pleased to continue our successful partnership with VMware, said. With VMware View 4.5 and Location Based Printing, VMware has made an important step forward in simplifying and optimizing printer driver administration." Charlotte Knzell, board of directors member, ThinPrint

VCE Coalition To lower IT cost and complexity, CIOs and IT managers are turning to integrated infrastructures. Our Vblock customers appreciate the ability to scale virtual desktop deployments in a pre-configured, predictable manner that removes the guesswork out of architecting virtual desktop environments. VMware View 4.5, which improves end user productivity by reducing desktop downtime, brings another layer of value to Vblock customers. Todd Pavone, senior vice president, VCE Solutions Wyse The ability to manage thousands of end users via a single solution is one of the key benefits of desktop virtualization, and the combination of VMware View with Wyse cloud client computing solutions enables our customers to save significant costs and energy savings, all without sacrificing end user performance. The complexity of managing countless PCs through time-consuming and expensive means is soon to become a thing of the past. Curt Schwebke, chief technology officer, Wyse Technology Additional Resources: Learn more about VMware View Read VMware CTO Scott Davis blog on VMware View 4.5 Read VMware View teams blog on VMware View 4.5 Read VMware Reference Architecture Brief for Stateless Virtual Desktops with VMware View 4.5 Watch a video introducing VMware View 4.5 Get product information, datasheets and screenshots
### Contacts: Christian Bateman VMware Global Communications cbateman@vmware.com (650) 427-1103 Hana Mandapat OutCast Communications for VMware Hana@outcastpr.com (415) 345-4702

View 3 or View 4 Components Connection Server 4.0.x or 3.1.x N/A Yes Yes No No Yes Limitations View Agent 4.0.x or 3.1.x Yes N/A Yes No No Yes No View Client 4.0.x or 3.1.x Yes Yes N/A N/A No N/A N/A Thin Client 4.0.x or 3.1.x Yes Yes N/A N/A No N/A N/A View Composer 1.0 or 2.0 Limitations Yes Yes No No Yes N/A
View 4.5 Connection Server 4.5 View Agent 4.5 View Client (Windows) 4.5 View Client (Mac) 4.5 View Client with Local Mode 4.5 Thin Client 4.5 View Composer 2.5
Until both View Connection Server and View Composer are upgraded, View Composer operations do not work. If you have View Connection Server 4.5 and View Composer 1.0 or 2.0, users can connect to their desktops, but no new linked-clone desktops can be created, and recompose, rebalance, and refresh operations do not work. Also, you cannot edit settings for linked-clone pools. IMPORTANT As the table shows, View Agent 3.1.x and 4.0.x are not compatible with View Composer 2.5. This limitation means that you must not use a View 4.0.x or 3.1.x master image, or snapshot, when creating, recomposing, or refreshing a pool that uses features specific to View 4.5. These View 4.5 features include using a system-disposable disk (SDD), using a Sysprep customization specification, and attaching a previously archived user-data disk (UDD) to an existing desktop. Although View Composer 2.5 can work with View Connection Server 4.0.x or 3.1.x in a limited fashion, this setup is available only for cases where upgrading all View Connection Server instances during the same maintenance window is not feasible. Specifically, new View Composer 2.5 features, such as the ability to use SysPrep customization, are not available until you update to View Agent 4.5. Because View Client with Local Mode is a View 4.5 feature, and its predecessor, Offline Desktop, was an experimental feature, View Client with Local Mode is not backward compatible with View 4.0.x and 3.1.x components. NOTE The instructions in this document are also applicable to patch releases of VMware View 4.5 and to upgrading from the release candidate (RC) version of View 4.5 to the general availability (GA) version.
VMware View Upgrade Overview
Upgrading an enterprise VMware View deployment involves several high-level tasks. Upgrading is a multistage process in which procedures must be performed in a particular order. You must complete the upgrade process in a specific order. If you do not complete each upgrade stage before moving on, you can lose data and server access. Order is also important within each upgrade stage. How many of the following tasks you need to complete depends on which components of VMware View you use in your deployment. Because VMware View 4.5 includes components that were not available in earlier releases, some of the tasks are installation rather than upgrade tasks. 1 On the physical or virtual machines that host View Connection Server instances, make backups and record various configuration and system settings. See Preparing View Connection Server for an Upgrade, on page 17. On the physical or virtual machines that host View Composer and vCenter Server, make backups and temporarily halt certain scheduled tasks. See Preparing vCenter Server and View Composer for an Upgrade, on page 18. If some of your end users are using View 3.1.x or 4.0.x Client with Offline Desktop, ask them to check in their View desktops. Upgrade View Connection Server on the existing host or migrate to a new machine. See Upgrade View Connection Servers in a Replicated Group, on page 21. Install and configure an event database that View Administrator 4.5 uses for displaying some of the View Connection Server events that were previously recorded only in logs. See the VMware View 4.5 Installation Guide. For the View Client with Local Mode component, install and configure one or more View Transfer Server instances. This server transfers data that end users need to check out and run View desktops locally on their client systems. See the VMware View 4.5 Installation Guide. View Client with Local Mode is the fully supported feature that in earlier releases was an experimental feature called View Offline Desktop. 7 Upgrade View Composer on the existing host or, if you are also upgrading to vSphere 4.1, migrate to a new machine. See Upgrade to View Composer 2.5 and vCenter Server 4.1 on a Different Machine, on page 30. Upgrade the VMware View software that runs on the physical or virtual machines that are used as desktop sources, as full-clone desktops in a pool, and as individual desktops in a manual pool. See Upgrade View Agent, on page 38.

n n n n

Internet Explorer 7 Internet Explorer 8 Firefox 3.0 Firefox 3.5
To use View Administrator with your Web browser, you must install Adobe Flash Player 10. To display text properly, View Administrator requires Microsoft-specific fonts. If your Web browser runs on a non-Windows operating system such as Linux, UNIX, or Mac OS, make sure that Microsoft-specific fonts are installed on your computer. Currently, the Microsoft Web site does not distribute Microsoft fonts, but you can download them from independent Web sites.
Supported Operating Systems for View Client and View Client with Local Mode
Users run View Client to connect to their View desktops. You must install View Client or View Client with Local Mode on a supported operating system. Table 3-6 lists the operating systems supported for View Client. Table 3-6. View Client Operating System Support
Operating System Windows 7 Windows XP Version 32-bit and 64-bit 32-bit Edition Home, Enterprise, Professional, and Ultimate Home and Professional Service Pack N/A SP3
Table 3-6. View Client Operating System Support (Continued)
Operating System Windows Vista Mac OS X Leopard 10.5 Mac OS X Snow Leopard 10.6 Version 32-bit N/A N/A Edition Home, Business, Enterprise, and Ultimate N/A N/A Service Pack SP1 and SP2 N/A N/A
IMPORTANT View Client with Local Mode is supported only on Windows systems and only on physical computers. In addition, to use this feature, your VMware license must include View Client with Local Mode. View Client with Local Mode is the fully supported feature that in earlier releases was an experimental feature called View Offline Desktop. Table 3-7 lists the versions of VMware Infrastructure or vSphere for View Client with Local Mode. Table 3-7. vSphere Requirements for View Client with Local Mode
Version VMware Infrastructure 3.5/Virtual Center 2.5 vSphere 4.0 vSphere 4.1 Update Level VI 3.5 Update 5 with VC 2.5 Update 6 Update 2 N/A
A Windows 7 or Windows Vista View desktop that is created on an ESX 3.5 host cannot produce 3D and Windows Aero effects. This limitation applies even when the desktop is checked out for local use on a Windows 7 or Windows Vista host. Windows Aero and 3D effects are available only if the View desktop is created using vSphere 4.x. When you check out a View desktop to run on your local computer, the hardware on client host must support both the local system and the virtual machine that now runs on it. For hardware requirements, see the chapter about system requirements for client components, in the VMware View Installation Guide. NOTE Several VMware partners offer thin client devices for VMware View deployments. The features and Linux operating systems that are available for each thin client device are determined by the vendor and model and the configuration that an enterprise chooses to use. For information about the vendors and models for thin client devices, see the Thin Client Compatibility Guide, available on the VMware Web site.

Determine if your company has written any batch files or scripts that run against the View database on the View Connection Server instance, and if so, document their names and locations. If you use load balancers for View Connection Server, document the configuration settings for the load balancers.
Preparing vCenter Server and View Composer for an Upgrade
Because vCenter Server and View Composer are installed on the same virtual or physical machine, some preparation tasks apply to both.
Preparing for Upgrades That Include vSphere
If you are upgrading to vCenter Server 4.1 in addition to upgrading to VMware View 4.5 with View Composer 2.5, you must consult the vSphere Upgrade Guide and perform the following tasks in the following order: 1 Verify that the virtual or physical machine meets the system requirements for vCenter Server 4.1. For example, vCenter Server 4.1 requires two CPUs and must run on a 64-bit operating system. Because View Composer 1.0 and 2.0.x were supported only on 32-bit operating systems, upgrading to vSphere 4.1 means that you must upgrade View Composer to a different machine. 2 If vCenter Server is installed in a virtual machine, take a snapshot of the virtual machine. For instructions on taking snapshots, see the vSphere Client online help. 3 If the computer name is longer than 15 characters, shorten the name to 15 or fewer characters. You use this name first on the 32-bit VirtualCenter Server 2.5 host or the vCenter Server 4.0 host, and then you use this name when you migrate to the 64-bit vCenter Server 4.1 host. You also use the same IP address. 4 Back up the VirtualCenter or vCenter Server database and the View Composer database. For instructions on performing a database backup, see the documentation from your database vendor. 5 Verify that the database server is compatible with vCenter Server 4.1. For example, if the database server is Oracle 9i, you must upgrade to Oracle 10g or 11g. If you plan to migrate vCenter Server from a 32-bit operating system to a 64-bit operating system and the database will be on the same system, verify that the database is supported on 64-bit operating systems. 6 Verify that the database is compatible with View Composer 2.5. View Composer supports a subset of the database servers that vCenter Server supports. If you are already using vCenter Server with a database server that is not supported by View Composer, continue to use that database server for vCenter Server and install a separate database server to use for View Composer and View Manager database events. 7 Make a copy of the folder that contains SSL certificates. This folder is located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter. Document the IP address and system name of the machine on which vCenter Server is installed. For all linked-clone desktop pools, disable provisioning of new virtual machines. Because View Composer might be upgraded during a different maintenance window than its desktop pools, provisioning must be postponed until both components are upgraded.

Chapter 4 Preparing for a VMware View Upgrade
If any desktop pools are set to refresh the OS disk on logoff, edit the Desktop/Pools settings for that pool and set Refresh OS disk on logoff to Never. This setting prevents an error from occurring when the newly upgraded View Composer attempts to refresh a desktop that has not yet been upgraded to View Agent 4.5.
If any desktop pools are scheduled to do a refresh or recompose operation, cancel these tasks.
Preparing for Upgrades of View Composer Only
If you are upgrading only View Composer and are not upgrading VirtualCenter Server, you must perform the following tasks: 1 If View Composer is installed in a virtual machine, take a snapshot of the virtual machine. For instructions on taking snapshots, see the vSphere Client online help. 2 Back up the VirtualCenter or vCenter Server database and the View Composer database. For instructions on performing a database backup, see the documentation from your database vendor. 3 Verify that the database is compatible with View Composer 2.5. View Composer supports a subset of the database servers that vCenter Server supports. If you are already using vCenter Server with a database server that is not supported by View Composer, continue to use that database server for vCenter Server and install a separate database server to use for View Composer and View Manager database events. 4 Make a copy of the folder that contains SSL certificates. This folder is located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter. Document the IP address and system name of the machine on which vCenter Server is installed. For all linked-clone desktop pools, disable provisioning of new virtual machines. Because View Composer might be upgraded during a different maintenance window than its desktop pools, provisioning must be postponed until both components are upgraded. 7 If any desktop pools are set to refresh the OS disk on logoff, edit the Desktop/Pools settings for that pool and set Refresh OS disk on logoff to Never. This setting prevents an error from occurring when the newly upgraded View Composer attempts to refresh a desktop that has not yet been upgraded to View Agent 4.5. 8 If any desktop pools are scheduled to do a refresh or recompose operation, cancel these tasks.
Upgrading VMware View Components
The VMware View components that you must upgrade include View Connection Server, View Client, and View Agent. Depending on the optional components you use, you might also need to upgrade View Composer, vCenter Server, ESX hosts, and the virtual machines on ESX hosts. If you plan to use View Client with Local Mode, you must also install a View Transfer Server instance. Depending on how large your View deployment is, you might perform the upgrade process incrementally, over several maintenance windows. For VMware View 4.5 patch releases, use the sections of this document that are specific to View Manager, View Composer, View Agent, and View Client. This chapter includes the following topics:

You do not need to make any changes to the configuration of existing load balancers. Procedure 1 Stop the service called VMware View Connection Server service on all View Connection Server instances in the group. View LDAP database corruption can occur if you upgrade a View Connection Server instance while other instances in the same group are running. Do not stop the VMwareVDMDS service. The VMwareVDMDS service must be running so that the View LDAP database can be upgraded. 2 On the host of the View Connection Server instance that is the standard, or first, server instance in the group, run the installer for the VMware View 4.5 Connection Server. The installer determines that an older version is already installed and performs an upgrade. The installer displays fewer installation options than during a fresh installation. The View LDAP is also upgraded. 9 Verify that the VMware View Connection Server service restarts after the installer wizard closes. Verify that you can log in to View Connection Server, and click About in View Administrator to verify that the new version is being used. Go to View Configuration > Product Licensing and Usage, click Edit License, enter the View Manager license key, and click OK. Verify that you can log in to a View desktop. Stop the View Connection Server service again. Repeat Step 1 through Step 7 to upgrade each View Connection Server instance in the group. After all servers in the group are upgraded, start the View Connection Server service on all of them.
Chapter 5 Upgrading VMware View Components
Use the vdmexport.exe utility to back up the newly upgraded View LDAP database. If you have multiple instances of View Connection Server in a replicated group, you need only export the data from one instance.
On one of the upgraded View Connection Server instances, copy the GPO templates and load them into Active Directory. Repeat Step 1 through Step 7 to upgrade each security server. VMware View 4.5 includes a security server pairing mechanism. Upgrades of View 4.5 security servers from View 4.5 RC to GA are not supported. If you have a View 4.5 RC security server, you must uninstall the security server and install the GA version.
If you use security servers, in View Administrator, go to View Configuration > Servers and remove any duplicate security servers from the list. The new automated security server pairing mechanism can produce duplicate entries in the Security Servers list if the full system name does not match the name that was assigned when the security server was originally created.

Run SviConfig to Manually Upgrade the Database
With the SviConfig command-line utility, you can upgrade the View Composer database separately from the View Composer software. This utility also creates a log file to simplify troubleshooting if the upgrade fails. IMPORTANT Only experienced View Composer administrators should use the SviConfig utility. This utility is intended to resolve issues relating to the View Composer service. Prerequisites Back up the View Composer database. For instructions, see the documentation for your database server. Procedure 1 On the vCenter Server virtual or physical machine, open a Windows command prompt and navigate to the SviConfig executable file. The file is located with the View Composer application.
Option 32-bit Windows 64-bit Windows Action Navigate to C:\Program Files\VMware\VMware View Composer \sviconfig.exe. Navigate to C:\Program Files (86)\VMware\VMware View Composer \sviconfig.exe.
Enter the command to stop the VMware View Composer service.

net stop svid

Run the SviConfig databaseupgrade command.
sviconfig -operation=databaseupgrade -DsnName=<target database source name (DSN)> -Username=<database administrator username> -Password=<database administrator password>

For example:

sviconfig -operation=databaseupgrade -dsnname=LinkedClone -username=Admin -password=Pass
A successful operation displays output that shows the upgrade steps.
Establishing database connection. Database connection established successfully. Upgrading database. Load data from SVI_VC_CONFIG_ENTRY table. Update SVI_DEPLOYMENT_GROUP table. Update SVI_REPLICA table. Update SVI_SIM_CLONE table. SviConfig finished successfully. Database is upgraded successfully.
Enter the command to start the VMware View Composer service.

net start svid

A complete log of the upgrade process is created.
Option Windows Server 2003 Windows Server 2008 Description C:\Documents and Settings\All Users\Application Data\VMware \View Composer\Logs\vmware-sviconfig.log C:\Users\All Users\VMware\View Composer\vmware-sviconfig.log
What to do next If the database upgrade fails, see Troubleshooting a View Composer Database Upgrade Failure, on page 29. If the result code is any number other than 0, which means success, see Result Codes for a Manual Database Schema Update, on page 28.
Result Codes for a Manual Database Schema Update
When you manually upgrade the View Composer database, the sviconfig databaseupgrade command displays a result code. Table 5-1 shows the sviconfig databaseupgrade result codes. Table 5-1. Result Codes for the databaseupgrade Command

Code 4 Description The operation ended successfully. The supplied DSN could not be found. Invalid database administrator credentials were provided. The driver for the database is not supported. An unexpected problem arose and the command failed to complete.
Table 5-1. Result Codes for the databaseupgrade Command (Continued)
Code Description Another application is using the View Composer service. Shut down the service before executing the command. A problem arose during the restore process. Details are provided in the onscreen log output. Unable to upgrade the database data. Unable to connect to the database server.
Troubleshooting a View Composer Database Upgrade Failure
When you upgrade the View Composer service with the View Composer installer or run the SviConfig databaseupgrade command, the operation might fail to upgrade the View Composer database. Problem The SviConfig databaseupgrade operation displays error code 17, or the View Composer installer displays a warning message.
Database upgrade completed with warnings
Cause The database-upgrade software contacts vCenter Server to get additional data about desktops. The database upgrade might fail if the desktops are not available, the ESX host is not running, or vCenter Server is not available. Solution 1 See the View Composer SviConfig log file for more information.
Option Windows Server 2003 Windows Server 2008 Action Navigate to C:\Documents and Settings\All Users\Application Data\VMware\View Composer\Logs\vmware-sviconfig.log. Navigate to C:\Users\All Users\VMware\View Composer\vmwaresviconfig.log.
The upgrade script logs a message for each failure. 2 Examine the log records to identify the desktops that failed to upgrade.
Option The desktop exists but is unavailable. The desktop does not exist. Action Make the desktop available again. Depending on the cause of the failure, you might have to restart the ESX host or vCenter Server, or take another action. Ignore the log message. NOTE A deleted desktop might appear to exist in View Manager if an administrator deletes the desktop virtual machine directly in vSphere.

What to do next If you used the vSphere 4.1 data migration tool, complete the tasks for backing up and restoring the vCenter Server database and creating a 64-bit data source name (DSN), as described in the chapter about upgrading to vCenter Server on a different machine and upgrading the existing database, in the vSphere 4.1 Upgrade Guide. Perform the procedure described in Migrate View Composer to the New Machine, on page 33.
Use the Data Migration Tool to Migrate to the New Machine
After you prepare the source machine for migration, you can use the vCenter Server data migration tool simplify moving vCenter Server to the destination machine. his procedure provides an overview of the tasks you must perform if you are using the vCenter Server data migration tool. To complete some of these tasks, you must have the step-by-step instructions found in the vSphere 4.1 Upgrade Guide and the VMware View Installation Guide. Prerequisites
Complete the required tasks on the source machine. See Prepare the Source Machine for View Composer Migration, on page 30. Verify that the Microsoft.NET Framework and the ASP.NET IIS registration tool are installed on the source and destination computers. See the topic in the VMware View Administrator's Guide about preparing a Microsoft.NET Framework for migrating RSA keys. Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the installer and perform the upgrade. Verify that you have the correct license keys for vSphere if you are upgrading Virtual Infrastructure components to vSphere.
Procedure Set the host name and IP address to the name and IP address originally used on the source machine. Migrate the RSA key container used by View Composer. a On the destination machine, open a command prompt and change directories to the directory where the aspnet_regiis program is located.
You might have several copies of the aspnet_regiis program on the computer. Use the one in the v2.0.xxxxx directory. b Use the aspnet_regiis command to import the RSA key pair.

aspnet_regiis -pi SviKeyContainer path\keys.xml
In this command, path\keys.xml is the complete path to the keys.xmlfile. The tool imports the key pair data into the local key container. 3 Perform the task described in the section about restoring the vCenter Server configuration and installing vCenter Server on the new machine, in the vSphere 4.1 Upgrade Guide. The data migration tool migrates the bundled SQL Server 2005 Express database server, if you use one, and creates a 64-bit DSN for it. If you use a different database, this procedure provides instructions for upgrading it. This procedure also copies the SSL certificate folder to the new machine. The data migration tool does not restore the View Composer database or create a DSN for it. 4 If you use a local database server, use your vendor's database tools to restore or attach the vCenter Server database and the View Composer database.
Create a 64-bit domain server name (DSN) for vCenter Server and a 64-bit DSN for View Composer. For instructions, see the vSphere 4.1 Upgrade Guide and the VMware View Installation Guide.
Download and run the installer for View Composer 2.5, which is the version included with VMware View 4.5. You can download the installer from the VMware Web site.
Verify that the View Composer service starts after the installer wizard finishes.
View Composer and vCenter Server instances are upgraded and are backward-compatible with existing View 3.1.3 or 4.0.1 View Clients and with desktop sources that have the View 4.0.1 or 4.1 Agent installed. What to do next Create a test desktop pool and verify that virtual desktops from the test pool work as expected. If you upgraded vCenter Server, perform the post-upgrade tasks described in the vSphere 4.1 Upgrade Guide. At your next maintenance window, continue with the VMware View upgrade. See Upgrade ESX Hosts and Virtual Machines, on page 35.
Migrate View Composer to the New Machine
After you prepare the source machine for migration, you must perform certain tasks on the destination machine. If you do not use the vCenter Server data migration tool, you can perform the required tasks manually. Some of the steps in this procedure would be performed automatically if you use the vCenter Server data migration tool. You might choose not to use the tool if you want to perform the upgrade incrementally so that you can verify at every step that the upgrade is successful. To use the data migration tool instead of performing this procedure, see Use the Data Migration Tool to Migrate to the New Machine, on page 32. Prerequisites

Complete the required tasks on the source machine. See Prepare the Source Machine for View Composer Migration, on page 30. Verify that the Microsoft.NET Framework and the ASP.NET IIS registration tool are installed on the source and destination computers. See the topic in the VMware View Administrator's Guide about preparing a Microsoft.NET Framework for migrating RSA keys. Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the installer and perform the upgrade. Verify that you have the correct license keys for vSphere if you are upgrading Virtual Infrastructure components to vSphere. Print or have available the vSphere 4.0 Upgrade Guide and the vSphere 4.1 Upgrade Guide.
In this command, path\keys.xml is the complete path to the keys.xmlfile. The tool imports the key pair data into the local key container. 3 Copy the SSL certificate folder to the destination machine.
Option Windows 2003 Server Windows 2008 Server Action Copy the folder to %ALLUSERSPROFILE%\Application Data\VMware \VMware VirtualCenter. Copy the folder to %ALLUSERSPROFILE%\VMware\VMware VirtualCenter.
If you use a local database server, use your vendor's database tools to restore or attach the vCenter Server database and the View Composer database. Create a 32-bit DSN for the vCenter Server 4.0 database. For more information, see the topic about creating a 32-bit DSN on a 64-bit operating system in the vSphere 4.0 Upgrade Guide. You need this 32-bit DSN if you install vCenter Server 4.0 rather than 4.1 on the destination machine. The data migration tool installs vCenter Server 4.1 on the destination machine.
Install vCenter Server 4.0 Update 2. For instructions, see the vSphere 4.0 Upgrade Guide. In the installer wizard, you will select the 32-bit DNS that you created earlier.
Create a test desktop pool and verify that virtual desktops from the test pool work as expected. Upgrade vCenter Server 4.0 to 4.1, as described in the chapter about upgrading to vCenter Server 4.1, in the vSphere 4.1 Upgrade Guide. Restart the View Composer service.
View Composer and vCenter Server instances are upgraded and are backward-compatible with existing View 3.1.3 or 4.0.1 View Clients and with desktop sources that have the View 4.0.1 or 4.1 Agent installed.
What to do next If you upgraded vCenter Server, perform the post-upgrade tasks described in the vSphere 4.1 Upgrade Guide. At your next maintenance window, continue with the VMware View upgrade. See Upgrade ESX Hosts and Virtual Machines, on page 35.
Upgrade ESX Hosts and Virtual Machines

Upgrading ESX hosts and virtual machines to vSphere is the most time-consuming aspect of this middle phase of a VMware View upgrade. Upgrading from ESX 3.5 involves more steps than upgrading from ESX 4.x because the upgrade includes upgrading the virtual hardware version of the virtual machines.
Upgrade ESX 3.5 Hosts and Their Virtual Machines
Upgrading ESX 3.5 hosts and virtual machines involves upgrading the host, the virtual machine virtual hardware version, and the version of VMware Tools on the virtual machines. If you use View Composer, the upgrade includes turning on vSphere mode. This procedure provides an overview of the tasks you must perform during the second and subsequent maintenance windows. To complete some of these tasks, you might need step-by-step instructions found in the vSphere Upgrade Guide and the VMware View Administrator's Guide. Prerequisites
Complete the procedure described in Upgrade View Connection Servers in a Replicated Group, on page 21. Perform the ESX preparation tasks listed in the vSphere Upgrade Guide. Verify that you have the correct license key for vSphere if you are upgrading Virtual Infrastructure components to vSphere. Verify that all ESX hosts are members of a cluster. If you want to upgrade a standalone ESX host, place it in a single-host cluster. If the ESX host is not part of a cluster, you might not be able to enable vSphere mode for View Composer.
Procedure 1 Upgrade ESX hosts to vSphere 4.1, cluster by cluster. For instructions, see the vSphere Upgrade Guide. If you have many clusters, this step could take several maintenance windows to complete. Upgrading ESX hosts includes the following tasks: a b c d e Use VMotion to move the virtual machines off of the ESX host. Put the ESX host into maintenance mode. Perform the ESX upgrade. Use VMotion to move the virtual machines back onto the ESX host. Perform post-upgrade tasks for ESX hosts.
Every ESX host must be a member of a cluster, as mentioned in the prerequisites. If an upgraded ESX host does not reconnect itself to vCenter, use vSphere Client to reconnect the ESX host to the vCenter Server. If you use View Composer, after all ESX hosts are upgraded, on the vCenter Server host, restart the View Composer service.
If you use View Composer, turn on vSphere mode. vSphere uses a new API to achieve performance improvements. a b Verify that all ESX hosts in a cluster are running vSphere 4.1. Log in to View Connection Server and turn on the desktop pool setting called Use vSphere mode for View Composer. For instructions, see the VMware View Administrator's Guide. c On a parent virtual machine upgrade View Agent to 4.5, create a test desktop pool, and verify that vSphere mode is used. This new test desktop pool uses the new View Composer API and as a result, does not create a source linked clone from the replica. If you use vCenter Server to watch the virtual machines being created, you see that a replica is created from the parent, but not a source-lc virtual machine.

Upgrade View Agent

The strategy for upgrading View Agent depends on the type of desktop source. This procedure provides an overview of the tasks you must perform to upgrade View Agent in a variety of virtual machines used as desktop sources. To complete some of these tasks, you might need the step-by-step instructions found in the vSphere Client online help or in the VMware View Administrator's Guide, available by clicking the Help button in View Administrator. IMPORTANT If you are upgrading View Agent from a version earlier than 4.5 and if you have used a group policy object (GPO) to disable Windows firewall, the installer returns one of the following errors and the upgrade is rolled back:
n n n Error 28014. Unable to close the firewall. Warning 28013 Unable to open the firewall. Internal Error 28051 Shared Access.
If you encounter error 28014 or warning 28013, you must use a GPO to enable firewall services and run the installer again to upgrade the agent. If you encounter internal error 28051, click OK in the error message box to continue the upgrade. Prerequisites Perform the following preparation tasks:
If you are upgrading ESX hosts and virtual machines, complete the procedure described in Upgrade ESX Hosts and Virtual Machines, on page 35. Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the installer and perform the upgrade.
Procedure 1 On parent virtual machines and virtual machine templates, download and run the installer for View Agent 4.5. You can download the installer from the VMware Web site. Step-by-step instructions for running the View Agent installer appear in the VMware View Administrator's Guide. 2 Take a snapshot of each upgraded parent virtual machine that you use to create linked-clone desktop pools with View Composer. For nonpersistent pools, you use the new snapshot for creating pools. For persistent pools, you use the new snapshot for recomposing all the virtual machines in the pool. For instructions on taking snapshots, see the vSphere Client online help. 3 If you use full-clone desktops or other virtual machines that you added as individual desktops or as part of a manual pool, upgrade View Agent by using whatever third-party tools you usually use for software upgrades. View desktops that were called individual desktops in View 3.1.3 or 4.0.1 deployments are added to manual pools in View 4.5. In the case of individual desktops, the manual pool contains only one desktop. 4 If you use Windows Terminal Servers or physical or blade PCs as desktop sources, download and run the installer for View Agent 4.5 on these physical machines. You can download the installer from the VMware Web site. 5 Use a View 3.1.3 or 4.0.1 client to verify that you can log in to the upgraded View 4.5 desktop sources with View 3.1.3 or 4.0.1 client software.

migrating to a new machine 32, 33 operating system requirements 12 port change 25, 30, 33 sviconfig database upgrade 27 upgrade preparation tasks 18, 30 upgrade procedure 25 View Connection Server hardware requirements 11 migrating to a new machine 23 purpose of 11 revert to a snapshot 24 supported operating systems 12 upgrade preparation tasks 17 upgrade procedure 21 upgrade requirements 12 vSphere compatibility 12 View LDAP 17 View LDAP upgrade 21 View Portal, browser requirements 15 View Transfer Server configuration, adding an instance 41 virtual hardware upgrade procedure 35, 36 virtual machines, upgrading 35, 36 VirtualCenter upgrade procedure 25, 30, 32, 33 VMotion 35, 36 VMware Infrastructure VMware Tools, upgrade procedure 35, 36, 43 VMwareVDMDS service 21 vSphere, upgrading components separately 43 vSphere data migration tool 30 vSphere mode for View Composer 35, 36 vSphere Update Manager 35, 36
Web browser requirements 14, 15 Windows 7 requirements for graphics 14 vSphere compatibility 16 Windows Terminal Servers 38