At a recent meeting of the Houston Area Systems Management User Group, I presented a strategy for delivering effective self-service application deployment that would be achievable for System Center 2012 Configuration Manager (ConfigMgr) admins could potentially implement. By intention, the solution does not require custom management pack authoring, extending Service Manager (SCSM) classes or custom PowerShell. However, it is flexible and leverages the rich capabilities of SCSM for publishing a Service Catalog. This way, any ConfigMgr admin with basic Orchestrator (SCOrch) skills who can install a basic SCSM deployment (a Management Server, database and portal server) can configure ITIL friendly self-service with System Center 2012, complete with approval routing and documentation of the request in a proper service request.
By request, I am posting the sample runbooks here for the community members.
There is a variation of my approach HERE, but in this sample I have eliminated the need for custom PowerShell script, thereby further simplifying the solution.
NOTE: You do not have to replace your service desk solution to leverage System Center for self-service. The service requests created here can pretty easily be exported with a bit of PowerShell and imported into your target ITSM system of choice.
Components in the solution as demonstrated were:
- ConfigMgr 2012 R2
- SCSM 2012 R2
- Orchestrator 2012 R2
- Cireson Portal (optional) – This component is 100% optional, though it reduces the required server count by 1, eliminates the need for SharePoint and provides a self-service experience across mobile devices and is much more responsive than the native portal.
What I demonstrated used User Collections in ConfigMgr. You could tweak the solution to use computer-based collections instead.
The following are the high-level
- Configure deployments in SCCM
- Import runbook in SCO
- Connect SCSM to SCO and ConfigMgr
- Select the software to make available
- Configure the Offering in SCSM (For SCSM newbies, see “Automation and Self-Service with SCSM” on MVA)
- Publish to the Service Catalog
Sample Runbook #1
In this example, we used to retrieve the user and application (app) object. The app object is represented in the SCSM database by the Package class, which is populated by the ConfigMgr Connector in SCSM, which brings over the applications you have created in ConfigMgr When you look at the last two activities, you will notice that the runbook assumes that the ConfigMgr application (represented by the Package class in SCSM) and ConfigMgr collection have the same name.
I am not going to walk through the detailed configuration steps of either sample, as you can simply download both sample runbooks, import and see for yourself.
Sample Runbook #2
I was asked if it would possible to extend the solution to allow use of existing packages. The short answer is yes, by simply adding a Map Published Data activity in which you can map the name of your application in ConfigMgr to the name of the collection to populate with the account of the user requesting the software.
Here is a shot of the properties of the Map Published Data activity in the sample runbook.
Download Runbook Samples
The runbook samples are available in a new GIT repository I setup to store community samples in a single, centralized repository. Both sample runbooks can be found at the URL below.