On 11/28/17, from 2am to 6am PST, BitTitan will shut down all web traffic to Manage.BitTitan.com and MigrationWiz.com (MSPComplete and MigrationWiz). While there will be no access at this time, migrations in progress should not be disrupted.
x

How do I allow HealthCheck for Azure to collect information from a public VMware vCenter server?

​How do I allow HealthCheck for Azure to collect information from a public VMware vCenter server?

Answer:

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.

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.​​

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. 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.

Follow these steps to allow HealthCheck for Azure to collect information from a public VMware vCenter server:

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 104.197.11.97​. 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 server that will allow HealthCheck for Azure to collect workload data from the virtualized machines that are connected to that vCenter.

From the left navigation pane, click on Configuration, then click Local Users and Groups, then click Users.

Create a new user.

In the Username, Full name, and Description fields, type "healthcheck-read-only."

Enter a password, and click 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 Add.

Click Users and then click OK.

Open the vCenter management dashboard, right-click on vCenter, then click Add Permission.

Click Add.

Select the healthcheck-read-only user account from the Users and Groupslist and then click OK.

From the Assigned Role drop-down list, select Read-only, then 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. The proxy connects to the vCenter IP on port 443, as well as the HealthCheck for Azure server (184.73.183.154) over port 80. If your VMware vCenter server is behind a firewall, allow outbound access on port 80 to IP address 184.73.183.154 and allow access on port 443 from the proxy (vCenter/Windows VM) to the vCenter IP address.

The HealthCheck for Azure Proxy can be installed either directly on the vCenter server or on a separate Windows virtual machine. The proxy is unique and per vCenter and virtual machine (VM). For example, if you have two vCenters, you will need two unique proxies that will need to be installed on either two Windows VMs or two vCenters.

Click Download.

Once downloaded, run the installer as an administrator and click Next.