Embotics® vCommander®  allows you to manage VMware vCenter, Microsoft SCVMM, Amazon Web Services and Microsoft Azure systems. When you add a private or public cloud to vCommander, we call it a managed system. This article explains how to add managed systems.

See also Troubleshooting Managed Systems.

question mark

The time this task takes to complete varies according to the number of VMs on the managed system.  In a typical environment of approximately 1,000 VMs, this task can take up to 10 minutes to complete. However, the performance of vCommander and of the managed system is not affected, because this activity runs in the background.

Adding a vCenter managed system

Access through:

Views menu > Operational or VMs and Templates

Available to:

vCommander Roles of Superuser and Enterprise Administrator

Before you add a managed system to vCommander, an administrative account must be set up in vCenter. You will enter the credentials for this account when adding the managed system to vCommander. For more information, see "Preparing to Install" in the vCommander Installation Guide.

See also Troubleshooting Managed Systems.

To add a vCenter managed system:

1.Select the root node of the Operational or VMs and Templates view.

2.In the Commands pane, click Add Managed System.

3.In the Managed System Type drop-down menu, leave the default setting, VMware Virtual Center.

4.Complete the fields as required:

Host: Enter the unique name of the managed system using its IP address or host name.

Port: If required, specify a port for https other than the default of 443.

Username: Enter the user name for the account you will use to administer this managed system.

For a domain account, enter the user name in this format:

domain\username

Password: Enter the password for this account.

5.Click OK.

Details about the managed system are displayed in its Summary tab. You can change what is displayed in the Details pane (see Customizing the Embotics® vCommander® Display).

NotePencil-smallTo grant permission to other users to work on the managed system, you must assign the appropriate access rights.

Adding an SCVMM managed system

Access through:

Views menu > Operational or VMs and Templates

Available to:

vCommander Roles of Superuser and Enterprise Administrator

Important notes

Before you add an SCVMM managed system, the System Center VMM Administrator Console must be installed on the vCommander host, and the vCommander Hyper-V Adapter service must be running on the vCommander host.

Before you add a managed system, an administrative account must be set up in SCVMM. You will enter the credentials for this account when adding the managed system to vCommander. For more information, see "Preparing to Install" in the vCommander Installation Guide.

The account used to add the SCVMM managed system to vCommander must have full administrator permissions on SCVMM. If the account has only delegated administrator permissions, automated deployment may fail.

See also Troubleshooting Managed Systems.

To add an SCVMM managed system:

1.Select the root node of the Operational or VMs and Templates view.

2.In the Commands pane, click Add Managed System.

3.In the Managed System Type drop-down menu, select Microsoft SCVMM.

4.Complete the fields as required:

Host: Enter the unique name of the managed system using its IP address or host name.

Port: If required, specify a port for https other than the default of 8100.

Username: Enter the user name for the account you will use to administer this managed system.

For a domain account, enter the user name in this format:

domain\username

Password: Enter the password for this account.

5.Click OK.

Details about the managed system are displayed in its Summary tab. You can change what is displayed in the Details pane (see Customizing the Embotics® vCommander® Display).

NotePencil-smallTo grant permission to other users to work on the managed system, you must assign the appropriate access rights.

Adding an AWS managed system

Access through:

Views menu > Operational or VMs and Templates

Available to:

vCommander Roles of Superuser and Enterprise Administrator

Important: See Managing Amazon Web Services with Embotics® vCommander® for a list of tasks to complete before adding an Amazon Web Services account as a managed system.

See also Troubleshooting Managed Systems.

To add an AWS account as a managed system:

1.Select the root node of the Operational or VMs and Templates view.

2.In the Commands pane, click Add Managed System.

3.From the Managed System Type menu, select Amazon Web Services.

4.Name: Enter a name that will help identify this managed system.

5.Access Key ID: Enter the access key ID from your AWS (Amazon Web Services) credentials.

6.Secret Access Key: Enter the secret access key from your AWS credentials.

7.If this account is authorized for GovCloud, enable the option AWS GovCloud account.

NotePencil-smallAWS GovCloud (US) Region accounts can be obtained only by individuals or entities that qualify as U.S. Persons under applicable regulations.

8.Update Frequency: vCommander retrieves changes from AWS and generates events based on these changes. By default, vCommander waits 60 minutes between updates. You can enter a value from 10 to 180 minutes. The last update time is displayed on the Summary tab for the managed system.

Note that this setting affects only how often configuration changes made in AWS are retrieved; changes made within vCommander are displayed as soon as the task has finished.

NotePencil-smallWhen a service exists for a shorter time period than the update frequency, the service may not be discovered by vCommander during the update.

If you do make changes outside vCommander and you want these changes to be visible in vCommander before the next scheduled update, you can synchronize the inventory.

Caution: More frequent updates (meaning lower values for this setting) may impact vCommander performance, especially in large installations.

9.Use Public Cloud Proxy: If the vCommander server is behind a firewall, enable Use Public Cloud Proxy.

NotePencil-smallIf you haven't already integrated your proxy server with vCommander, click Add Public Cloud Proxy Server and configure the proxy. For instructions, see Connecting Amazon Web Services to Embotics® vCommander® through a Proxy Server.

10.Sync Tags and Custom Attributes: To synchronize AWS tags and vCommander custom attributes, click Configure.

In the Synchronize AWS Tags and vCommander Custom Attributes dialog, enable the options Import AWS Tags as vCommander Custom Attributes and/or Export vCommander Custom Attributes as AWS Tags as required.

To exclude certain AWS tags and custom attributes from synchronization, enter them as a comma-separated list in the Excluded Tags/Custom Attributes text field.

