The configuration script included on the VM desktop runs a sequence of actions to prepare the VM to use the Core. It removes the Core ID associated with the VM (to avoid Cores with duplicate IDs); starts the Core service; moves the trial license to the desktop; creates a desktop shortcut for the Core Console; and automatically creates a repository on any new disks attached to your VM.
This task describes the process of running this configuration script from the shortcut on the desktop of your Rapid Recovery Core VM. Quest recommends performing this process after first attaching storage to the Azure VM, and repeating it each time you add additional storage to your VM. Running this script initially typically takes about five minutes, after which the command window closes.
After initial configuration of your VM, if you attach additional storage from the Azure Marketplace, running this script again configures the virtual disk as the storage location for your repository. When run subsequently, the script takes less than a minute to run.
Perform this procedure to configure your Core the first time, and each time you add additional storage.
- From the Azure VM desktop, right-click on the Configure Rapid Recovery Core shortcut, and from the context-sensitive menu, select Run as administrator.
A command window entitled Administrator: Windows PowerShell appears, and the script begins to run. Several operations occur sequentially, and the progress of the script is logged in the command window.
- If a Microsoft Windows dialog box appears prompting you to format the disk before you can use it, click Cancel.
The script continues to run; the script formats the storage drive in the most efficient manner for using the Rapid Recovery Core. When the script is complete, the command window closes. The Core Console shortcut appears on the desktop, to let users easily launch the Rapid Recovery Core Console.
Next steps
Before protecting machines in your Core or replicating from another Core, you must disable the Compatibility View feature in the Internet Explorer web browser. For more information, see Disabling Compatibility View in Internet Explorer.
Before using your Core, you must associate a license key. For more information, see Activating your Rapid Recovery license.
If using a standard license with Rapid Recovery Core, you must agree to the use of privacy information. For more information, see X.
Internet Explorer includes a Compatibility View feature. The purpose of this feature is to correct the display of websites optimized for old versions of Internet Explorer (version 7 or earlier). By default, this option is typically enabled for all intranet sites, but can present problems when viewing modern web interfaces.
This task describes the process to disable the Compatibility View option of Internet Explorer, which is required for using the Rapid Recovery Core Console on the Azure VM. This is a one-time setup step.
Perform the steps described in the following procedure to disable Compatibility View in Internet Explorer.
- Open an Internet Explorer web browser window on the Azure VM.
For example, double-click the Core Console shortcut on the VM desktop.
An Internet Explorer web browser window opens. If the content does not display, check for and disable the Compatibility View feature as follows.
- If the Set up Internet Explorer 11 dialog box appears, do the following:
- Select Don't use recommended settings.
- Optionally, clear Send Do not Track requests to tell sites you prefer not to be tracked.
- Click OK.
The dialog box closes, and Compatibility View is now disabled.
- If the dialog box does not appear, from Internet Explorer, click the
Tools icon, and then select Compatibility View settings.
The Compatibility View settings dialog box appears.
- In the Compatibility View settings dialog box, clear the following settings:
| Display intranet sites in Compatibility View |
You must clear this option. |
| Use Microsoft compatibility lists |
You must clear this option. |
- Click Close.
The dialog box closes, and Compatibility View is now disabled.
To perform this task, you must be using a Windows machine on which PowerShell is enabled. You must also have access to an Azure account that is granted the service administrator or service co-administrator role.
The Publish Settings file is an XML document generated on Azure. The file contains the AzureServiceManagement API definition, and information about your Azure subscription, including secure encoded credentials, your subscription type, and an Azure management certificate. This file contains a file extension of .publishsettings, from which the description is derived. Without the Publish Settings file, you cannot connect your Core to an Azure account.
You can obtain a copy of the Publish Settings file from a Windows machine logged into your Azure account.
|
|
Caution: Since the publish settings file contains your credentials and information about your Azure account, Microsoft recommends storing the publish settings file in a secure location. Once you have loaded the certificate, you can delete the file from your local system. |
Microsoft imposes a limit of 100 management certificates per subscription, with an additional maximum limit of 100 management certificates for all subscriptions under a specific service administrator’s user ID. If you need to access the same Azure account from multiple Cores, you can generate the Publish Settings file one time and re-use the same file to load the management certificate into multiple Cores. In this way, you can avoid exceeding the certificate generation limit.
Complete the steps in this procedure to obtain the Publish Settings file.
- From a Windows machine, log into the Azure dashboard.
- While logged into Azure, open another browser window.
- Execute a PowerShell script to download the file by entering the following address into the URL of the browser: https://manage.windowsazure.com/publishsettings/index?client=powershell.
When successful, the Publish Settings file is saved to your default download directory.
- Move this file to a machine accessible to the Core Console.
To associate Azure subscription information with your Rapid Recovery Core, see the Rapid Recovery User Guide topic "Loading an Azure management certificate."
Generally, each Core must have a software license that registers with the license portal. This section contains information relevant to using Rapid Recovery in Azure.
The following topics describe information about licensing.