cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1071
Views
0
Helpful
0
Comments
Orf Gelbrich
Cisco Employee
Cisco Employee
Task NamePower Shell Script example creating scripts with the @ symbol
Description
  1. Change the user of a running workflow
Prerequisites
  1. Tested on 5.3.1
CategoryWorkflow
ComponentsvSphere 5.x
User Inputs
  1. userid to change to
Output

Instructions for Regular Workflow Use:

  1. Download the attached .ZIP file below to your computer. *Remember the location of the saved file on your computer.
  2. Unzip the file on your computer. Should end up with a .WFD file.
  3. Log in to UCS Director as a user that has "system-admin" privileges.
  4. Navigate to "Policies-->Orchestration" and click on "Import".
  5. Click "Browse" and navigate to the location on your computer where the .WFD file resides. Choose the .WFD file and click "Open".
  6. Click "Upload" and then "OK" once the file upload is completed. Then click "Next".
  7. Click the "Select" button next to "Import Workflows". Click the "Check All" button to check all checkboxes and then the "Select" button.
  8. Click "Submit".
  9. 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.

A big thank you goes out to Joshua Barton for this inspiration:

How to create a power Shell script that spans multiple lines:

Example:

Screen Shot 2015-07-27 at 5.41.41 PM.png

Several things to note here...

The start @' has one tick which means expressions in single quoted strings are not evaluated

The \$a and \$b need to be escaped in order for UCSD not to evaluate the varaible

The ${VMName} is replaced before the script is shipped off to the Power Shell agent

The workflow:

Screen Shot 2015-07-27 at 5.41.30 PM.png

At run time the evaluation can be monitored

Screen Shot 2015-07-27 at 5.41.18 PM.png

The workflow generates 3 files.

File #1 (b) is created:

Screen Shot 2015-07-27 at 5.40.37 PM.png

File #1 (b) is then executed and produces 2 more files:

File #2

Screen Shot 2015-07-27 at 5.40.50 PM.png

File #3

Screen Shot 2015-07-27 at 5.41.01 PM.png

The workflow input:

Screen Shot 2015-07-27 at 5.42.09 PM.png

Workflow user input:

Screen Shot 2015-07-27 at 5.42.21 PM.png

The original inspiration:


Screen Shot 2015-07-27 at 5.42.43 PM.png

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links