Month December 2013

This toolkit contains fifteen downloadable tools to help you manage and troubleshoot Microsoft System Center 2012 R2 Configuration Manager.

The Microsoft System Center 2012 R2 Configuration Manager Toolkit contains fifteen downloadable tools to help you manage and troubleshoot Microsoft System Center 2012 R2 Configuration Manager. The following list provides specific information about each tool in the toolkit.

Note:

Items with an * are new in the R2 Toolkit and require Microsoft System Center 2012 R2 Configuration Manager for full functionality.

I was working on a new management pack for Tivoli Storage Manager. I want to discover the nodes from the TSM server via an administrative console. Unfortunately you have to login in that console to get the info out TSM. I have made a Powershell script that is using the console to export a list of nodes with some information to a text file. After the export the script imports the text file as CSV and put the information into SCOM for making it as discovered objects.

The best and nicest thing to do is using the credentials via a Run As Profile, not hard coded in the script. This is not handy and it’s wrong. What happens if the user not exist anymore or the password has expired. You don’t want to edit the management pack for only to change the username and password. The perfect why to do that is to use the Run As Profiles via SCOM console.

After some resourcing I have found a solution to use Run As Profile in the script. This means you have to make a Run As Profile for your management pack and use the Parameters(if you are using Powershell) in the Probe action.

Let’s see. First you have to make a Run As Profile in Authoring Console. This is located in Health Model\Secure References. You need the ID later for your Probe action configscript. Give it a nice name, because you will see that later in the SCOM console.

Go to your Powershell Script in Probe Module and add these parameters at the end of the configuration. Between </SCRIPTBODY> and <TIMEOUT>

<Parameter>

<Name>TSMuser</Name>

<Value>$RunAs[Name=”TEST.CST.TSM.ADMIN.RUNAS”]/UserName$</Value>

</Parameter>

<Parameter>

<Name>TSMpass</Name>

<Value>$RunAs[Name=”TEST.CST.TSM.ADMIN.RUNAS”]/Password$</Value>

</Parameter>

</Parameters>

Change it to your ID. With param you can use the parameters in the script.

Import the management pack in SCOM and go to administration. You have to make a Run As Account. This can only in SCOM and not in Authoring Console. If you are done with making an account, go to Run As Profile. Open the Profile and add the account you just created.

So, after this your are done and the script use the credentials from SCOM instead hard coded in the script 😉