Home > Blogs > VMware vCenter Orchestrator Blog > Tag Archives: plug-in

Tag Archives: plug-in

How to manage everything as a service with vRealize Automation ?

One of the great feature of vRealize Automation is that it can be extended way beyond your virtual infrastructure to manage Anything as a Service (XaaS). This means using its self service portal for provisioning, running day two operations and decommissioning any type of services. Just think about the many different services an IT organization delivers to its end users. many distinct processes, people and interfaces involved that could be offered as a service.

XaaS comes into two flavors in vRA:

  • An XaaS catalog item, similar to an application blueprint can be requested directly. Once provisioned it is listed under the items tab where it can be opened to show properties and operated. The vRA service designer the service with defining the details level and operations users can perform and entitle these to different user groups

Requesting a DNS host Record


Operating a DNS host record : Removal action


  • An XaaS component can be added to an application blueprint. When requested by a user the XaaS component get requested as well and is displayed as part of the application deployment.

Requesting an application blueprint including a DNS host record XaaS component

It can be operated from there and will be decommissioned automatically with the application

Operating a DNS host record : Removal action


How does this work ?

vRA can be extended to manage new entities that are called custom resources. Technically a vRA custom resources maps to a vRO plug-in inventory object.

Adding a custom DNS Host resource mapping to a Microsoft DNS.resourceRecord vRO Dynamic Type

New resources can be provisioned using an XaaS blueprint that is basically a mapping to a vRO workflow that create and output the object

Adding an XaaS blueprint

Resource actions are mapping to vRO workflows that take a custom resource as an input and operate it.

Adding an resource action

vRA displays with updating in real time the properties of the resources provisioned for each users in the items tab by leveraging the vRO plug-in inventory

How does a vRO plug-in work ?

One of the function of a vRO plug-in is to provide an inventory of managed objects: in a similar way vCenter displays an inventory of Hosts, VMs, networks and storages vRO can manage any type of objects. Once there are new managed objects in the inventory you can create CRUD (Create, Rename, Update, Delete) workflows to operate them.

The first thing a vRO admin does to configure a plug-in is to add a management host. For example adding a vCenter Host to its inventory so vRO can query vCenter API to populate the vCenter inventory.

vRO knows how to query the child resources of the management host because there is in each vRO plug-in a configuration file that documents what kind of child objects are to be discovered under a parent object and how to query the child objects properties. This is done using the plug-in findRelation() method.

When you select a plug-in object in one of vRO workflow input field:

  • Using the tree-view a plug-in method called hasChildrenInRelation() is called to show if a parent object has child objects then findRelation() is called to list the child objects.
  • Using a drop down a plug-in method called findAll() is called to list all the objects of a given type under all the management hosts of a plug-in. The same findAll method is also called when programmatically calling Server.findAllForType([Type]) in a vRO scriptable task or action.

vRO Microsoft DNS inventory side by side with Microsoft DNS Manager inventory

The selected object is called a Finder object. The vRO workflow engine uses this object unique ID to carry it between the different steps of the workflow. Whenever you use this object as an input of scriptable task or action a plug-in method called findById is called. findById will get the object properties as a Scripting object so they can be used programmatically. So basically the object properties are reloaded every time the object is used as an input.

If you open the Orchestrator API explorer you can see it lists for each plug-in the finder and scripting objects. The finder object has text based properties listed to the end user in the input of the workflow, the scripting object can have more properties, non text based (JavaScript objects ) and also provide methods to act on this object.

Now you may wonder how the inventory and its hasChildrenInRelation(), findRelation(), findAll(), findById() methods are implemented.

In the case of a Java based plug-in :

  • The inventory is described in the VSO.XML file contained in the plug-in .dar file (a dar file is a zip file format you can extract).
  • The methods are implemented in Java. Part of the plug-in will consist in Java libraries used to interface with the management host API (for example HTTP libraries to interface REST APIs) or the library provided by the SDK provided by the vendor of the management solution.

