September 6 2012

Application Approval Workflow Solution Accelerator

Straight from the TechNet website (http://technet.microsoft.com/en-us/library/hh881789.aspx) – Application Approval Workflow (AAW) takes an application request submitted through the System Center 2012 Configuration Manager Application Catalog and transforms it into a System Center 2012 – Service Manager service request, allowing flexible approval lists and activities.

In my scenario I was interested in having a different approvers for different applications when users were requesting applications through the SCCM Application Catalog (Self Service portal).  It was not sufficient to have SCCM Administrators as application approvers, sometimes we needed department manager to be the approver, sometimes the line manager and sometimes the application owner.  After implementing SCCM, SCSM and SCORC, here are a few of the things I learnt along the way when implementing the AAW Solution Accelerator (mostly for self reference later on!):

  • Even after installing AAW you still don’t have any workflow templates – there are 3 sample ones here (http://blogs.technet.com/b/servicemanager/archive/2012/06/20/application-approval-workflow-sample-templates.aspx) – line manager approval, department manager approval and multistep approval process. Like a lot of Service Manager administration, you need to use PowerShell to import these (Import-SCSMManagementPack cmdlet);
  • The account used in the SCSM Orchestrator connector needs to be a member of the OrchestratorUsersGroup  group;
  • The account used in the Orchestrator Integration Packs configuration needs to be a member of the OrchestratorSystemGroup group;
  • At one stage I was getting ‘The object ‘Get Extended Application Information’ in the Runbook ‘CM-> SM Synchronization’ failed’ error in SCORC, this seemed to be happening because SCORC was installed on the same server as SCCM, I moved SCORC to a different server and the error did not reappear. I believe this is something to with having SCORC on the SCCM primary server as the Orchestrator Integration Packs configuration would not let me use credential to set up the connection to SCCM as it considered this a ‘local’ connection;
  • ‘Selection Criteria’ needs to be created through SCSM to associate the workflow template with the application or user – this then needs to be put into ‘production’ status;
  • Upon first attempt to access the SCSM Self Service portal, ‘Access Denied’ error is shown. Solution is here – http://systemcenter.no/?p=136;
  • You will come across this issue if you are using the default which is to use a self signed certificate – I needed to create a new certificate, ensure the issuing CA was trusted on the client and update the webconfig file – http://blogs.technet.com/b/servicemanager/archive/2012/05/04/faq-why-is-my-self-service-portal-service-catalog-blank.aspx and http://www.code4ward.net/main/Blog/tabid/70/EntryId/139/Service-Manager-2012-Self-Service-Portal-not-working-blank.aspx

Maybe this well assist someone else along the way….

 

 



----------------------------------------------------------------------------
I use a maximum of one Google Ad per post to help offset some of my blog hosting costs.

----------------------------------------------------------------------------


Tags: , , , , ,

Posted September 6, 2012 by danovich in category "Opalis / Orchestrator", "SMS / SCCM

1 COMMENTS :

  1. By danovich (Post author) on

    Tomasz Gosciminski has also been doing some testing and has confirmed that the SCCM connector is not required in SCSM for AAW to work

    Reply

Leave a Reply