Task Name
This workflow extracts the domain to be joined later in order to pre-provision the FQDN in AD. | |
| Description | |
| Prerequisites | Tested on UCSD 6.0.1.0 and 6.1 |
| Category | Workflow |
| Components | vSphere 5.x and HyperV |
| User Inputs | CatalogID and VDC_ID |
| Output | SPDomainName |
Instructions for Regular Workflow Use:
- Download the attached .ZIP file below to your computer. *Remember the location of the saved file on your computer.
- Unzip the file on your computer. Should end up with a .WFD file.
- Log in to UCS Director as a user that has "system-admin" privileges.
- Navigate to "Policies-->Orchestration" and click on "Import".
- Click "Browse" and navigate to the location on your computer where the .WFD file resides. Choose the .WFD file and click "Open".
- Click "Upload" and then "OK" once the file upload is completed. Then click "Next".
- Click the "Select" button next to "Import Workflows". Click the "Check All" button to check all checkboxes and then the "Select" button.
- Click "Submit".
- A new folder should appear in "Policies-->Orchestration" that contains the imported workflow. You will now need to update the included tasks with information about the specific environment.
I want to give credit to Orf Gelbrich and his expertise and all the help he and Russ Whittier gave me to complete this!
User Need: Had to find out what domain the category VM would be joining into PRIOR to VM deployment. They were pre-creating the computer entry in AD using PowerShell to alleviate the need for reboot etc. when the VM actually joined.
Solve: What I thought would be an easy task, turned into a myriad of procedures and methods! I had to use API calls, XML parsing, Cloupia scripting, Tabular Report gleaning, etc. etc. The output of this workflow (Could be saved as a compound task) is just the Domain Name or Workgroup the VM will be joining when provisioned. With a little tweaking, what information element from which policy do you need?
Step 1: Get the Category ID
Step 2: Does the Category have an Application Category over ride Deployment Policy?
Step 3:a If override was in place, run a report to extract the Domain Name from the Policy.
Step 3:b If override was not in place, go to VDC to find the System Policy.
Step 3:c If no name was found in the Policy, It could be HyperV, Check that policy API for the data.
Step 3:d Need to parse the API returned XML data for the Domain name…
Step3:e Log the Domain Name in Red in the SR Log and set a workflow output with the Domain Name.
From 3:b Get the System Policy from the VDC
Repeat 3:a , 3:c , 3:d and 3:e
A picture is better:
Workflow:
