In this multi-part blog post I am going to show you have I have fully automated the deployment of the GoToMeeting Client each time there is an update.

In Part 1 we are going to go build three Orchestrator runbooks

  1. the first runbook will monitor when the process should run
  2. the second runbook will be the main control runbook
  3. the third runbook will Unzip the zip file if there was an update downloaded with the runbook we will build in Part 2

Runbook 1
Continue reading

I recently had to rebuild my machine, after getting Windows 8 reinstalled I started installing my System Center Consoles since I was in a hurry to work on a powershell script for a runbook in Orchestrator that connected to ConfigMgr my first two consoles I installed were ConfigMgr and Orchestrator then went on to deploy the Integration packs for Orchestrator. Most of the IPs installed without any issues but the System Center 2012 ConfigMgr and OpsMgr IPs failed to install. The error message in the Deployment Manger was not very helpful. “Fatal error during installation.

Since I wasn’t sure where the log files were on the remote computer or what was the root cause of the issue fired up Process Monitor this quickly lead me to the log directory that can be found at
Continue reading

In my lab I have an issue where SQL doesn’t always start when my VM is rebooted this causes the SCOM services not to start up as well, in our production environment we every once in a while will have something happen that causes SQL to fail. So I created some runbooks that will monitor SQL and the SCOM services. If you are running more than one SCOM management server or running a SQL cluster you will need to create these runbooks for each server.

Monitor SQL Service – Runbook
Continue reading

I’m preparing to upgrade my SCSM environment to SP1 one of the Prerequisites is to stop the SCSM DW jobs. I decided that since this is a requirement to do every six months or so and I don’t want to relearn how to use them cmdlets every time. I always forget to use the –computer parameter and the powershell cmdlet fails. This also allows me to just export the two runbooks I created out of my lab environment and into production. The scripts below will figure out what your Extract jobs are called you just need to update the server name.

Create a new runbook for stopping the DW jobs and paste the following code into a Run .net Script

$SMModule
=
“C:PowershellModulesService ManagerPowershellSystem.Center.Service.Manager.psd1”

$SMDWModule
=
“C:PowershellModulesService ManagerMicrosoft.EnterpriseManagement.Warehouse.Cmdlets.psd1”

Import-Module
-force
$SMModule

Import-Module
-force
$SMDWModule

$SCDWJobs
= @(“Transform.Common”,“Load.common”)

$SCDWMGJobs
=
Get-SCDWJob
-computer
SCSMDW01
|
where {$_.Name -match
‘Extract*’}

foreach ($SCDWMGJob
in
$SCDWMGJobs){

Disable-Scdwjobschedule
-JobName
$SCDWMGJob.Name -ComputerName
SCSMDW01

}

foreach ($SCDWJob
in
$SCDWJobs){

Disable-Scdwjobschedule
-JobName
$SCDWJob
-ComputerName
SCSMDW01

}

The Start runbook is the same concept just need to use the Enable-SCDWJobSchedule

$SMModule
=
“C:PowershellModulesService ManagerPowershellSystem.Center.Service.Manager.psd1”

$SMDWModule
=
“C:PowershellModulesService ManagerMicrosoft.EnterpriseManagement.Warehouse.Cmdlets.psd1”

Import-Module
-force
$SMModule

Import-Module
-force
$SMDWModule

$SCDWJobs
= @(“Transform.Common”,“Load.common”)

$SCDWMGJobs
=
Get-SCDWJob
-computer
SCSMDW01
|
where {$_.Name -match
‘Extract*’}

foreach ($SCDWMGJob
in
$SCDWMGJobs){

Enable-Scdwjobschedule
-JobName
$SCDWMGJob.Name -ComputerName
SCSMDW01

}

foreach ($SCDWJob
in
$SCDWJobs){

Enable-Scdwjobschedule
-JobName
$SCDWJob
-ComputerName
SCSMDW01

}

I just completed upgrading my lab install of Orchestrator and wanted to blog a few minor notes. This blog post just covers the high level steps.

If you have all of the System Center 2012 products installed this is the first system center product to upgrade to SP1 if you are following the Sequencing guide provided by Microsoft.

Most important steps of the upgrade are to make sure you have a backup of the database, if you are running Orchestator in a VM I would recommend a snapshot also if this is a production environment.
Continue reading

In this Blog post I’m going to cover how I created an AD group Connector to update the CMDB with some extended properties for AD groups.

I wanted to be able to publish the description field for AD Groups in the SCSM portal so it is easy for the end users to know what the purpose of the group is, so they can request to be added to the group then the owner of the group can get the approval notification.

to do this I needed to extend the AD Group class with the SCSM Authoring tool. Continue reading