There is another type of plug-ins called Dynamic Types.

  • The inventory is described in a vRO resource element in a JSON format that can be edited by workflows that are provided with the Dynamic Types plug-in or edited in an external editor by exporting and importing back the resource.
  • The methods are implemented as vRO workflows or actions. For example if you interface with a REST based API you can write an action leveraging the HTTP-REST plug-in to fetch the properties of the objects.

The difference between the Java plug-in and the Dynamic Types plug-in are:


Java Dynamic Types
Closed source (Java binary) Open source (Actions and workflows)
Scripting objects (Complex properties, methods) The scripting object equals the finder object so there are no complex properties or methods.
Can leverage Java libraries but then has dependencies on these Can leverage vRO JavaScript available via platform and plug-ins
Requires Java development skills Requires scripting skills


There are a lot of existing Java plug-in available from VMware and VMware partners from VMware web site individual product download pages or VMware Solution Exchange.

When there are no Orchestrator plug-in for a given technology there is the option to create your using the plug-in software development kit or Dynamic Types.


With this article I have demonstrated how vRealize Automation can be extended to manage the lifecycle of any service with XaaS and how it is leveraging vRealize Orchestrator plug-ins to do so.

For an in depth technical walk through on how I have created the Dynamic Types Microsoft DNS plug-in featured in the screenshots of this article please check this “How to create a Microsoft DNS Dynamic Types plug-in ?” article.

If you are interested by the Microsoft DNS Dynamic Types plug-in I have uploaded it on VMware Sample Exchange


vCenter Orchestrator Holiday Gifts


The vCenter Orchestrator gifts season started a few months ago with the general availability of vCO 5.5. The compelling release was announced just in time to share the vCO momentum at VMworld.  Along with the amazing new features introduced, VMware continues with a lot more presents.

This year the holiday magic brings to vCenter Orchestrator users several updates, product integrations and learning gadgets that make automation with vCO more powerful than ever.

1. VMware has just announced the GA of VMware vCloud Automation Center 6.0(vCAC 6.0). The extension and creation of XaaS is done using the vCAC Advanced Service Designer which allows you to seamlessly leverage any vCO workflow and convert it to a catalog item or day 2 operation, available as a service in the vCAC Self-service portal.

 2. vCO CLI is the code name of the new debugging extension which will not only facilitate all experienced vCenter Orchestrator users and also helps the newcomers to programmatically explore the rich vCO ecosystem through interactive command shell. Access to the vCO plug-in’s inventory is integrated into the tool UI for easy navigation to the integrated solution objects.

3. Our super powerful and generic HTTT- REST and SOAP plug-ins are now able to support proxy configurations and assure security compliance of your automated solutions.

4. The long awaited vCO Powershell plug-in 1.0.3 is updated to support Powershell 3.0 inventory and is fully backward compatible with your existing scripts.

5. In vCenter Orchestrator plug-in for Microsoft Active Directory 1.0.4 the old configuration mode is removed and you are now able to configure the plug-in automatically through native vCO workflows.

For additional information on these materials, please visit the following sites:

The entire vCO team wishes you the very best for the holidays and 2014.


VMware vCenter Orchestrator 5.5 is now GA!

As part of the of the vSphere 5.5 announcement, we are extremely glad to share the general availability of vCenter Orchestrator 5.5 !

Large organization will greatly benefit from the enhanced cloud-scale architecture, out-of-the box high availability of the platform, and major improvements to the REST API.

Additionally, workflow developers can enjoy a more efficient development experience thanks to the new debugging and failure diagnostic capabilities in the vCenter Orchestrator client.

We continue enriching the vCO plug-in intelligences and number of integrations with variety of partner applications, including management systems from EMC, F5 Networks and NetApp. Please, refer to the VMware Solution Exchange for a complete listing of the available vCenter Orchestrator plug-ins.

 Optimized for growing clouds

