Recast Management Server Onboarding FAQs

How do I install and configure the Recast Management Server? 
You can find instructions here:

Where should the Recast Management Server be installed?
We recommend installing RMS either on its own server or the ConfigMgr server.

Can the Recast Management Server co-exist with our current SCCM server? Or is a new one recommended? 
Yes, it can co-exist. If it is installed on a new server, we do recommend allocating at least 4 cores CPU and 8GB of memory for RMS. For further RMS pre-requisites, please see this article: Installing Recast Management Server

What is the Recast Proxy?
You can find details here: About Recast Proxies

Does the Proxy require an Agent on a computer?
No, it does not. You can find more about Recast Agents here: Installing Recast Agents

To install the Recast Proxy, do I need a service account?
Yes. You will need to create or use an existing service account for the proxy.

If an action is done through a Proxy, how is that shown in the audit log?
The audit log reflects the user that kicked off the action. If a Proxy route was used, then the "PROXIES" button to the right of that audit log action will be populated and say "TRUE".

Why can't I see the Web Dashboards in the Recast Management Server?
The Web Dashboards require the Recast Proxy to be installed. You can learn about how to set that up here: Configuring Recast Proxy for Recast Management Tasks

More information about Web Dashboard trends can be found here: Web Dashboard Trends Overview

How resource-intensive are the Web Dashboards' snapshots and trends? 
These are saved in the database, so there will be a slight increase there. You can edit how long you want these to be stored by editing the MaxSnapshotAge in your RMS settings.

Where can I find more information about RMS and its features?

If you have any further onboarding questions, please reach out to your Technical Onboarding Manager.

For technical issues, please visit our Recast Management Server Troubleshooting page or email