Change the FileHold server name
Warning: Use this tool if the name of the FileHold Windows Server has changed or needs to chang. You should not consider changing the FileHold Windows server name without very good reason. The Server name change must not also include a domain change at the same time.
- Changing a Windows server name does not always work out. System ID's can become corrupted. Local Users and Groups snap-in may not work, SQL Server might stop functioning. Most of the time, it is painless, but rarely or occasionally, it can be very problematic. If you are running a virtualized server, take a snapshot, and for any type of server make sure you have backups of all relevant FileHold data and databases.
- You might also need to setup a new LocalServer\FH_Service account, and assign proper permissions if the FH_Service account was a local account. This guide does not cover that scenario.
- If you have an SSL Certificate enabled, this page does not cover this procedure, but you can refer to this page for the guide on replacing the SSL Certificate and ensuring your system works after the change.
- This guide will show you how to change the FileHold name specifically using the FHInstrumentation tool.
- Run FHIT as a domain administrator. You must also be an administrator on the SQL Server that houses the FileHold databases.
- Select Change Port, server name or protocol and click Start.
- Select the Check Server Name checkbox, and enter the server name of the FileHold Windows Server
- Click Next.
- Click Start.
- Once it is completed, restart the WWW Service.
- Run the FHInstrumentation Health Checker as an administrator to validate the system change.
- Update your Web Client Login URL and Desktop Client URL with the new server host name.
- Try to login to FileHold and test the system.