After some extremely busy weeks I finally found some time to write a blog again. In my earlier blogs about RES Workspace Manager 2014 I explained the support of this current version with System Center 2012 R2 Configuration Manager and Microsoft App-V version 5. I my first blog about the support of Configuration Manager 2012 R2 in RES Workspace Manager 2014 I mentioned that you are able to deploy the application with RES Workspace Manager 2014 without actually deploying it to a collection in Configuration Manager 2012 R2.
As we all know you need to deploy an application or package to be able to install it on a device. The fact that RES Workspace Manager 2014 is installing the applications without actually deploying it in Configuration Manager 2012 R2 got me triggered to look at how this integration really works.
How it works is actually really simple, what really happens when you click on a link that is managed via RES Workspace Manager 2014 is that during the Execution Phase (see figure below) a custom Collection with the name of the workstation is and a custom required deployment is created.
The Configuration Manager 2012 client is triggered to perform an Application Deployment Evaluation Cycle that kicks of the just created required deployment.
After the deployment of the package is finished the collection and deployment are removed from Configuration Manager 2012 R2. When the deployment fails, because for instance your requirement rules or detection methods are not okay the collection will and deployment not be deleted.
Have a nice weekend! More blogs on the integration soon and maybe some dcr’s… 😉
Earlier blogs on RES Workspace Manager 2014 and Configuration Manager 2012 can be found here:
- RES Workspace Manager 2014 adds support for ConfigMgr applications
- App-V 5, ConfigMgr 2012 R2 and RES Workspace Manager 2014 better together