BitTitan has partnered with Cloudamize to provide HealthCheck for Azure. HealthCheck for Azure is a network assessment and migration planning tool that measures the readiness of your network infrastructure for migration to Azure, and also provides migration planning tools.
HealthCheck for Azure scans all of a network’s physical and virtual nodes over a 14-day period, analyzes the network infrastructure, assesses migration readiness, and calculates the cost to move servers and workloads to Azure. Additionally, it maps dependencies among network nodes, applications and services, and provides a configuration map on which to base migration planning.
In the process, the network analysis calculates server loads over time and can then recommend server and workload configurations in Azure that enable infrastructure planning and optimizes resource loading. Ultimately, HealthCheck for Azure assesses a network’s cloud-readiness and provides recommendations, guidance, and planning tools for a successful migration.
For a hands-on demo and technical deep-dive, see the webinar: HealthCheck for Azure Technical Boot Camp (1:08).
HealthCheck for Azure licenses and accounts
Using HealthCheck for Azure requires that you have a sufficient number of licenses to run your assessment project. You must purchase one license for each network node (virtual or physical server) that you intend to assess.
For guidance on creating customers, see View, add, and edit your customers. To purchase licenses:
- Log on to your MSPComplete account and click on Purchase in the top right corner of the page.
- On the left navigation bar, select HealthCheck, then select the number of licenses you wish to purchase, then click Next.
- Follow the remaining prompts to complete your purchase.
Provision the HealthCheck for Azure Account
With licenses purchased, you can provision your account.
- 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.
- Next, select the plan, then select Azure as the assessment target. (For more information about available plans, see HealthCheck for Azure Assessments and Pricing Plans.)
- Click Next.
- On the Account Information page, view the order summary. If necessary, purchase additional licenses.
- Click Confirm on the Purchase Order Information page.
Add and remove licenses
To add additional licenses, or to remove existing licenses:
- Log on to your HealthCheck for Azure for the desired customer, and click on the Licenses link.
- The Update licenses pane appears.
From the Update licenses pane you can see the total number of licenses currently available, as well as the number of licenses presently assigned to your assessment.
From the pane you can do any of the following:
- Add licenses to the assessment.
- Remove licenses from the assessment.
- Purchase additional licenses, if needed.
Download and install the agent
Running the HealthCheck for Azure assessment requires that you download and install the assessment Agent on all of the nodes in your network infrastructure. We recommend that you install the Agent throughout the network, even on servers that you may not intend to migrate. This is because one of the services that the assessment provides is creating a graphical map of all of your network’s application and server dependencies. Being able to visualize all of these dependencies is essential to migration planning.
For instructions and guidance on installing the agent, see the following:
- How do I install the Windows Agent by using a Group Policy Object and Active Directory?
- How do I install the Windows HealthCheck for Azure Agent using a graphical user interface?
- How do I install the Linux HealthCheck for Azure Agent?
- How do I install the HealthCheck for Azure Agent on a Hyper-V Environment?
- How do I allow HealthCheck for Azure to collect information from a private VMware vCenter server?
- How do I allow HealthCheck for Azure to collect information from a public VMware vCenter server?