I'm trying to figure out how to apply changes to a service profile on a sub-org level. I notice that there is a type of Cisco.Ucs.OrgOrg and that the Get-UcsServiceProfile Cmdlet has a parameter of "-Org". However, I don't know how to use the Cisco.Ucs.OrgOrg type.
Do I need to typecast a string containing the desired sub-org name to type Cisco.Ucs.OrgOrg? If so, how? Any details regarding changes on a sub-org level would be appreciated. I know documentation on PowerTool thus far is scarce as it is, but I can't find ANYTHING about this particular item.
Thanks!

Thanks, that helps me understand a little more.
 
I will further clarify my specific needs - there are no nested suborgs, other than what's nested within "root". There are, however, several suborgs at that level and I want to limit my changes to only specific sub-organizations for "layer 8" reasons. As a result, I need my script to not only limit changes to the suborg specified, but allow the user of the script to select it from a list at runtime for ease of use.
 
As a result, I used the following snippet to populate a string array to present these to the user.
 
echo 'Getting organizational units from system...'
foreach ($thisOrg in Get-UcsOrg | Select Name | Out-String)
{
    $UcsOrgs += $thisOrg.ToString()
}

 
I then created a new var to hold the Org object (non-string) and referred to it in my statement to power on service profiles:
 
#This is where I will later build in the ability to choose an org from the list. For now, I'm simply hard coding as string.
$targetedOrgString = 'ORG-A'

echo "Powering on all Service Profiles in $targetedOrgString ..."

$targetedOrg = Get-UcsOrg -Name $targetedOrgString
Get-UcsServiceProfile -Org $targetedOrg | Set-UcsServerPower -State admin-up -Force
 
Any issues with the above segments? Anything I can improve upon?

Wow....that's great! Thank you!
 
I was initially pretty discouraged when I discovered the relative lack of practical documentation, but if the forum is or will be anything like this, I'll do my best to contribute so we can get some mean PowerTool scripts going!

 
Fortunately, although my environment is large, it is not very complex. There are only a few sub-orgs off of the root (so far) so this script is more than sufficient. I did modify it a little to improve usability.

Matt:



If you upgrade to version 0.9.8.0 (available on CDN) we have added pathing support for powershell library locations to add the path to the Cisco UCS PowerTool psd1 (CiscoUcsPS.psd1) which is now located in C:\Program Files (x86)\Cisco\Cisco UCS PowerTool\Modules\CiscoUcsPS. After upgrade if you are still having issues, please let me know.



Thanks,

Eric



From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Wednesday, May 02, 2012 7:56 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Matt Oswalt in Unified Computing UCS Manager - Microsoft Discussions: RE: Applying changes to Service Profiles in a specific Sub-Organization



Matt Oswalt has created a new message in the forum "Microsoft Discussions":

--------------------------------------------------------------
I noticed you're using the following to "import" the UCS PowerTool module:

# Import the UCS PowerTool module
Import-Module CiscoUcsPs

When I run that I get this:


Import-Module : The specified module 'CiscoUcsPs' was not loaded because no valid module file was found in any module directory.

So instead of running that I have to use this:

cd 'C:\Program Files (x86)\Cisco\Cisco UCS PowerTool'
.\StartUcsPS.ps1

Any idea how I can get that to import the way you are?
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/unifiedcomputing/forums/-/message_boards/view_message/5547644>

or simply reply to this email.