Quantcast
Channel: VMware Communities: Message List - vSphere Upgrade & Install
Viewing all articles
Browse latest Browse all 11859

Re: Upgrade vSphere from 4.1 to 5.1

$
0
0

Based on what I've read thus far Albert is that the installation DVD has scripts for the different databases that you run prior to the installation to prepare for SSO.

 

VMware vSphere 5.1 Documentation Center

Verify that your vCenter Server database meets the database requirements. See vCenter Server Database Configuration Notes and Preparing vCenter Server Databases.

Create a vCenter Server database, unless you plan to install the bundled database.

Create a vCenter Single Sign-On database, unless you plan to install the bundled database.

If you are using an existing database for Single Sign-On, you must create a database user (RSA_USER) and database administrator (RSA_DBA) to use for the Single Sign-On database installation and setup. To create these users, run the script rsaIMSLiteDBNameSetupUsers.sql. The script is included in the vCenter Server installer download package, at vCenter Server Installation directory\Single Sign On\DBScripts\SSOServer\Schema\your_existing_database..

If you are using an existing database with your vCenter Single Sign-On installation or upgrade, make sure that the table spaces are named RSA_DATA and RSA_INDEX. Any other table space names will cause the vCenter Single Sign-On Installation to fail.

If you are using an existing database for Single Sign-On, to ensure that table space is created for the database, run the script rsaIMSLite<DBName>SetupTablespaces.sql. The script is included in the vCenter Server installer download package, at vCenter Server Installation directory\Single Sign On\DBScripts\SSOServer\Schema\your_existing_database. You can run this script prior to the installation, or during the installation, when you are prompted by the installer. You can leave the installer to run the script, and resume the installer after you run the script.

If you are using an existing Microsoft SQL Server database for Single Sign-On, and you want to use a dynamic port, you must provide a named instance for the SQL database during the Single Sign-On installation. The instance name created during Microsoft SQL Server installation usually defaults to MSSQLSERVER. For non-default instance names, you can determine the instance name after Microsoft SQL Server is installed by using the SQL Configuration Manager. Under SQL Server Network Configuration, the SQL Configuration Manager lists all available instances of the SQL installation.

If you install Single Sign-On with an external Microsoft SQL Server database, using a static port, and you have a firewall between Single Sign-On and the external database, you must open a static port on the firewall to communicate between Single Sign-On and the database. For example, to do this in Windows Server 2008, you can add a static port in the Windows Firewall Control Panel.


Viewing all articles
Browse latest Browse all 11859

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>