Last month I published a new version of Enum Builder to the TechNet Gallery. The latest version only addressed a few bugs, the main bug was the accessibility property was being set to Private, this has been corrected and now sets the property to Public. In the previous release I added 2 new features:

1. Command line executable, here is an example of how to use the switches

EnumBuilderCLI.exe –MPID TestMP –MPVersion 1.0.0.0 –MPName TestMP –RootEnumMPID System.WorkItem.Incident.Library –RootEnumMPVersion 7.0.5244.0 –RootEnumKey 31bf3856ad364e35 –CSVFile “C:_ITNew folderIR_Classifications – Copy.csv” –NewMPFile “C:_ITNew folderIR.xml”

2. The gui version now has an option to create negative ordinals

clip_image001

During the setup of Application Approval Workflow that can be downloaded here, you are asked to provided a user to connect to ConfigMgr and Service Manager. These accounts are stored in Orchestrator to run different runbooks. There is a few things that the documentation doesn’t cover or assumes that you already know from using Orchestrator.

If you selected to use an AD group during install for your Orchestrator user Group you will need to create a local group called OrchestratorUsersGroup on your Orchestrator Server.
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.

If you try to install the SCOM agent on a SharePoint server that already has the SCSM self-service portal installed, the install of the SCOM agent will fail. To resolve this the only option is to uninstall the SCSM self-service portal then install the SCOM agent and reinstall the SCSM Self-service Portal.

Since most of the configuration for the self-service portal is stored in the SCSM database this process can be done fairly easily as long as you have not done any major modifications to the self-service portal and where having a well-documented change process in place comes into play.
Continue reading

After upgrading my SCSM management server to SP1, I found that my management server would not start. The only error I could find in the logs that was related was this error that wasn’t very helpful.

The Management Group <MGNAME> failed to start.  The error message is 0x80131701(0x80131701).  A previous message with more detail may have been logged.

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

}