...building hybrid clouds that can support any device from anywhere
Okay Readers – we have the next post ready to go!
Here is the fifth of six posts in the MVP Spotlight Series for the Automation Track…
This post will walk you through importing the solution built during the Automated Service Requests with Microsoft System Center 2012 R2from TechEd 2014.
This solution has two components:
Read the in depth blog posts about the SharePoint solution and the SMA Solution (TOC found here).
You have a working SharePoint site to deploy the list to. The SharePoint site is compatible with a 2013 list template.
The template is available here.
You have configured TFS integration for SMA based on this blog post. If you have not done this you can still follow along but will have to setup the global variables and do the imports manually.
The files are available here.
These are the actual workflow files. They contain references to global configurations and accounts that are defined in XML files included in the export. Review and update these as needed for your environment.
These file contain all of the settings for the scripts. The values of these should be updated to reflect your environment.
To update the value of a variable update its ‘value’ section in the xml class:
This file contains settings that will be accessed by multiple workflows.
This file contains settings and variables for the Monitor-DFSShare-Approved workflow.
In our example we have to user accounts, these names are defined in the DFSShare.xml file. Since these are accounts and contain passwords that should be encrypted we need to create them by hand in our SMA environment. The configuration file merely has a pointer to their name. To do this we just open up the Windows Azure Pack (WAP) user interface (UI) and create them with the appropriate names!
Note Follow the same steps to create your DomainAccess account asset in SMA.
And Voilà!You now have a fully automated DFS share request in your SMA environment!
And now a few notes from me (Charles)…
Be sure to check out Ryan’s session from TechEd North America 2014!
In this session, see a real-world implementation of a fully automated IT service catalog developed by a Fortune 500 company for supporting self-service requests. This service catalog is based in Microsoft SharePoint and utilizes the newly released Service Management Automation (SMA) engine. During the session we look at how the solution is architected, cover integration between SMA and SharePoint, build a new service offering from the ground up, and share the best practices we have developed for doing work with SMA along the way. So what’s the best part? You get access to the solution we create, so you leave with access to a working solution to help get you started!
Speakers: Ryan Andorfer, Mike Roberts
Link on TechEd NA 2014 Channel 9 Recording: DCIM-B363 Automated Service Requests with Microsoft System Center 2012 R2
And finally - As always, for more information, tips/tricks, and example solutions for Automation within System Center, Windows Azure Pack, Windows Azure, etc., be sure to check out the other blog posts from Building Clouds in the Automation Track (and http://aka.ms/IntroToSMA), the great work over at the System Center Orchestrator Engineering Blog, and of course, Ryan’s Blog over at http://opalis.wordpress.com!
I'm trying to find what the correct channel is for reporting on feedback/bugs in the SMA and Azure Automation products. I have a few that I would very much like to report, but the whole Connect thing is very messy and unclear to me. Is there a "formal"
feedback mechanism for these products?
@Trond - Here is one of the best places to submit feedback:
Though, both UserVoice and Connect are monitored by the PG.