<==Charvo==> cloud age is upon Us

In vSphere 6.0 U2, you can have an External PSC or an Embedded PSC. The below process is to add an External PSC to the Active Directory Domain. Login into the vCenter server, go to Administration tab, go to System Configuration –> Nodes and click on the PSC node you want to add to the domain. Click on the node, go to Manage tab, click on Active Directory and click on Join button Provide the Domain name and its credentials (It could be a read-only service account in the domain) to join the PSC to the domain once credentials are provided, click OK to proceed. Note that the only way for you to know that this process is complete is that you get no error and there is no entry in the recent tasks tab in the vSphere web client. If that is the case then the domain add is successful. Now, you will need to reboot the PSC Once the PSC is rebooted, you can go back into the vCenter server and to the node and you can see that this node (PSC) is now ad

How to Export and Import a Workflow Package in VMware vRealize Orchestrator Workflow packages are exactly what they sound like – a collection of workflows compressed into a package format that can be imported on one or more target servers.  Actually, they’re a little more than that: they also contain other components necessary for workflow dependencies such as actions, configuration elements, and resource elements. Workflow packages are a good tool for distribution and backup of workflows on a source (development) server.  Once a package is created and exported from the source server, it can be imported on a target server with ease.  Target servers could be test, staging, or production servers, or they could be customer servers, meaning workflow packages can be used to distribute software internally among an organization’s vRealize Orchestrator servers or external to an organization’s customers STEP 1: CREATE THE WORKFLOW To get started, we need to create an empty workflo

Create Your First vRealize Orchestrator Workflow - Hello World Before we begin creating our first workflow, let’s create a place to put it.  Follow these steps to create a new workflow folder: 1.        Change the view drop-down at the top of the Orchestrator client to Design. 2.        Click the blue Workflows tab (this tab should be selected by default, but ensure it is selected, and click it if necessary) 3.        Right-click the top-level node. This node is named according to the logged in user, for example “administrator @ server-fqdn” 4.        Click “Add Folder…” 5.        Enter the folder name “vRO Examples” 6.        Click OK Repeat these steps to create a folder underneath the vRO Examples folder named “First Workflow.”  Right-click the vRO Examples folder and click “Add Folder…” to create the folder at this level instead of the top level. Create the workflow by following these steps: 1.        Right-click the First Workflow folder 2.        Cl

Copying a File From a Resource Element to a Guest VM This workflow is useful as a utility workflow that can convert a file stored in a resource element into a file on a guest VM.  This is done first by saving the file from the resource element to the local file system of the vRealize Orchestrator appliance.  From there it is copied into a guest VM’s file system using the VMware Host Guest Filesystem (HGFS) interface of VM Tools.  In some secure environments this functionality may be blocked in the VMX settings of the virtual machine, so it is a good idea to check to make sure HGFS is not blocked before attempting to use this interface.  Assuming that using HGFS to copy files to the guest VM is not a problem, then this workflow serves as a good way to copy script files from resource elements to virtual machines.  A benefit of this approach is that network connectivity is not required from the vRealize Orchestrator instance to the guest VM, making it a better candidate than SSH in