<

HOW TO: Deploy and Install VMware vSphere vCenter Server 7.0 (VCSA 7.0)

Posted on
10,080 Points
80 Views
Last Modified:
Published
Experience Level: Beginner
34:48
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
EE Fellow, MVE, Expert of the Year 2021,2017-11, Scribe 2016-2012, Author of the Year 2018-6,2013-2012 VMware vExpert Pro, vExpert 2025-2011
In this video, I will show you how to Deploy and Install the VMware vSphere vCenter Server 7.0 (VCSA 7.0), with some helpful tips along the way.

For more guidance and a step by step tutorial with screenshots, which supports this video, please see the following article which this video is based on  HOW TO: Deploy and Install VMware vSphere vCenter Server 7.0 (VCSA 7.0)

Video Steps

1. Pre-requisites.

Download the VMware-VCSA-all-x.y.z-abcdefg.iso (DVD image) from VMware and before you start allocate a static IP Address for vCenter Server 7.0 and create an A Record in DNS

2. Mount the ISO.

Mount the ISO, and browse to the folder - vcsa-ui-installer\win32 on the DVD, click the installer.exe file to start the installation of VMware vCenter Server 7.0. There is an OVA present in the ISO. vCenter Server is not designed to be deployed from the OVA. Use the vcsa-ui-installer.

3. Follow the wizard.

Ensure to use a hostname, and FQDN, you did create an A Record in DNS before you started the installation?

4. Configuring VMware vCenter Server 7.0..

Click Continue to proceed with Stage 2 of the deployment process.

5. Connecting to vCenter Server 7.0.

Click the FQDN URL, to access vCenter Server using the vSphere Web Client..
0
0 Comments
Secure Boot is a mode of running VMware ESXi server  that helps prevent malicious files and programs like ransomware from being loaded on to it. This is due to the fact it will only allow signed software packages. However, the recovery keys need to …
Facing persistent SCCM client installation or uninstallation issues? Use a script-based approach to reset the WMI repository and re-register components. This method resolves deep-rooted problems and restores SCCM functionality. Here's a quick step-b…