Monthly Archives: February 2015

Automation, BlueStripe, Integration, Savision

SCOM | BlueStripe | Live Maps Integration

1 Comment

Last year I helped a customer integrate System Center Operations Manager 2012, BlueStripe (FactFinder), and Savision Live Maps. Contact me if your company is planning to integrate these products – there are several things to consider to get the most out of this integration and make it a huge success.

I developed an enhanced integration pack that was integral in the success of this project. Read more in this case study written by BlueStripe:

https://bluestripe.com/case-studies/sap-application-performance-major-utility-keeps-sap-working/

(I am not affiliated with BlueStripe or Savision. I consulted on this project through SCOMskills.)

 

Smile

Administrative Tasks, Powershell

Operations Shell–Using different credentials

Leave a comment

Some companies setup their user accounts and then provide an administrator account, and maybe only the administrator account is a member of the Operations Manager Administrator user role. The Operations Console provides a login screen, so it’s not a problem authenticating to the management group. But the Operations Shell does not provide a login option – it will automatically attempt to login using the context of the current user.

This results in an access denied message:

New-SCOMManagementGroupConnection : The user does not have sufficient permission to perform the operation.

 

One way to get around this is to use the Powershell Get-Credential cmdlet. Add this to the beginning of administrative scripts or start your console sessions with:

 

$Credentials = Get-Credential –UserName [domain\username] -Message "Enter password"

$MS = [your management server name]

New-SCOMManagementGroupConnection -ComputerName $MS -Credential $Credentials

 

Smile

Administrative Tasks, Installation

Report Server – The underlying connection was closed

1 Comment

I ran into an issue while helping a customer install reporting services. I haven’t seen this problem before, so thought it might be helpful to share with the community.

After installing SQL Reporting Services 2012, and choosing to automatically configure the default instance during the setup process, the main SRS page displayed an error:

“The underlying connection was closed. Could not establish trust relationship for the ssl/tls secure channel.”

image

Choosing to have the SQL installation wizard to configure SRS automatically has always resulted in success for me until now, so this was a bit disconcerting. Long story short, the issue was fixed by updating the rsreportserver.xml config file SecureConnectionLevel value from 2 to 0. I don’t know why the wizard set this value to 2, assuming SSL would be used, but explicitly disabling this solved the problem in this case.

Additionally, when installing the SCOM Report Server role, the wizard failed after selecting the SRS instance. Removing the SSL bindings completely in the Reporting Services Configuration Management tool solved that problem as well.

 

Smile