Note: This is an inplace upgrade of a previoulsy installed vCenter 4 instance. Update 1 can also be installed as a fresh instance. Don’t forget to upgrade your vSphere Client after completing this tutorial.
I’am using the following image:
VMware-VIMSetup-all-4.0.0-208156.iso
1. Insert or mount the DVD with VMware vCenter 4 update 1. You will be presented with the screen below. Before we start the installation we want to check each host and make sure they are ready and compatible with update 1. Under the Utility menu, click “Agent Pre-Upgrade Check”
2. The welcome screen for the Agent Pre-Upgrade check appears. Click Next.
3. In this screen we are asked for which DSN we would like to use to connect to the database. The default install of vCenter 4 creates the DSN VMware VirtualCenter. If you have installed the full version of SQL and setup your DSN manually, then simply select the DSN in the drop down menu. Select your authentication method, we are using Windows Credentials. Click Next.
4. Do you want to scan all hosts (Standard Mode) or manually select which VMware hosts you would like to scan (Custom Mode) for compatibility. As I currently only have one host installed and connected to vCenter. I will select Standard Mode. Click Next.
5. The pre-check is now ready to run. You can see the total amount of hosts that the pre-check will scan. Click Run precheck.
6. The pre-check is has completed with no errors. Click Next.
7. You can see in the screen shot below that my one VMware host (vmcluster1.vmlab.local) has passed the pre-check. You can click on View Report for more information. Click Next.
8. This completes the Pre-Check wizard. Once you click Finish you will return back to the vCenter product installation windows.
9. Now that we have ran the “Agent Pre-upgrade Check” we are now ready to install vCenter 4 Update 1. Click vCenter Server.
10. A notification window appears letting you know that this will upgrade vCenter server to update 1. Click Yes.
Note: If you don’t have vCenter installed and this is the first time installing it, you will not see this window.
[ad#sysadmintutorialsRectanglePosts]
11. You are presented with the vCenter Server install wizard. Click Next.
12. Accept the license agreement and click Next.
13. Select the Data Source name that you have configured on the server for use with vCenter. Click Next.
Note: If this is a new install, you can either select “Install a Microsoft SQL Server 2005 Express instance” (which is for smaller scale deployments or testing/lab scenarios) or Use an existing support database and select the Data Source Name that you use to communicate with your SQL or Oracle server.
14. As we are using Windows Authentication we will leave these fields blank, the installer will use the currently logged on user to authenticate to the database. Otherwise enter the username and password to communicate with the database. Click Next.
16. As we are upgrading and want to keep all our existing data within our database server, I will select “Do not overwrite, leave my existing database in place”. Click Next
Note: You do have the option to start with a fresh database, however you would only select this in a new install or if your database is corrupt and unrecoverable.
17. Enter the credentials of the account used to run the vCenter services, or select “Use SYSTEM Account”. Click Next.
18. Verify that all the ports are correct as per your original install. Click Next.
19. We are now ready to begin the actual upgrade. Click Install.
20. As your vCenter services are probably still running, this window warns you that these files need to be updated, and in order to do so the services will need to be stopped. You also have the option to keep the services running and reboot the server at the end of installation to update the necessarry files. Click Ok.
21. Installation is now complete. Your vCenter server will now be running update 1. Click Finish.
Disclaimer: All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.
Be the first to comment