+3We are wanting to move the Command Center off the CS onto a standalone WebServer so when we present the Command Center to our customers, they are in essence logging onto the WebServer and not the CS.
Can someone confirm this is the correct procedure to follow?
Web Server Hardware Refresh
https://documentation.commvault.com/2023e/expert/web_server_hardware_refresh.html
Thanks in advance.
Best answer by Jacek Piechucki
Hi,
If the requirement is just to give the users the Web Console/Command Center access via an external client, it is enough to deploy a client with “only” Command Center package. It will then be the Application server, while Commserve stays the WebServer. It is the simplest action assuming, for its simplicity, that the new client will have access to Commsere database.
Good day,
Effectively yes that’s it - backup the DM2 / CVCloud databases off the CS and restore them onto the new WebServer. Worth noting technically you don’t have to migrate your WebServer - you could stand up a WebConsole machine that points to the Commserve as the WebServer. That way your end users are logging into the WebConsole machine but there’s less work up front to make this work.
The baseURL registry key is clutch here - it tells the WebConsole machine where to go to for WebServer access. So can you follow that doc sure, but do you have to? As with many things there are more than one answer. No right or wrongs as long as you achieve the desired effect.
Hi,
If the requirement is just to give the users the Web Console/Command Center access via an external client, it is enough to deploy a client with “only” Command Center package. It will then be the Application server, while Commserve stays the WebServer. It is the simplest action assuming, for its simplicity, that the new client will have access to Commsere database.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
