There are two types of permissions that will allow the Recast Management Server installer to automatically create the SQL database with all the necessary permissions:
- The user account running the installation can be assigned a SysAdmin role in the SQL instance. If the user account has permission to connect remotely, use the Test SQL Connection button to check connectivity to the SQL Server during the install. After the RMS installer creates the database, the SysAdmin permission can be removed.
- The computer account of the Recast Management Server can be granted db_creator permissions. In this case, check the Skip SQL Connection Test box on the installer's SQL Configuration page.
Pre-create the RecastManagementServer Database
If the account running the Recast Management Server installer does not have permission to create a SQL database, the database administrator can pre-create a database named RecastManagementServer and assign permissions manually.
Remote SQL Server: Where the database is remote from the Recast Management Server, assign db_owner permissions on the database to the computer account of the Recast Management Server.
Local SQL Server: Where the database is local to the Recast Management Server, assign db_owner permissions on the database to the IIS AppPool\Recast Management Server account.
NOTE: The IIS AppPool\Recast Management Server account will not exist until after the installation is finished, so db_owner permissions will need to be assigned after installation.
Add the Computer Account via SSMS
If the computer account for the Recast Management Server computer does not exist in SQL, users will need to add the computer account manually, as a Login Account in SQL Server Management Studio (SSMS).
Add the Computer Account as a Login Account
To create the computer account as a login account:
1. Open SSMS and expand the folder of the server instance in which you want to create the new login.
2. Right-click on the Security folder, point to New and select Login.
3. In the Login - New window, on the General page, enter the Login name of the account in the following format: <domain name>\<computer name>$. Including the dollar sign ($) treats the login name as a computer account rather than a user account.
4. On the User Mapping page, in the Users mapped to this login section, select RecastManagementServer.
5. In the Database role membership section, select db_owner.
Recast Management Server software can be installed on its own server or on the primary Configuration Manager server.
Run the Recast Management Server Installer
After downloading Recast Management Server from the Recast Portal, run the installer and follow its prompts.
IIS
To configure IIS:
1. On the IIS Configuration page, change the Server Name only if the client is going to use a DNS alias.
2. Set the IIS Port. The default IIS Port is TCP 444, to prevent conflicts when Recast Management Server is installed on Configuration Manager servers. The IIS Port can be changed to 443, or any open TCP port, to suit your environment.
Certificates
Recast Management Server requires a certificate for secure communication with Right Click Tools and any Recast Proxies.
To configure a certificate:
On the Certificate Configuration page, we recommend that you Use an Existing IIS Certificate issued by a trusted Certificate Authority (CA). If you choose to Generate a Self-Signed Certificate, you must import the Recast Management Server self-signed certificate to the Trusted Root Certificate Authorities store on devices running Right Click Tools, Recast Agent, or Recast Proxy.
CERTIFICATE NOTES:
- The certificate subject name (or a subject alternative name) should match the server name in the URL that Right Click Tools and Recast Proxies are pointed toward.
- Right Click Tools will prompt for any untrusted certificates and add them to an allowed list.
- The certificate can be changed later by editing the Binding in IIS Manager.
SQL Server
There are two types of permissions that will allow the Recast Management Server installer to automatically create the SQL database with all the necessary permissions:
- The user account running the installation can be assigned a SysAdmin role in the SQL instance. If the user account has permission to connect remotely, use the Test SQL Connection button to check connectivity to the SQL Server during the install. After the RMS installer creates the database, the SysAdmin permission can be removed.
- The computer account of the Recast Management Server can be granted db_creator permissions. In this case, check the Skip SQL Connection Test box.
SQL SERVER NOTES:
- The default SQL Server Port Number is 1433.
- A fully licensed version of SQL is strongly recommended to avoid the 10GB storage limitation of SQLExpress.
- After the SQL database is created, set the database recovery model to simple to prevent storage issues.
- Remote SQL Server: The computer account of Recast Management Server will need db_owner permissions to create the database on the remote device. If the account running the Recast Management Server installer does not have permission to create a SQL database, the database administrator can pre-create the RecastManagementServer database and manually give the computer account db_owner permissions.
- Local SQL Server: The IIS AppPool\Recast Management Server account will need db_owner permissions to create the database on the local device. Alternatively, the database administrator can pre-create the database and give the IIS AppPool\Recast Management Server account db_owner permissions to the database. The IIS AppPool\Recast Management Server account will not exist until after the installation completes, so the permissions will need to be given after installation.
Import License
You can download and import your Recast licenses when installing Recast Management Server.
To download your Enterprise license:
1. On the Import License page, enter your Recast Portal email address and password.
2. Click Download License. The license information will appear in the right-hand column.
NOTE: If your server does not have internet access, click Browse for License to browse the filesystem for a license file that has been exported from the Recast Portal.
Proxy
If the Recast Proxy is being installed on a server other than the Recast Management Server, install the Proxy separately after Recast Management Server installation.
NOTE: Proxy configuration is optional for Privilege Manager where Active Directory or Microsoft Entra ID objects are not used to target rules.
To configure the proxy during RMS installation:
On the installer's Proxy Configuration page, enter the service account Domain, Username, and Password and click Test Credentials to verify service account details.
TIP: If you haven't already set up the required proxy permissions, remove any information from the text fields, select Test ConfigMgr Connection and the Skip ConfigMgr Verification checkbox, and click Next.
Domain
To configure your domain:
1. On the Domain Configuration page, enter the Domain Name.
2. Click Test Domain Connection to verify that the service account has access to read from your domain.
Configuration Manager
NOTE: Configuration Manager does not need to be set up for Privilege Manager.
To set up your Configuration Manager for the proxy:
1. On the Configuration Manager Configuration page, enter the following information:
- Name of the site server that has your SMS Provider role
- Site Code
- Name of the SQL Server where your Configuration Manager SQL database is located
- SQL Database name
NOTE: You can skip the Configuration Manager Configuration page during Recast Management Server or Recast Proxy installation by removing any information from the text fields, selecting Test ConfigMgr Connection and the Skip ConfigMgr Verification checkbox, and clicking Next.
2. Click Test ConfigMgr Connection to check that the service account has access.
MBAM
MBAM configuration is only required for a separate MBAM Server. If you are using the ConfigMgr-integrated BitLocker or AD, you can skip this section. MBAM also does not need to be configured for Privilege Manager or Application Manager.
To configure MBAM:
1. Tap Click Here to Configure MBAM.
2. Add your Administration URL and SQL Server information.
3. Click Test MBAM Connection to verify that the service account has access to MBAM.
Initiate RMS Installation
Once you have filled in all the necessary information, click Install at the bottom of the MBAM Configuration page.
When the installation is complete, open the Recast Management Server by navigating to https://ServerFQDN:Port in a web browser (Chrome, Edge, or Firefox are recommended).
When asked to sign in, enter the username and password for the account used to install the Recast Management Server.
Installation Log Location
To check the installation logs for Recast Management Server and Recast Proxy (when installed together), navigate to C:\Users\user account running the install\AppData\Local\Temp
NOTE: The log is named something like Recast_Management_Server_2022*****.log
The Recast Management Server requires access to specific external domains depending on which Recast Software products are in use. If you are using a web proxy on the Recast Management Server, or on the server running Recast Proxy, you will need to direct network traffic to those external domains through the web proxy, as the web proxy will not automatically detect settings on the server where the RMS or Recast Proxy is installed.
You can direct network traffic through the web proxy by changing the environment variables in your Recast Management Server web.config file.
To change environment variables for a web proxy:
1. Open the web.config file located at C:\Program Files (x86)\Recast Software\Recast Management Server\web.config.
TIP: We recommend making a copy of the existing web.config file before editing.
2. In the aspNetCore module, edit the Environment Variables information and add opening and closing tags.
<environmentVariables> <environmentVariable name="all_proxy" value="http://proxyserver:port" /> <environmentVariable name="no_proxy" value="RmsServer.example.com,SccmServer.example.com" /> </environmentVariables>
For details about the environment variables used for default proxy initialization, see Http
3. Recycle the Recast Management Server application pool and restart the site in IIS.
After editing the environment variables in the web.config file, follow these steps to verify the web proxy settings are correct for the account running the Recast Proxy service.
4. Log into the server as the Recast Proxy service account, open Internet Options and verify the proxy information is correct there.
5. If you are defining the web proxy manually, navigate to Internet Properties > Connections > LAN settings and check that Automatically detect settings and Use automatic configuration script are deselected. If both those options and Use a proxy server for your LAN are configured, they will conflict.
NOTE: If the Application Manager catalog fails to load and returns an error: 'The proxy tunnel request failed with status code 407', add a rule to allow NoAuth access from the Recast Management Server to the external domains required for Application Manager.
A Recast Agent is installed on a computer and runs actions on that computer as the local system account. A Recast Agent should be deployed on each device you want to run 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, see Recast Agents and Recast Agent Gateways.
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.
Deploy 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.
TIP: Alternatively, you can choose to deploy Recast Agents by downloading and running the Agent installer.
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:
1. If you haven't already done so, complete your initial AM setup, skipping the Setup Wizard's Define Deployment Processes step.
2. Add a deployment process for the 'Recast Agent' application.
3. On the Deployment Process Details page, click the Settings cog to open your Global Deployment Process settings.
4. On the Advanced tab, set Additional Installation Parameters:
- Silent Agent Install: Add the RCTENTERPRISESERVER=https://<RMS URL>:<Port> parameter to your install string, substituting the URL and port number for your Recast Management Server.
- Connect Recast Agents to a specific Agent Gateway: Add the AGENTGATEWAY=https://<AG URL>:<Port> parameter to your install string, substituting the URL and port number for your Agent Gateway
NOTE: Adding these parameters in Application Manager's deployment settings enables deployed Recast Agents to connect to your Recast Management Server, verify that the certificate used by the RMS is trusted, and successfully enroll with the RMS. Recast Agents are required to enroll with the RMS before they can communicate with a Recast Agent Gateway and be used to run actions.
Agent Deployment Video Walkthrough
See Recast Application Deployment with Application Manager on our YouTube channel.
By default, the RecastManagementServer database is set to full recovery. We recommend switching your SQL Server recovery model from full recovery to simple recovery to prevent the database from running out of disk space due to an overload of transaction logging.
To learn more about the difference between simple, full, and bulk-logged recovery, see Recovery Models (SQL Server) | Microsoft Learn.
To switch the SQL Server recovery model to simple recovery:
1. Open SQL Server Management Studio (SSMS).
2. Expand the Databases folder.
3. Right-click on the RecastManagementServer database and select Properties from the drop-down menu.
4. In Database Properties, click the Options page.
5. Change the Recovery model to Simple and click OK to save your changes.
