For Task 5 & 6 of this multi-product implementation workflow, you'll set up Configuration Manager and/or Intune 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
For Application Manager to work with Intune, you'll first need to do the following within the Microsoft Azure portal:
- Create the Entra ID App Registration to be used with Application Manager
- Add client secret
- Grant the application API permissions
Create the Entra ID App Registration
To create the app registration:
1. Log into https://portal.azure.com using your Azure credentials with full admin rights.
2. Search for App registrations.
3. On the App registrations page, click New registration.
4. Give the application a meaningful display Name. You can change the name later.
5. As the Supported account type, select Accounts in this organizational directory only (Recast Software only - Single tenant).
6. Click Register.
7. In the Overview pane that opens, copy the Application (client) ID and Directory (tenant) ID. You'll need to enter these later in your Recast Management Server.
Add Client Secret
1. On the App registrations page, under Manage, click Certificates & secrets.
2. On the Client secrets tab, add a New client secret.
3. Add a description for the secret (for example. Application Manager service), choose when the secret Expires, and click Add.
NOTE: You must create a new client secret before the current one expires and change the client secret for your Recast Management Server service connection.
TIP: Schedule a support ticket, task or calendar entry before the expiry time to perform these actions.
DO NOT navigate away from the page before completing the next step!
4. Copy the client secret value to a clipboard and save it to a secure location. You will not be able to see the client secret after navigating away from the page. You will need to specify the client secret whenever you modify Entra ID details in Application Manager, for example, if you want to change the display name of the Entra ID tenant).
Add API Permissions for the Application
To add API permissions:
1. On the App registrations page, under Manage, click API Permissions.
2. Select Add a permission.
3. On the Microsoft APIs tab, click Microsoft Graph.
4. Add the following permissions:
| Application permissions | DeviceManagementApps.ReadWrite.All | Read and write Intune apps |
| DeviceManagementConfiguration.Read.All | Read Intune device configuration and policies, permission only required to specify application categories in AM deployment processes | |
| GroupMember.Read.All | ||
| Device.Read.All | ||
| Delegated permissions | User.Read |
5. Click Grant admin consent for [Tenant Name].
Once the Entra ID App Registration is done and you have the Application (client) ID, Directory (tenant) ID and Client secret available, you can then add a service connection from your Recast Management Server to Entra ID for 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.
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.
Deploying Agents with Application Manager
We recommend deploying Recast Agents using Application Manager. 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 and Right Click Tools applications will be available in the AM software catalog.
Prerequisites for Deploying Agents using Application Manager:
- Recast Management Server is running Recast Software version 5.4 or later, as that version introduces Application Manager in RMS.
- Required proxy permissions for Application Manager are in place
To deploy the Recast Agent application with Application Manager, complete the initial AM setup, selecting 'Recast Agent' as the application to deploy.
For a video walkthrough, see Recast Application Deployment with Application Manager on our YouTube channel.
TIP: Alternatively, you can choose to deploy Recast Agents by downloading and running the Agent installer.