VMware

VMware vCenter Orchestrator Plug-In for Microsoft Active Directory 1.0 Release Notes

VMware vCenter Orchestrator Plug-In for Microsoft Active Directory 1.0 | 29 Apr 2011 | Build 96

VMware vCenter Orchestrator 4.1 | 13 Jul 2010 | Build 581

Last Document Update: 29 Apr 2011

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Introduction to the VMware vCenter Orchestrator Plug-In for Microsoft Active Directory

The VMware vCenter Orchestrator plug-in for Microsoft Active Directory allows organizations to automate the management of directory services tasks, particularly as they pertain to cloud provisioning use cases. For instance, the plug-in enables the automatic provisioning of vCloud Director organizations based on data retrieved from Active Directory. The plug-in also includes many administrative actions related to computers, organizations, user groups, and users, such as resetting passwords or adding users to a user group. The drag-and-drop workflow designer of vCenter Orchestrator allows you to easily assemble these actions into higher-level workflows to automate repetitive Active Directory administrative tasks.

The VMware vCenter Orchestrator plug-in for Microsoft Active Directory 1.0 release runs on VMware vCenter Orchestrator 4.1 and later. The plug-in is compatible with Microsoft Active Directory 2003 and 2008. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for Microsoft Active Directory.

Top of Page

Known Issues

The following issues are known limitations in the VMware vCenter Orchestrator Plug-In for Microsoft Active Directory 1.0 release:

  • Network connectivity between Orchestrator and all domains in a forest is required to use the multi-domain feature

    You cannot run workflows on subdomains that are not connected to Orchestrator. Subdomains that do not have network connectivity are not visible to Orchestrator.

  • Subdomains require the same port as the root domain

    If you try to connect to a subdomain, you must use the root domain port number, which is specified in the Orchestrator configuration interface.

    Note: Subdomains must use the same type of connection as the root domain.

  • Orchestrator cannot reconnect to domains

    If a domain is unavailable or there is no network connectivity when you start the Orchestrator client, the domain is not listed in the Inventory view and you cannot run workflows on the domain.

    Workaround: Restart the Orchestrator client when network connectivity to the domain is restored.

Top of Page