VMware VIEW 4.5 - GUIDE DE MISE A NIVEAU Guía de instalación descargar pdf (Pagina 29)

2 Examine the log records to identify the desktops that failed to upgrade.

Option Action

The desktop exists but is

unavailable.

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.

The desktop does not exist.

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.

3 Run the SviConfig databaseupgrade command again.

Migrate View Composer to Another Computer

In some situations, you might need to migrate a View Composer service to a new Windows Server

computer. For example, you might migrate View Composer and vCenter Server to a new ESXi host or

cluster to expand your View deployment. In addition, View Composer and vCenter Server do not have to be

installed on the same Windows Server computer.

You can migrate View Composer from the vCenter Server computer to a standalone computer or from a

standalone computer to the vCenter Server computer.

IMPORTANT These topics pertain to migrating View Composer 5.2 to another computer. You must upgrade

from View Composer 2.x or 3.x to View Composer 5.2 before you perform these tasks.

If your current version of View Composer is installed on a computer that does not meet the system

requirements for View Composer 3.0, you cannot use these procedures. For example, if you have View

Composer 2.6, which is included with View 4.6, installed on a Windows Server 2003 operating system, see

the procedure called "Manually Migrate View Composer to the New Machine" in the VMware View 4.6

Upgrades document. After you migrate View Composer 2.6 to a system with a Windows Server 2008 R2

operating system, you can perform an in-place upgrade to View Composer 5.2.

Guidelines for Migrating View Composer on page 30

The steps you take to migrate the View Composer service depend on whether you intend to preserve

existing linked-clone desktops.

Migrate View Composer with an Existing Database on page 30

When you migrate View Composer to another computer, if you intend to preserve your current

linked-clone desktops, the new View Composer service must continue to use the existing View

Composer database.

Migrate View Composer Without Linked-Clone Desktops on page 32

If the current View Composer service does not manage any linked-clone desktops, you can migrate

View Composer to a new computer without migrating the RSA keys to the new computer. The

migrated View Composer service can connect to the original View Composer database, or you can

prepare a new database for View Composer.

Prepare a Microsoft .NET Framework for Migrating RSA Keys on page 33

To use an existing View Composer database, you must migrate the RSA key container between

computers. You migrate the RSA key container by using the ASP.NET IIS registration tool provided

with the Microsoft .NET Framework.

Migrate the RSA Key Container to the New View Composer Service on page 33

To use an existing View Composer database, you must migrate the RSA key container from the source

computer on which the existing View Composer service resides to the computer on which you want to

install the new View Composer service.

Chapter 5 Upgrading Horizon View Server Components

VMware, Inc. 29

1 2 ... 24 25 26 27 28 29 30 31 32 33 34 ... 61 62

Comentarios a estos manuales

Sin comentarios

VMware VIEW 4.5 - GUIDE DE MISE A NIVEAU Guía de instalación Pagina 29

Comentarios a estos manuales

Relacionado con productos y manuales para Software de gestión de sistemas VMware VIEW 4.5 - GUIDE DE MISE A NIVEAU