Gathering alerts from multiple UCS pods using Powertool

We wanted a script to automate the gathering of UCS alerts from all the pods in our environment. After installing the Cisco Powertool plugin, I created the following:


$podcsv = import-csv .\UCS_Pods.csv
$credcsv = import-csv .\UCS_Credentials.csv
$ucsuser = $credcsv.username
$ucspasswd = $credcsv.password
$secpasswd = convertto-securestring $ucspasswd -asplaintext -force
$ucscreds = new-object ($ucsuser,$secpasswd)
$datetime = get-date -uformat “%C%y%m%d-%H%M”

foreach($pod in $podcsv)
connect-ucs -credential $ucscreds $podip
get-ucsfault | select ucs,id,lasttransition,descr,ack,severity | export-csv -path .\$datetime-$podname-errors.csv


You will need to place a list of the pods, and their management IPs in a CSV (named UCS_Pods.csv) in the following format:



And the credentials for a user account to login in a CSV (named UCS_Credentials.csv) in the following format:



The account you use to connect should ideally be created as a standalone read only account on each UCS system.

Configuring SSRS for Kerberos authentication

Had an issue with Kerberos passthrough authentication not working with SSRS. The following ended up resolving this:

1) Configure SPNs on the Service Account running SQL/SSRS for: 
  a. MSSQLSvc\<NETBIOS and FQDN>:1433 
  b. MSSQLSvc\<NETBIOS and FQDN>:<InstanceName> (where multiple instances exist on a server) 
  c. MSSQLSvc\<NETBIOS and FQDN>:<InstancePort> (where multiple instances exist on a server) 
  d. HTTP\\<NETBIOS and FQDN> (for SSRS servers) 
2) Select ‘Trust this computer for delegation to any service (Kerberos only)’ for SSRS servers 
3) Select ‘Trust this account for delegation to any service (Kerberos only)’ for SVC_MSSQL service account 
4) Amend reportserver.config file to force Kerberos rather than NTLM 

There are numerous Technet articles on this although all seem to be somewhat theoretical, or specific around certain infrastructure topologies.

Regenerating self-signed Keyring certificates in UCS

This site details how to regenerate a self-signed Keyring certificate in UCS:

I ran this on a UCS pod which was on v2.1(2a) in order to clear an alarm showing in UCS Manager, after the regeneration, the cert status was showing as unknown when running the ‘show keyring detail’ CLI command. This was not what I was expecting.

Turns out that this is a bug with v2.1.2(a), it has since been fixed in v2.1(2c) (patch notes:

Exchange 2010 – Finding all mail older than a certain date in a given mailbox

I was looking around for how to do this, ended up throwing together a few sources and putting this together:

[PS] C:\Windows\system32>Get-Mailbox "username" | New-MailboxSearch -Name search123 -SearchQuery "Received:<01/01/2014" -estimateonly
[PS] C:\Windows\system32>Get-MailboxSearch search123 | Start-MailboxSearch
[PS] C:\Windows\system32>Get-MailboxSearch search123 | ft name,status,percentcomplete,resultnumberestimate,resultsizeest
 imate -auto
Name Status PercentComplete ResultNumberEstimate ResultSizeEstimate
---- ------ --------------- -------------------- ------------------
search123 EstimateSucceeded 100 97515 26.91 GB (28,894,471,176 bytes)

This could then be used with a Retention Policy to see how much mail we had left to archive.