vCenter Orchestrator 5.5 is greatly optimized for growing clouds thanks to significant improvements in scalability and high availability. The cluster mode configuration enables a collection of vCO orchestration nodes to work together, sharing a common database and provides high availability of the workflow execution in case of orchestration node failure. In addition, our extended REST API allows automatic installation and configuration of the necessary vCO server nodes. It also provides dynamic scale-up and scale-down of the orchestration capacity when vCenter Orchestrator is being used in conjunction with an external load balancer.

Workflow Debugging

The vCenter Orchestrator 5.5 client is fully equipped with a workflow debugger, allowing vCO workflow developers to easily test and fix their custom workflows. In case you want to re-run an extensive workflow from a common point of failure, you are able to configure and resume the execution from the last failed state of the workflow.

Security Enhancements:

The vCenter Orchestrator 5.5 appliance contains a complete set of security improvements, including Operating System updates and security hardening script enhancements, which seamlessly secure your orchestration deployment and reduces the platform surface of vulnerability.

Last but not least, you’ll still be able to leverage all of the workflow you’ve already created in the previous release and be able to run them seamlessly in version 5.5.

These are just the major new capabilities but you’ll find plenty of additional enhancements that make the automation and integration of your software-defined datacenter easier than ever before. For a full list of new features and capabilities, please refer to the detailed overview or the release notes.

As a reminder, in 2013, we continued to integrate vCO with the products from VMware Cloud Suite. Cloud administrators are now able to establish a self-healing datacenter and automatically remediate any infrastructure failure by simply leveraging the vCenter Operations remediation workflow package.

Additionally, vCenter Orchestrator offers bi-directional integration with vCloud Automation Center (vCAC). vCO workflows can be coupled with resources managed by vCAC, either as part of the provisioning and decommissioning process, or as a Day-2 operation available in the  vCAC self service portal.

