Information Technology Reference
In-Depth Information
VMM 2008 R2 SP1 is running an earlier version of SQL Server, you will need to update
to SQL Server 2008 R2 SP2 before upgrading to VMM 2012 R2.
You will need to ensure that Windows AIK for Windows 7 is installed on the VMM 2008
R2 SP1 server.
Library servers running Windows Server 2003 must be upgraded to Windows Server
2008 R2, as VMM 2012 R2 does not support library servers running on Windows Server
2003.
You also have the option of performing an upgrade where you install VMM 2012 R2 on
a separate computer, and upgrade the database from the VMM 2008 R2 SP1 installation. As
an alternative, you can backup the VMM 2008 R2 SP1 database from the original SQL Server
instance and restore it on a newly deployed instance of SQL Server. You can then use this
restored instance as part of the upgrade process when deploying VMM 2012 R2 on a new
computer.
During the upgrade process you will be asked to specify which account to use for the
System Center Virtual Machine Manager Service, and whether you want to use distributed key
management to store encryption keys within the AD DS database. You can choose to use the
Local System account or a domain account. If the VMM 2008 R2 deployment is configured to
use a domain account for the VMM service, you must use the same domain account for the
VMM 2012 R2 VMM service; otherwise encrypted data will not be preserved. Encrypted data
will be preserved if the VMM 2008 R2 service account was configured to use the Local System
account, and you choose to use a domain account for the VMM 2012 R2 service only if you
choose to use distributed key management.
The VMM 2012 R2 upgrade process includes an automatic rollback function in the event
that the upgrade fails. This will return the deployment to VMM 2008 R2.
MORE INFO
UPGRADING VMM
You can learn more about upgrading VMM at http://technet.microsoft.com/en-us/library/
dn469623.aspx .
Orchestrator
System Center 2012 Orchestrator was the first version of Orchestrator. Prior to the release of
System Center 2012 Orchestrator, the product was known as Opalis. You cannot perform an
in-place upgrade from Opalis 6.3 to System Center 2012 R2 Orchestrator. You can perform
a migration of Opalis policies to Orchestrator runbooks. To migrate, perform the following
general steps:
1.
Export the Opalis Integration Server 6.3 policies and global settings.
Import the policies on a computer where the Orchestrator Runbook Designer is in-
stalled. When prompted for a password, leave the Password option blank.
2.
 
Search WWH ::




Custom Search