NotePencil-smallTags prefixed with "aws:" are reserved for AWS use and are automatically excluded from sync. vCommander form-type custom attributes are also automatically excluded.

You can enter up to 5000 characters in this field.

Click OK.

To learn more, see Synchronizing AWS Tags and Embotics® vCommander® Metadata.

11.Click OK to finish adding the managed system.

Details about the managed system are displayed in its Summary tab. You can change what is displayed in the Details pane (see Customizing the Embotics® vCommander® Display).

What's next?

You can configure vCommander to retrieve AWS billing data, so that VM billing records are more accurate.

To grant permission to other users to work on the managed system, you must assign the appropriate access rights.

Adding an Azure Resource Manager (ARM) managed system

Access through:

Views menu > Operational or VMs and Templates

Available to:

vCommander Roles of Superuser and Enterprise Administrator

vCommander manages each Azure Resource Manager subscription as a separate managed system. If your Azure account has multiple subscriptions, you need to add each subscription as a separate vCommander managed system.

Important: See Managing Azure with Embotics® vCommander® for a list of tasks to complete before adding a Microsoft Azure Resource Manager subscription as a managed system.

See also Troubleshooting Managed Systems.

To add an Azure subscription as a managed system:

1.Select the root node of the Operational or VMs and Templates view.

2.In the Commands pane, click Add Managed System.

3.In the Managed System Type drop-down menu, select Microsoft Azure.

4.Name: Enter a name that will help identify this managed system.

5.Subscription ID: Enter the Azure subscription ID. See Managing Azure with Embotics® vCommander® for more information.

6.Tenant ID: Enter your Azure tenant ID. See Managing Azure with Embotics® vCommander® for more information.

7.Application ID: Enter your Azure application ID. See Managing Azure with Embotics® vCommander® for more information.

azure-portal-settings

8.API Key: Enter your Azure API key (or authentication key). See Managing Azure with Embotics® vCommander® for more information.

9.Update Frequency: vCommander retrieves changes from the public cloud account and generates events based on these changes. By default, vCommander waits 60 minutes between updates. You can enter a value from 10 to 180 minutes. The last update time is displayed on the Summary tab for the managed system.

Note that this setting affects only how often configuration changes made in the public cloud account are retrieved; changes made within vCommander are displayed as soon as the task has finished.

NotePencil-smallWhen a service exists for a shorter time period than the update frequency, the service may not be discovered by vCommander during the update.

If you do make changes outside vCommander and you want these changes to be visible in vCommander before the next scheduled update, you can synchronize the inventory.

Caution: More frequent updates (meaning lower values for this setting) may impact vCommander performance, especially in large installations.

10.Click OK.

Details about the managed system are displayed in its Summary tab. You can change what is displayed in the Details pane (see Customizing the Embotics® vCommander® Display).

NotePencil-smallTo grant permission to other users to work on this managed system, you must assign the appropriate access rights.

Adding an Azure Service Manager (Classic) managed system

Access through:

Views menu > Operational or VMs and Templates

Available to:

vCommander Roles of Superuser and Enterprise Administrator

vCommander manages each Azure Service Manager subscription as a separate managed system. If your Azure account has multiple subscriptions, you need to add each subscription as a separate vCommander managed system.

Important: See Managing Azure Classic with Embotics® vCommander® for a list of tasks to complete before adding a Microsoft Azure Service Manager subscription as a managed system.

See also Troubleshooting Managed Systems.

To add an Azure subscription as a managed system:

1.Select the root node of the Operational or VMs and Templates view.

2.In the Commands pane, click Add Managed System.

add-managed-sys-azure

3.In the Managed System Type drop-down menu, select Microsoft Azure (Classic).

4.Name: Enter a name that will help identify this managed system.

5.Subscription ID: Enter the subscription ID from your Azure credentials.

NotePencil-smallYou can find this ID in the Settings page on the Azure Management Portal.

6.As part of adding an Azure managed system, you must upload a public key certificate to the Azure Management Portal. This certificate authenticates vCommander in Azure.

To upload a certificate in the Azure Management Portal:

a.Click Download Certificate for Azure.

b.Once the vCommander.cer certificate file has been downloaded, log in to the Azure Management Portal (https://portal.azure.com/).

c.In the left-hand pane, click Subscriptions, then select your subscription.
azure-cert-upload-select

d.On the right-hand configuration pane for your subscription, click Management Certificates, and then click Upload.
Note that before uploading a certificate for your system, you must delete any other certificates for that system.

e.In the Upload Certificates Preview, select your subscription, click the folder button to browse to the .cer certificate file you downloaded, and click Upload.

f.When the upload is complete, you should see the vCommander host name in the list of management certificates.

g.Now go back to vCommander to finish adding the managed system.

7.Update Frequency: vCommander retrieves changes from the public cloud account and generates events based on these changes. By default, vCommander waits 60 minutes between updates. You can enter a value from 10 to 180 minutes. The last update time is displayed on the Summary tab for the managed system.

Note that this setting affects only how often configuration changes made in the public cloud account are retrieved; changes made within vCommander are displayed as soon as the task has finished.

NotePencil-smallWhen a service exists for a shorter time period than the update frequency, the service may not be discovered by vCommander during the update.

If you do make changes outside vCommander and you want these changes to be visible in vCommander before the next scheduled update, you can synchronize the inventory.

Caution: More frequent updates (meaning lower values for this setting) may impact vCommander performance, especially in large installations.

8.Click OK.

Details about the managed system are displayed in its Summary tab. You can change what is displayed in the Details pane (see Customizing the Embotics® vCommander® Display).

NotePencil-smallTo grant permission to other users to work on this managed system, you must assign the appropriate access rights.