Setting up Micetro in Azure - Micetro - 26.1.0

Step 1: Basics

In step 1, configure the basic settings for Micetro, including information regarding subscription, resource group, and location.

1. Select the Subscription to which you want the Azure Consumption of the deployment to be billed.
   Note: You will only be charged for the Azure Consumption used by the deployment. The Azure Marketplace offering comes with trial keys for all components of Micetro.
2. Select an empty Resource group or create a new one.
3. Select a Location.
   Warning: Latency varies depending on the location of the deployment and the location of the endpoints that are intended to be managed within Micetro.
   
   
   

Step 2: Virtual Machine

In the Virtual Machine step, configure the virtual machine settings, such as user credentials, system specifications, and storage accounts.

1. Select your Windows operating system from the dropdown.
2. When selecting Virtual machine size, consider the size of the environment you intend to manage.
   
   

   Our recommendations regarding virtual machine size are as follows:

   DNS zones	IP addresses	Subnets	Virtual machine size
   < 100	< 5000	< 1000	D2s_v3
   < 1000	< 50000	< 10000	D4s_v3
   Tens of thousands	Millions	Hundreds of thousands	D8s_v3

3. Select either a new or existing Diagnostic storage account.
   Tip: If you have an existing centralized storage account for VM diagnostics, you can use that.
4. In the Local administrator account section, enter a Username, which will be used as the local administrator account for the VM which will be created.
   Note: Some words are reserved and cannot be used for the account name, such as "admin", "administrator", and "user".
5. Enter a Password, which will be used as the password for the above mentioned local administrator account.
   Important: Passwords must contain at least twelve (12) characters, with at least one symbol and one number.

Step 3: Networking

In the Networking step, configure your network settings, such as the virtual network, subnets, ports, and DNS.

1. If you have extended your on-premise Active Directory to the Azure Cloud, you can optionally join the VM to the domain.
   Note: To join an Active Directory domain, the selected Virtual network must be able to communicate with the respective domain agent.
   1. Select the Virtual network from the dropdown.
   2. Select the Subnet.
2. Network Security Group
   • Select whether to Allow or Deny HTTP access to the machine. If allowed, the Micetro Web Application is accessible from the public internet.
3. Public DNS Name
   • Select a Public IP Address for the VM. If you select to create a new public IP address and the Virtual Network being deployed uses a Load Balancer, the SKU type selected must match the one used by the Load Balancer. For more information, refer to What is Azure Load Balancer?.
   • Enter a DNS Prefix for the public IP Address. The DNS prefix must be globally unique. A default value is given with "bluecat-" followed by a randomly generated unique string.

Step 4: Database Configuration

In the Database Configuration step, configure your database settings.

1. Enter a username that will be used as the SQL server administrator account for the Azure SQL server.
   Note: Some words are reserved and cannot be used for the account name, such as "admin", "administrator", and "user".
2. Enter a password that will be used as the password for the SQL server administrator account.
   Important: Passwords must contain at least twelve (12) characters, and include three (3) of the following: one number, one lowercase letter, one captial letter, and one special character.
3. Select a Database Edition from the dropdown. This determines the speed and capacity of the created database. For more information, refer to the Microsoft documentation.

Step 5: Active Directory

In the Active directory step, configure Active Directory credentials.

By joining the virtual machine to an Active Directory Domain, the Micetro DNS/DHCP Agents can be run under domain service accounts and the DNS/DHCP servers can be managed agent-free.

1. To join the virtual machine to Active Directory, select Yes.
2. Configure the Active directory administrator account by entering a username and password for the Domain user.
   Note: The credentials entered here require membership in the Administrators, or equivalent, on the local computer to complete the process of joining the domain.
   
   
   
3. Configure the Service account under which the Micetro DNS/DHCP should run by entering a username and password for the service account.

After deployment

The deployment may take up to 15–20 minutes, depending on the traffic of the Azure region to which you are deploying.

It may be helpful to reference the Architecture during the deployment.

When using Azure Marketplace, you receive the latest major version of Micetro, such as 25.1.0. If subsequent minor/patch versions have been released, such as 25.1.1, you need to update your Micetro version through the Web Application. Minor/patch versions are not available in Azure Marketplace.

For instructions on updating Micetro through the Web Application, refer to Updating Micetro components and appliances.