Installing and Configuring ConfigMgr Fast Channel Support

    Recast ConfigMgr Fast Channel support was added in version 4.2.2004 of Right Click Tools and Recast Management Server. Fast Channel Support requires a script to be installed in your ConfigMgr console, and requires a WMI provider to be installed on the devices you would like to manage though the Fast Channel. The script is created when installing Right Click Tools, the WMI Provider is installed by installing the Recast Agent.

    Recast Fast Channel Support Basic Requirements

    This documentation assumes that you have the most recent version of the following configured and functional.

    • Fast Channel Support requires ConfigMgr Current Branch 1710 or later
    • Recast Management Server - Fast Channel Support will be managed through the Recast Management Server
    • Recast Proxy - enables the Recast Management Server to read from AD and ConfigMgr to populate scopes
    • Right CLick Tools - contains the Fast Channel Script that will need to be added to the ConfigMgr Console
    Note

    The account that you use for Recast Proxy will need to have the ability to read devices with the Add/Remote programs table, and permissions to run scripts. Ideally you should scope the account to only have permission to run the Fast Channel Script.

    Download the newest version of Recast Agent

    You can download the latest installer for Recast Agent by logging into the Recast Portal site at: https://portal.recastsoftware.com/

    Installation

    Fast Channel Script Import

    Import and approve the ConfigMgr Fast Channel Script in your ConfigMgr console. This script is located in 'C:\Program Files(x86)\Recast Software\Recast RCT\Extras'. The script is called 'Recast ConfigMgr Fast Channel.ps1'.

    Adding Script to ConfigMgr

    Install Recast Agent

    The Recast Agent can be installed two ways. It can be installed as a full Recast Agent that connects to the Recast Management Server (formerly known as a Recast Device proxy) or as the Fast Channel Agent that only installs the WMI provider required to make the Fast Channel work.

    Note

    Because the Fast Channel Only version does not communicate with the Recast Management Server, your Recast Portal account information or license file will be needed during the install process. You can download the license file from https://portal.recastsoftware.com

    First Agent Install Screen

    Full Agent Install

    On the second installer screen you will decide if you would like to install the full Recast Agent which communicates with the Recast Management Server or if you would like to install the Fast Channel Agent.

    To install the full Recast Agent, add your Recast Management Server information to the installer and click "Test Connection" to verify that the installer is able to communicate with the Recast Management Server.

    Full Agent Install Screen

    After the connection has been tested successfully, you can click install. When installation is completed you need to go into the Recast Management Server to approve the new Agent.

    Fast Channel Agent Install

    On the second install screen you can also select to only install the Fast Channel Agent. Choose this by clicking the box labeled "Only install ConfigMgr Fast Channel Agent."

    Fast Channel Agent Install

    License the Fast Channel Agent

    This screen will only display if you have selected to only install the Fast Channel Agent. You can enter your Recast Portal email address and password, or you can browse for a downloaded license file.

    Add The License File

    Installing Recast Agent Silently

    There are two parameters that need to be specified to install the Recast Agent silently.

    You should use the parameter RCTENTERPRISESERVER=https://: if you would like to have the Agent communicate with the Recast Management Server (full Agent).

    You should use the parameter LICENSEPATH= to specify the license file to use for your Agent installation. In version 4.2.2004 this needs to be specified for all silent Agent installations.

    Silent Install Examples

    msiexec.exe /i "Recast Agent.msi" /qn RCTENTERPRISESERVER=https://FQDN.domain.com:444 LICENSEPATH=".\License\my.license" (will install the Full Agent on a device, note that the license path can be a relative or full path) msiexec.exe /i "Recast Agent.msi" /qn LICENSEPATH=".\License\my.license" (will install the Fast Channel Agent on a device, note that the license path can be a relative or full path)

    Configuring the Fast Channel in Recast Management Server

    Create a Scope

    Create a ConfigMgr Site scope, or a ConfigMgr Device Collection Scope. With this scope, Recast Management Server is creating a list of devices to determine which endpoints are able to run actions over the fast channel. Specifically it is creating a list of computers with the appropriate Configuration Manager Client version (5.00.8577 or higher) and the appropriate Recast Agent version (4.2.2004 or higher) installed.

    ConfigMgr Site Scope

    ConfigMgr Device Collection Scope

    Create a Route

    Create a ConfigMgr Fast Channel Route.

    ConfigMgr Fast Channel Route

    Your Recast Management Server is configured to route actions over the ConfigMgr Fast Channel.

    Which Devices can be routed via Fast Channel

    To find out which devices can be routed to via the fast channel, click on the GetDevicesInCollectionScope or GetDevicesInSiteScope Actions in the Audit Log.

    Devices to route to Fast Channel

    Then click "View Results" on the far right, in the window that opens click "Compare Data" and scroll down to select "IsRecastFastChannelCapable". A chart will appear that will show how many devices are capable of Fast Channel Communication in your scope.

    Chart of Fast Channel Capable Devices

    Are Actions Running over the Fast Channel

    To determine if actions are actually running over the fast channel you can check the scripts node under the monitoring section. If you can see that the Fast Channel Script you added is running successfully, it can be assumed that it is working correctly.

    monitoring node