So don’t hesitate to try it today and let us know what you think via blog comments, Twitter (#vCO) or the vCO Community.


The vCO Team

vCenter Orchestrator 5.1 Update 1 Released

Voila! vCenter Orchestrator 5.1. Update 1 Is Now Available!

This is not just an ordinary update release.  vCO 5.1.1 actually incorporates significant enhancement around built-in plug-ins and the vCO platform itself.

Please, take your time and read throughout the outlines below to find out more about this compelling release.

vCenter Server configuration

Yes, it is true: tedious manual configuration of vCenter Server is no longer required when you use vCO 5.1.1.  The new release provides out-of–the box workflows that automate the configuration of vCenter Server instances, thereby allowing you to dynamically provision vCenter Server capacity  in your datacenter.

Notifications, notifications, … and more notifications

Sending and receiving e-mail notifications have always been an important part of most automation processes.  In addition to POP, vCO now provides out-of-the-box support for the IMAP protocol. And triggering notification or notification-based workflows have never been easier thanks to significant improvements in available scripting methods.  The E-mail plug-in has been extended with several new scripting objects that can be used either with the IMAP or POP client for:

  • Retrieving messages
  • Reading details of the retrieved messages as well as file attachments
  • Searching messages
  • Deleting messages

Fine-tuning and fixes

When it comes to workflow development, we all know that the sum of little things is what adds up to a great experience.  With that in mind, we’ve included quite a number of changes and fixes that we trust will go a long way to improving your experience:

  • The zooming feature in the workflow schema has been enhanced so that it re-centers on the selected element(s).  It is now available in the contextual element menu and as a shortcut.
  • Copy and paste is the key to productive workflow development. vCO 5.1.1 is enhanced not to miss any of the properties of your workflow activity element during the copy paste process.
  • Take a deep breath and relax – no more issues with JSON.  vCenter Orchestrator 5.1.1 introduces a new JSON format that can be used by providing the Accept: application/json;v=5.1.1 header

For a complete list of all fixes, please be sure to read through the vCO 5.1.1 release notes and documentation listed below.

VMware vCenter Orchestrator 5.1.1 Download Landing Page:




Documentation Landing Page:


Release notes:


VMware Releases vCenter Orchestrator Gifts in Time for the Holidays

As 2012 comes to a close, we thought it would be a great time to end the year with some gifts to put under your (virtual) holiday tree!

2012 was a great year for automation in general, with the launch of the vCloud Suite 5.1, and orchestration in particular, with the release of vCenter Orchestrator 5.1.  Our team was extremely happy to see a tremendous increase in vCO adoption, and a growing list of integrations with other management systems.

In that spirit, we are very glad to announce the availability of several integrations and learning tools to make your automation projects easier than ever before.

1. vCloud Automation Center 5.1, which was just released, provides the ability to extend pre-built processes and post-provisioning actions by invoking vCO workflows. This means that any technical integration or logic built in vCO can be leveraged by vCAC’s lifecycle-management platform, thereby broadening the realm of self-service provisioning and basic administration for consumers of IT services.

2. Reversely, the new vCenter Orchestrator Plug-in for VMware vCloud Automation Center allows organizations to automate vCAC provisioning and post-provisioning tasks. With these two components, customers can leverage full bi-directional integration capabilities between vCloud Automation Center and vCenter Orchestrator.

3. Another new offering is the vCenter Orchestrator Elastic Service Plug-in. This plug-in provides a foundation for the self-scaling virtual datacenter, by automatically balancing the physical resources between virtual datacenters in VMware vCloud environments. This plug-in contains a rules engine that can analyze resource usage metrics (for instance, metrics captured by vCenter Operations Manager) and make scale-up or scale-down decisions automatically.

4. The vCenter Orchestrator Plug-in for VMware Service Manager enables organizations to automate operations around Configuration, Incident, Task and Service Request management.  Thanks to this plug-in, repetitive tasks such as updating an Incident or creating a Configuration Item when a new virtual machine is provisioned can now be fully automated.

5. And to help you take advantage of all of the above gifts, the VMware Training department just released over 10 self-paced vCO training videos available for free!

For additional information on these materials, please visit the following sites:


The entire vCO team wishes you the very best for the holidays and 2013.


Important vCenter Orchestrator Plug-in Updates

With the recent vCenter Orchestrator 5.1 and vSphere 5.1 availability, it’s obviously important to ensure that not just individual products but all of your integrations are up-to-date.

Besides the already released plug-ins for vCenter Server 5.1 (built-in) and vCloud Director 5.1, we are are glad to announce the availability of several plug-in updates to make your entire vCloud suite up-to-date:

1. The vCenter Update Manager plug-in has been updated to support version 5.1 and vCenter Single Sign On. This plug-in is essential for scanning and remediating vSphere inventory objects against baselines.

2. The vCO Multi-Node plug-in has been updated to support vCO 5.1, vCenter Single Sign On, and the new vCO REST API capabilities to leverage the remote invocation of new systems types such as actions and packages.  What’s more, this new version also provides better performance and corrects some previous defects.

3. The vCO Plug-in for vSphere Auto Deploy 5.1 supports… vSphere Auto Deploy 5.1!  Need we say more?

4. The vCO Plug-in for Microsoft Active Directory 1.0.2 provides support for vCenter Single Sign On and contains an import fix for concurrent workflow execution.

5. The vCO AMQP Plug-in 1.0.2 offers significant performance improvements and fixes a known issue with the vCO server restart.

6. The vCO Plug-in for vCenter Server 5.0.2 contains important performance improvements for customers who are running vCO with vCenter Server 5.0.

  • vCO Plug-in for vCenter Update Manager 5.1: download
  • vCO Multi-Node Plug-in for 5.1: download
  • vCO Plug-in for vSphere Auto Deploy 5.1: download
  • vCO Plug-in for Microsoft Active Directory 1.0.2: download
  • vCO AMQP Plug-in 1.0.2: download
  • vCO Plug-in for vCenter Server 5.0.2: download

As always, be sure to check VMware Solution Exchange for a complete list of plug-ins available from VMware and our partners.  That’s your best place to find the latest integration solutions such as the ServiceNow plug-in recently published by InterraIT.


The vCO Team

Auto Deploy plug-in


The Auto Deploy plug-in allows simplified and automated provisioning of physical hosts with ESXi software by interacting with Auto Deploy server. The user is able to browse rules and rule sets defined within the Auto Deploy server, configured public depots and all available host profiles within the vCenter Server that can be used. The plug-in provides a set of pre-defined workflows for Auto Deploy hosts configuration, public depots configuration, rules management, answer files management and reprovisioning of ESXi hosts.

Using Auto Deploy plug-in together with vCenter Server plug-in users can benefit from pre-defines workflows by decreasing the effort and time of provisioning and reprovisioning of stateless hosts with ESXi software.


  • Configured Auto Deploy server registered to a specific vCenter Server must be available.
  • Make sure that the network where the vCO, Auto Deploy server and public depots reside allows enough bandwidth to transfer large amount of data (ESXi software packages).
  • It may take some time to complete some workflows like creating, modifying rules or reprovisioning of ESXi hosts with image profiles that have not been used at least once. The second time an image profile is used will go much faster as the the software packages from the depots will be cached by the Auto Deploy server.
  • Make sure that Auto Deploy server is configured to reuse connections:


On the Linux version you need to change the following properties in the /etc/vmware-rbd/httpd/conf/httpd.conf file and restart Auto Delpoy server:

  1. KeepAlive = On
  2. MaxKeepAliveRequest = 0
  3. KeepAliveTimeout = 300 (or more)


Depot configuration

Only online depots are supported currently which means that depots should be accessible through a URL. The plug-in provides workflows for configuring access to such public depots so that later they can be used during the process of provisioning and reprovisioning of stateless hosts.


After completion of the 'Add a depot' workflow the depot will be added to the Inventory.


Auto Deploy host configuration

The plug-in provides a way of configuring Auto Deploy hosts by simply pointing to the associated vCenter Server host. The plug-in will automatically discover the registered Auto Deploy server (if available) and it will appear in the plug-in's inventory.


After completion of the 'Add an Auto Deploy host' workflow the Auto Deploy host will be added to the Inventory.


Rule management

Actually the way Auto Deploy works is via rule management on Auto Deploy server. The plug-in provides an easy way for creating, modifying or activating rules within the rule engine of Auto Deploy server. There are also predefined workflows for retrieving rules that impact a specific host and workflows for testing and repairing the rule set compliance.


Host profiles and answer files

The plug-in provides a way for managing answer file corresponding to a certain host profile using a XML format. The user should know the actual keys of the parameters in order to modify specific values from the answer files for a specific host.

In case the host doesn't have an answer file, a simple XML template will be presented so that the user can fill the empty placeholders with real values and modify the XML content. In case an answer file already exists for the particular host it will be displayed and ready for edition. The user can also provide a XML content as an already prepared XML file. Answer files will be saved and later used when a host profile with user interactions is applied on the specific host.


Provision an ESXi host

In order to provision a stateless ESXi host for the first time the host must be configured to perform PXE boot. Provided that Auto Deploy server and infrastructure environment has been configured properly the following additional steps must be performed:

  1. Create a deploy rule that impacts the target ESXi host.
  2. Activate the new created rule so that the rule engine evaluates the rule when receiving requests from the target ESXi host.
  3. Reboot the ESXi host to initiate the boot process.

Create rule

Use the workflow 'Create a deploy rule' to create a new rule. It won't be active.


Select an image profile from the already configured depots:


Optionally, select a datacenter, host folder or cluster within the vCenter Server inventory where the ESXi host will be registered:


After clicking of Submit button the process of creating the new rule will start. If the image profile is used for the first time it may take some time to finish the workflow. Of course later, if the same image profile is used again in some other workflow it will finish much faster. After successful completion of the workflow the new rule will be shown in the plug-in's inventory.


The next step is to activate the rule using the workflow 'Activate a deploy rule and a working set' so that it becomes active. Actually the rule will be added to the working rule set first and then the whole working rule set will be activated. It is not possible just to activate a single rule. This means that all rules in the order they are placed in the working rule set will be added to the active rule set.


After activation the rule is added both to the working and active rule set. It becomes non-editable and from now on it is evaluated by the rule engine on requests from the ESXi hosts. If you want to modify already activated or non-editable rule you must use 'Copy a deploy rule' workflow which actually hides the original rule and replaces it with completely new one.


After rebooting the ESXi host it will perform PXE boot and Auto Deploy server will provision it with the software images defined by the created rule. As we set also a vCenter Server location in the rule, the ESXi host will be registered in the specified host folder after booting.



Reprovision an ESXi host with a new image

This use case shows a simple use case when by modifying a single rule the ESXi host can be provisioned with a new software images (virtual infrastructure bundles). There are predefined workflows for reprovision ESXi hosts with new image, answer files and a new location. All of them assume that a modification on single rule is needed. Use the workflow 'Reprovision a host with a new image' to reprovision ESXi host with a new image.


If the image profile is used for the first time the workflow will take more time to complete. The workflow will reboot the ESXi host automatically and the host will load the new specified image:



The Auto Deploy plug-in provides basic building blocks as workflows and actions for interacting with Auto Deploy server and managing stateless ESXi hosts. The workflows can be used 'out of the box' or custom high level workflows can be composed according to the real use cases in order to automate  and greatly decrease the time and effort to provision and reprovision stateless ESXi hosts.


More info about VMware vCenter Orchestrator Plug-In for vSphere Auto Deploy: release notesdocumentation and download


VMware Releases Four New VMware vCenter Orchestrator Plug-ins!

As 2011 comes to an end and the holidays approach quickly… it just felt right to thank the fast-growing vCO user community with a set of new shiny toys.  Not to mention that, like people with children know all too well, we've heard these requests over and over again throughout the year… 😉

So on this holiday note, we are extremely pleased to release four new plug-ins that should help you achieve your 2012 cloud automation resolutions!

1. The first one is the VMware vCenter Orchestrator SQL Plug-In.  Who hasn't had a need to automate operations on database tables and records?  Well, now you can do so without actually having to write any SQL statements.

2. The second is the VMware vCenter Orchestrator Plug-In for vSphere Auto Deploy.  Considering the move to a stateless ESXi architecture?  If so then this plug-in is definitely for you. 

3. Third is the vCenter Orchestrator Multi-Node Plug-In.  As you increase the scale or geographical reach of your automation solutions, you may need to deploy more vCO server instances.  In that case, this new plug-in makes it a lot easier to manage several vCO instances from a single point.

4. And last but not least… is the vCenter Orchestrator Plug-In for Microsoft Windows PowerShell!  It lets you leverage your existing PowerShell and PowerCLI scripts and opens up so many new capabilities… that we'll need several postings to tell you all about it 😉   So be on the lookout for additional articles on this topic very soon.  In the meantime, we obviously encourage you to take it for a first spin.

For additional information on these new plug-ins and to download them, please visit the following sites:

We hope that these new plug-ins will keep you occupied during the holidays.  Seriously, we'd actually prefer that everyone took a well-deserved break, but we know how hard it is not to play with new technology 😉

So on this note, the entire vCO team wishes you the very best for the holidays and 2012.


PS.  As always, you can find documentation on vCO and all available plug-ins on the vCO Documentation site.


SNMP plug-in – integration with vCenter Server

In this post we will show how you can use the SNMP plug-in to receive various vCenter Server alarms in vCO and include these events as part of more complex orchestration logic.

vCenter Server configuration

First, you must register the vCO server in the list of SNMP trap receivers in vCenter Server. This list is accessible in the vSphere client, in vCenter Server Settings, which is accessible from the Administration menu.


You can have up to four different receivers, one of which must link to the address of your vCO server and the port defined in the Trap Host node in the SNMP inventory in vCO.

Configure Alarms

After you have registered the vCO server, vCenter Server can send SNMP traps to it. Some traps will start to be sent immediately. Many alarms in vCenter Server are configured to send traps by default.

Some default alarms are defined on the root of the vCenter Server inventory (1), from where they propagate to all child objects. If you go to the Alarm management tab (2), you can check the definitions (3) of the default alarms. Selecting a specific alarm (4), you can check on its Actions tab (5) if sending SNMP traps is active for this specific alarm (6).


These settings can be changed on the object where the alarm is defined. If the fields are not editable, then this is an inherited alarm, and you need to find the parent object that defines the alarm to change the settings.

Create custom alarms

Sometimes you may need to monitor something specific that is not part of the default alarms, or you only want to monitor it for a certain host, virtual machine or other object. Then you need to add a custom alarm to the object (a datastore in this example).


Then, you need to add some triggers which define under what conditions this alarm should be triggered.


Finally, you need to add an action that will send a trap. Note that you may need to add handlers to state changes. For example, the green to yellow state change does not send a trap, as by default only the yellow to red state change is defined to send a trap.


After this, the vCenter Server instance is ready and is sending traps to vCO.

Configure vCO to receive traps

On the receiving end, you first need to add the vCenter Server instance to your inventory with the “Register an SNMP device” workflow.


Then you can either apply a policy, which will be receiving all kinds of traps and running scripts on each of them, or start a workflow, which will be waiting for a specific trap.

The policy is applied from the Policy Template “SNMP Trap”, and takes as a parameter the SNMP device that you just registered.


This exact policy is only printing the trap data to the system log, but it could do other tasks, such as, call actions or workflows that should handle the received traps.

You must start the policy after it is created, or set it to auto-start if you need it to work after server restart.

You can leave this policy to be listening for traps for the moment, and check the other possibility to receive traps – the “Wait for a trap on an SNMP device” workflow.


After you enter the device and OID parameters and run the workflow it reaches a trigger where it suspends and starts waiting. It can be resumed only by the specified SNMP trap.


If the OID field from the workflow presentation was left empty, then the workflow will be resumed by any trap, just like the the policy. Any trap filtering on the policy must be done programatically, after the trap is received. Listening to all incoming traps can help you easily get the correct OID that will be sent from vCenter Server for a specific alarm. These OIDs are also listed in the MIBs that are described in vSphere Datacenter Administration Guide, in the “Monitoring Your Virtual Infrastructure” section, chapter “SNMP and vSphere”.

If everything is configured correctly, vCO should start receiving SNMP traps and trap data will be logged from the policy, like in this example, which is monitoring datastore space usage.


The SNMP plug-in is not limited only to use with vCenter Server. It can be used with any SNMP-enabled system or device. This is just one scenario that shows how the SNMP plug-in, together with the workflow library from the vCenter Server plug-in, can be used as the basis for the automation of various datacenter administration tasks.

vCenter Orchestrator Plug-in for Microsoft Active Directory now released

We are extremely pleased to announce the General Availability of 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 around computers, organizations, user groups and users, such as resetting passwords or adding users to a user group.

What versions of Active Directory are supported?

  • 2003
  • 2008

What versions of vCenter Orchestrator are supported?

The plug-in runs on VMware vCenter Orchestrator 4.1.x.

How many workflows and actions are there?

  • Total number of Actions = 14
  • Total number of Workflows = 32

What can the users do with the Active Directory Plug-in 1.0.0?

  • Browse Users, Computers, Groups and Organizational Units in an Active Directory multi-domain forest
  • Run pre-defined workflows like creation of Users, changing user Passwords and a lot more.
  • Create new custom actions and workflows that serve better to their scenarios.

Where can I find more details about the Active Directory Plug-in 1.0.0?
Below are some resources to help you better understand the value and scope of the Microsoft Active Directory plug-in: