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

This is just a quick post to use as a reference for when writing powershell scripts for orchestrator. I will update this post in the future with other useful Import-Module powershell snippets as I write them or run across them in my runbooks.

The snippets that don’t say Remote connection next to them you need to have the powershell Cmdlets installed locally on your Orchestrator Server.

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 change request solution we have created a few new templates for Change Request. Unless I miss something it doesn’t seem that this a GUI interface that allows you to update the Category filed in the template or once the WorkItem is created. We are creating custom views for each different type of change request and since we utilized 3 of the 4 built in templates and just modified them they already had the category populated with the data I wanted to filter on. So I figured this would be a quick runbook to create.

Here is the layout of the runbook
Continue reading

When installing the Cloud Services Process Pack SP1 version, I ran into a few issues that are worth noting. On the Orchestrator Server

  1. If you don’t have an OrchestratorUsersGroup on the local machine because you selected a domain account during the install. You will need to create one this was covered by a blog post you can find here.
  2. Add your service account for Orchestrator and the account running setup if they are different to the OrchestratorUsersGroup.
  3. SQL Version Requirement, I didn’t find any documented requirements searching the web and the admin guide quickly. On the configuration screen below I was getting an error “SQL Server 2008 was not found” My SQL Server was running SQL 2008 R2 SP2. After upgrading to SQL 2008 R2 SP2 CU5 I was able to proceed past the error.

     

    I am now stuck at the step of importing the runbooks

    One thing to check is that your powershell scripts are unblocked you can find details on that here, but that didn’t allow me to proceed any further in the setup.

    Update: I was able to finish the install

    The last change I made that allowed the setup wizard to finish was to open the runbook designer on the server, create a new runbook check it out, then delete it.

    Few other items to note that I had recently done in troubleshooting was added the logged on user to the OrchestartorSystemGroup on the local machine and added the service account to the OrchestratorUserGroup on the local machine.

    Here is the Technet forum post that provided the solution to the strange problem.

In preparing for the upgrade to SP1 for SCOM I decided to finally put in some alerting and simi-auto resolution to the settings for Veeam KB1036 that needs the SCOM agent reconfigured after every patch to the SCOM agent.

Issue: When the health service agent is upgraded with a CU/SP patch it stops reporting into the management server, this triggers a Health service alert but doesn’t directly tell everyone that we also just lost all of our monitoring into ESX.
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

}