For Task 5 & 6 of this multi-product implementation workflow, you'll set up your Configuration Manager Console to work with Application Manager. There's no need to install Application Manager separately, as it is included automatically in your installed Recast Management Server if you are licensed for AM.
Once you're done this task, you're ready to complete the initial setup for Application Manager and deploy Recast Agents using AM.
For Application Manager to work within your Configuration Manager Console, you'll need to set up Distribution Point Groups and Collections in your ConfigMgr environment. You also have the option to set up an Application Root Folder.
Set Up Distribution Point Groups
Application Manager targets application content to distribution point groups. You must have or create at least one distribution point group in Configuration Manager before installing Application Manager. You might want to include all distribution points in your distribution point group, but in larger environments it's possible to include only distribution points used for application media distribution. You can use existing distribution point groups in Application Manager.
To create a new distribution point group:
1. In your Configuration Manager console, navigate to Administration > Distribution Point Groups.
2. In the upper left-hand corner, click Create Group.
3. In the window that opens, specify a Name for the distribution point group.
4. On the Members tab, select the distribution points where content should be distributed by Configuration Manager when new applications are created by Application Manager and click OK.
Set Up Collections
Device and user collections are used as a deployment target in Application Manager's deployment processes. You can create collections in your Configuration Manager console by navigating to Assets and Compliance > Device Collections or User collections.
If you are using Application Manager to deploy all your selected applications to all of your devices, which is most common, you only need two collections — Pilot & Production.
Create an Application-Specific Collection
To deploy an AM-created application to only those devices containing a previous version of the application, you can create application-specific collections in Configuration Manager by using queries. After the collection is created, add it to an application-specific deployment process in Application Manager.
- In addition to deploying an application to an application-specific collection as a Required deployment, you can also create an Available deployment for the rest of your devices.
- If the newly created collection is not visible in Application Manager, navigate to the Deployment Processes page in RMS and click the Refresh icon on the Add Collection side panel.
To configure an application-specific query for a collection:
1. On the Membership Rules page in the device or user collections wizard, add a query rule to a collection.
2. Under Query Rule Properties, click Edit Query Statement.
3. On the Criteria tab, add new criteria and select Installed Software > Product Name. Add the application name to the Value field with percentage symbols around it (%APPLICATION%).
Example queries for application-specific collections
You can also use our example queries as listed below. Add a WQL query by selecting Show Query Language in the Query Statement Properties window.
TIP: You can determine an application's exact product name in your Configuration Manager console by selecting a device with the application installed and going to Resource Explorer > Installed Software.
Mozilla Firefox
select * from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId = SMS_R_System.ResourceId where SMS_G_System_INSTALLED_SOFTWARE.ProductName = "Firefox x64"
Google Chrome
select * from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId = SMS_R_System.ResourceId where SMS_G_System_INSTALLED_SOFTWARE.ProductName = "Google Chrome (64-bit)"Adobe Reader DC
select * from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId = SMS_R_System.ResourceId where SMS_G_System_INSTALLED_SOFTWARE.ProductName = "Adobe Acrobat Reader DC (64-bit)"If the product name includes a version
select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceID = SMS_R_System.ResourceId where SMS_G_System_INSTALLED_SOFTWARE.ProductName like "<product name>%"
Set Up An Application Root Folder (optional)
Application Manager will create a folder structure for Configuration Manager in Software Library > Application Management > Applications. You can specify the root folder name created under Applications. All applications added by AM will be created under this root folder with the following structure: Publisher > Application name. By default, the root folder name is Application Manager, but you can change this in the deployment process settings.
Next Up — Complete your initial Application Manager setup then do Task 6: Deploy Recast Agents Using Application Manager
A Recast Agent is installed on a computer and runs Right Click Tools actions on that computer as the local system account. A Recast Agent should be deployed on each device you want to run Right Click Tools actions against. After deploying Recast Agents, you can configure them to run Right Click Tools actions or for Fast Channel Support. You can also use the same Recast Agent for Endpoint Insights and Privilege Manager. To learn more about Recast Agent uses, see the Recast Agent Overview.
We recommend deploying Recast Agents using Application Manager. To do so, first complete the initial setup of Application Manager.
NOTE: Your Right Click Tools Enterprise license alone gives you access to Application Manager to deploy Recast Agents. (In the absence of Application Manager licensing, only the Recast Agent application will be available in the AM software catalog.) To deploy Agents using Application Manager, first ensure that your Recast Management Server is running Recast Software version 5.4 or later, as that is the version that introduced Application Manager in RMS.
TIP: Alternatively, you can choose to deploy Recast Agents using the Agent installer.
Prerequisites for Deploying Recast Agents:
- If deploying 5000+ Recast Agents, follow the 503.2 IIS Error instructions before proceeding.
- If your Recast Management Server is using a self-signed certificate, you must first import the certificate into the Trusted Root Certificate Authorities Store on all devices that will have Agents.