We’ve been thinking about posting this information for a while now but Thomas Ellermann beat us to it :) Thanks Thomas for compiling this information!
The Solutions Accelerator Team (SAT) created many compelling solutions for the System Center suite of products. The team, however, was disbanded last year causing many of their solutions to lose sponsorship. As a result, there have been many questions on the roadmap and supportability of their solutions. This blog post provides some direction on the following three rather popular Service Manager solutions.
As things stand, all of these solutions are end-of-life and are not expected to see any further development. They do continue to be supported, but support is limited to largely the following three categories:
Other bugs and asks are not in scope.
Additionally, the table below summarizes the different versions of Service Manager which have been tested against these solutions. Configurations marked “No” are not supported.
As you can see, CSPP is the only solution tested and supported for SCSM2012 R2, however, we strongly recommend you consider Windows Azure Pack (WAP) as a replacement.
As mentioned above, there will not be any further development on these solutions. So, please be aware of this if you rely on these solutions and wish to upgrade your current environment to the R2 release of Service Manager.
Hope this helps bring clarity.
That's really bad news! Especially the thing with AAW, how does MS provide functionality to synchronize SCCM and SCSM for any software requests? Will this functionality be included in SCSM in further releases or how can it be solved? Please don't tell me 'self-development' as this is a feature used very often and self-development makes not much sense here as it is not individual for each customer.
That is a shame. Automating application deployment is a very core feature to be requested when it comes to System Center integration. And everything from one portal, best would be the SCSM portal (which is shocking). I hope to see a new and improved portal with functions from integration with SCCM to deal with deployment of applications without having to automate everything through homebuilt Orchestratorflows.
The IT GRC and Cloud Services packs were both non-starters for most of my clients, but the AAW is required functionality. This is really bad news. My only hope is that there is some future plan for combining the CM and SM end users portals into a unified HTML5 user-portal solution for R3, but until then, we're left twisting in the wind a bit here.
Hvis is sad news. We have used a lot of time on customizing the AAW solution. It has helped us with Automation of applications in our environment. From having dedicated IT staff to Control app deployment, everything is automated to day with AAW, supporting runbooks and workflows in SCSM.We have saved huge amount of time and Money on this. By adding the App Cat as å Web part in the portal, We are able to have one portal to the end users.We were planing on using the solution on our next upgrade.... Guess We have to se What Cireson (Travis, Wally) will do about this, i bet Three is a new app request solution in CS portal around the corner.. Another Cool SAT tool out of scope!