We are looking into implementing Deep Command 2.1 and the documentation references the need for the Intel RCS for remote configuration. Is my understanding that, RCS is for configuring AMT systems in the LAN remotely and SCS is for configuration on the actual AMT hosts, correct? If so, is it supported (best practice) to install the Intel RCS on the same server host that is running ePO? The ePO is the only agent handler in our environment and the database is offloaded on a dedicated SQL server. Thanks.
This is supported; however, depending on your overall node count it may not be recommended. Once the total number of systems you are managing with ePO reaches around 50,000 (roughly) we recommend a dedicated server for the ePO application.
The RCS server is only used during the provisioning process so it does not generally impart a particularly high load on the server; however, if you were to try to provision a very large number of machines at once it could prove problematic to co-host it on ePO.
We have less than 1000 systems and we always do phased deployments. I don't think we will ever reach 50K nodes on a single ePO so we should be OK. Thanks.
If we have well under 1000 clients and already have Intel SCS 8,2 on a separate server, what are the steps to move it to the ePO server before updating it to RCS Manager 126.96.36.1991?
Actually we have been in contact with McAfee support and they have recommended not to install on the same host as the ePO. The Intel SCS appears to be a lightweight component and in relatively small environments, it would be great for places with limited hardware resources to be able to use the ePO server to host this component.
I'm in McAfee Support.
It all depends on the size of the enviroment. For a very small enviroment under 1000 machines co-locating the SCS server on the ePO server is fine provided the ePO server is appropriatly resourced. If the ePO server is already taxed then adding any application to it would be ill-advised regardless of what the application is or how many machines ePO is managing.
To move the SCS application simply install it on whatever server you want to use it on, create your profile and install the RCS manager plugin from ePO. Then complete 2 ASCIs and you should see the profile from the new RCS server in the EDC policies.
We already have a working profile on the existing Intel SCS. How do we prevent conflicts when we install RCS Manger plugin on the ePO server? Can we copy the profile from the existing SCS?
Also, when Deep Command was initially set up a couple years ago with version 1.0 or 1.5, I remember needing to do a lot of configuration with certificates and machine account permissions in DCOM etc on the server that has SCS.
Would we need to do that all over again if moving it to the ePO server?
Once AMT has been configured on systems, does the McAfee managed RCS component continue to communicate with endpoints, or is it really there for the initial configuration and then only for subsequent configuration changes?
Yes you will need to follow all the required steps to install the SCS server. The exact steps are documented in the product guide. You cannot migrate your profile rather you will have to generate a new one. No conflicts should occur with the RCS manager having multiple RCS servers is a supported configuration. In your provisioning policy for EDC inside ePO you simply need to point it to the newly created profile on your new RCS server to begin using it.
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center