HackTheMind LLC is up and running, but I have not had the time to work on the site.

I am also starting an online toy and game store with www.htmgames.com .

Take care.

I got laid off from the place that used SCOM and Power Shell, and now work for a company that uses *nix servers. Unfortunately, this has brought about a “use it or lose it” scenario. My PowerShell skills have diminished.

This will be changing though. I have a few projects I am working on for HackTheMind, LLC. that will require PowerShell, and as I get them completed, I will post writeups on them.

Take care, and keep scripting.

I will not go into the long boring details, instead, I will just paste the email I sent which has more then enough information.

——————————————————————————————

http://www.bozeman.net/bozeman/humanResource/forms.aspx

The part that has the form in question:

Consent and Release to Conduct a Criminal Background Check (Notarized Version)

Only under a couple days ago did I get confirmation that even people in the Software Asurance Program wouldn’t get R2 proper until the 1st of July. Bleh.

You can download it here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=93ddf25b-1ef0-4851-81b0-5fb9a2f76181&displaylang=en

YAY!

#==============================================================================================
# End of Main Script Body

Notes will be comming soon.

So, I tweaked a script I found long ago and then made it work in Powershell V1 (with help from #powershell user JasonMArcher). I would give credit to the original author, but I don’t remember who it was. (aka, if you are reading this, please let me know so I can give proper credit.)

$erroractionpreference = "Continue"

$a = New-Object -comobject Excel.Application
$a.visible = $True

$b = $a.Workbooks.Add()
$c = $b.Worksheets.Item(1)

$c.Cells.Item(1,1) = "Machine Name"
$c.Cells.Item(1,2) = "File Name"
$c.Cells.Item(1,3) = "Version"
$c.Cells.Item(1,4) = "Report Time Stamp"

$d = $c.UsedRange
$d.Interior.ColorIndex = 19
$d.Font.ColorIndex = 11
$d.Font.Bold = $True

$intRow = 2

$colComputers = get-content E:\SCOMScripts\patching\Servers.txt

foreach ($strComputer in $colComputers)
{
$c.Cells.Item($intRow,1) = $strComputer

Function GetFileInfo
{

$Path = "\\"+ $strComputer + "\C$\Program Files\System Center Operations Manager 2007\MOMModules.dll"

$File = get-item $Path

$c.Cells.Item($intRow,2) = $File.Name
$c.Cells.Item($intRow,3) = [System.Diagnostics.FileVersionInfo]::GetVersionInfo($Path).ProductVersion
}

GetFileInfo

$c.Cells.Item($intRow,4) = Get-date
$intRow = $intRow + 1
}

$d.EntireColumn.AutoFit()

I did some modifications and here is another version that get’s the machine names from SCOM. This has to be ran from the Operations Manager Console.

$erroractionpreference = "Continue"

$a = New-Object -comobject Excel.Application
$a.visible = $True

$b = $a.Workbooks.Add()
$c = $b.Worksheets.Item(1)

$c.Cells.Item(1,1) = "Machine Name"
$c.Cells.Item(1,2) = "File Name"
$c.Cells.Item(1,3) = "Version"
$c.Cells.Item(1,4) = "Report Time Stamp"
$c.Cells.Item(1,5) = "Reporting Node"

$d = $c.UsedRange
$d.Interior.ColorIndex = 19
$d.Font.ColorIndex = 11
$d.Font.Bold = $True

$intRow = 2

$colComputers = get-agent

foreach ($strComputer in $colComputers)
{
$c.Cells.Item($intRow,1) = $strComputer.ComputerName

Function GetFileInfo
{

$Path = "\\"+ $strComputer.ComputerName.ToString() + "\C$\Program Files\System Center Operations Manager 2007\MOMModules.dll"

$File = $Path

$c.Cells.Item($intRow,2) = $File
$c.Cells.Item($intRow,3) = [System.Diagnostics.FileVersionInfo]::GetVersionInfo($Path).ProductVersion
}

GetFileInfo

$c.Cells.Item($intRow,4) = Get-date
$c.Cells.Item($intRow,5) =  $strComputer.PrimaryManagementServerName
$intRow = $intRow + 1
}

$d.EntireColumn.AutoFit()

Only you can’t seem to find it because your SCOM UI locks up and crashes when you try to have full scope to find it? Ohh yeah.

Then this one line is for you.


((get-rule | ? {$_.DisplayName -like "*RuleName*"}).getmanagementpack()).displayname


That’s all it takes. Just change where is says *Rule Name* to match the name, or part of the name your rule has, and hit enter. It will output the MP it’s in.

Have fun.

After looking at it a moment, it dawned on me of a way to have server lists that one can use for automation.

Let us say you have a XML file like the following:

<?xml version=”1.0″ encoding=”utf-16″ ?>
<Objs Version=”1.1.0.1″ xmlns=”http://schemas.microsoft.com/powershell/2004/04″>
   <DataCenter1>
       <FrontEnd>
           <Servers>webserver1</Servers>
           <Servers>webserver2</Servers>
          <Servers>webserver3</Servers>
      </FrontEnd>
      <BackEnd>
          <Servers>datalayer1</Servers>
          <Servers>datalayer2</Servers>
      </BackEnd>
   </DataCenter1>
</Objs>

This is a very simple XML file, that one might use to tell the difference between the front end systems and the back end systems in a datacenter.

Now, how would you load this into powershell?
PS C:\Powershell> [xml]$Servers = gc .\servers.xml
Once that is done, you can now grab things from the XML loaded into $Servers.
PS C:\Powershell> $Servers.Objs.DataCenter1.FrontEnd.Servers
webserver1
webserver2
webserver3
As you can see, this gave me the list of servers under the FrontEnd element.

So to use this, in a foreach loop for example, just do the following foreach.
foreach($Server in $Servers.Objs.DataCenter1.FrontEnd.Servers)
{
Write-Host "$Server is a Front End Server."
}
foreach($Server in $Servers.Objs.DataCenter1.BackEnd.Servers)
{
Write-Host "$Server is a Back End Server."
}
This will give you the following.
webserver1 is a Front End Server.
webserver2 is a Front End Server.
webserver3 is a Front End Server.
datalayer1 is a Back End Server.
datalayer2 is a Back End Server.
Very basic XML usage, but it was enough to give my co-worker a running start.

Later