How do I allow HealthCheck for Azure to collect information from a private VMware vCenter server?
HealthCheck for Azure analyzes a customer’s virtual and physical environment over a 14-day period. Once the analysis is complete, you will have access to an assessment of the customer’s infrastructure as an Azure environment and a detailed mapping of their environment to help you plan their migration to Azure.
Purchase a HealthCheck for Azure Plan license for each virtual machine in your customer’s infrastructure, but not for the Hyper-V hosts or vCenter servers. For instruction on purchasing licenses, see How do I purchase licenses (KB004647).
Note: Installing the Agent only on the Hyper-V hosts is not sufficient. We recommend that that you install the Agent on all virtual and physical servers in your network to ensure a full and accurate assessment of your infrastructure.
Follow these steps to allow HealthCheck for Azure to collect information from a private VMware vCenter server. Install the agent everywhere in the customer's infrastructure, even if you only want an analysis of a subset of the infrastructure. This allows HealthCheck for Azure to analyze the entire topology, and give you better guidance for your customer’s migration.
- Log on to your MSPComplete account and, from the All Products dashboard, select the HealthCheck for Azure tile.
- From the drop-down, select the customer. If the customer does not yet exist in the MCPComplete system, click New, then create the customer.
- Click the Go To HealthCheck for Azure button.
- If you have previously provisioned HealthCheck for Azure, or upon provisioning HealthCheck for Azure, click Activate Service.
- In the VMWare box, click on Setup to download the VMWare Collector.
Note: Before running the installer, make sure that all computers on which the agent is being installed have the internet outbound port 443 open to agent.cloudamize.com (FQDN) or IP address 188.8.131.52. This establishes a direct connection to the HealthCheck for Azure server. For an indirect connection, you can specify your own proxy during the installation, and the agent will communicate with the HealthCheck for Azure server via your proxy.
- Toggle to the VMware vCenter server and open Server Manager. Create a read-only user account on the VMware vCenter host machine that will allow the HealthCheck for Azure Agent to collect workload data from the virtualized machines that are connected to that vCenter.
- From the left navigation pane, click on Configuration, then click on Local Users and Groups, then click on Users.
- Create a new user.
- In the Username, Full name, and Description fields, type healthcheck-read-only.
- Enter a password, and click on Create.
Important: Write down the username and password. You will enter them into the HealthCheck for Azure sign-up page.
- Open User Properties for the newly created user.
- Click on the Member Of tab and click on Add.
- Click on Users, and then click OK.
- Click OK.
- Open the vCenter management dashboard, right-click on vCenter, and click Add Permission.
- Click on Add.
- Select the healthcheck-read-only user account from the Users and Groups list and click OK.
- From the Assigned Role drop-down list, select Read-only, and click OK.
- To verify that the setup was done correctly, click on the Permissions tab from your vCenter, and confirm that the role for the newly created account is set to read-only.
- Toggle back to the HealthCheck for Azure sign-up page and enter the vCenter name, IP address, and credentials for the read-only user you just created on the machine that is hosting your VMware vCenter.
Important: VMware vCenter can have either a public or private IP address. If your vCenter IP address is a private IP address (e.g., 10.x.x.x or 192.168.x.x), you will need to install the HealthCheck for Azure Proxy that will forward data to the HealthCheck for Azure server. The HealthCheck for Azure sign-up page will recognize when you provide a private IP address, and will offer the HealthCheck for Azure Proxy for download.
For instructions on installing and configuring the Agent Proxy, see Set Up and Configure a Proxy Connector to the VMware VCenter (KB005556).