This guide is for skilled IT administrators with experience in working with BMD NTCS. It covers the following scenario:
You want to change the name of your BMD NTCS server and the SQL Server installation is also on this server. Please note that we strongly recommend doing a backup before making any changes on the server.
For the procedure described below, all users have to be logged out of BMD NTCS.
Please consider before proceeding with the first steps:
At first, you should uninstall the BMD NTCS client from every workplace, since later on the network path is going to change according to your adjustments. This step has to take place before renaming the server.
Use BMDNTCS_PGM share to start BMDNetClient.exe.
BMD recommends deleting all maintenance plans before renaming the computer. If you do not do this, you might no longer be able to properly delete or start the maintenance plan.
Adjust the settings of the computer name (Control panel - System) accordingly.
First, you have to adjust the respective INI files used by BMD NTCS.
You can find BMD.ini in the BMD NTCS installation directory. This directory is located on the respective drive (e.g. C:\ or D:\ – Program Files (x86) – BMDSoftware).
BMDGLOBAL.ini is in the same directory as BMD.ini.
You can find BMDClient.ini in the folder ProgramData (hidden).
C:\ProgramData\BMDNTCS\BMDClient.ini
Cab be found in the installation directory of BMD NTCS.
If Exchange synchronisation is enabled, you have to adjust BMDSYNCService.ini accordingly..
Next, you have to adjust the BMD NTCS paths, since they still refer to the old server name.
If you get a notification that there is an available update, you can skip it. Next, the following window opens:
In this menu you can now check how many entries there are under the current path name by entering \\ and tab. This gives you an overview (preview) of the current paths with the old server name. The number of paths can vary (in the screenshot, the old server name is displayed in grey).
When logging in to SQL Server Management Studio, you now need to use the new server name to establish a connection.
If you rename a server on which an SQL instance is installed, you have to enter the following command in the Query Editor of MGMT Studio in order to allow for correct registration of the new computer name.
Please note that after registering the new server name you have to restart the SQL Server to apply the changes!
Now, enter the following command and then click on “Execute” (please insert the respective server name to delete the old server name):
sp_dropserver 'oldservername\bmd'
GO
If you set the command correctly, it will be displayed as “completed successfully” under “Messages”:
The results should no longer include entries of the old server name.
If you deleted the maintenance plan, you now have to set it up again. For this, please refer to our online documentation “Creating an SQL maintenance plan”.
Since the SQL and BMD NTCS services might have been stopped, you have to start them manually. You can do this via “Services/Services on the server”. Check whether the services are already running. In general, SQL Server services are started automatically when you restart the server.
Log in with your user details and then start BMD NTCS with your respective username. If single login is active, you can start BMD NTCS without entering the username.
Due to changing the server name, you now have to check the single login details in BMD NTCS (if you are using single login).
Go to the user administration window in BMD NTCS under TOOLS → Tools → Authorisations → Users. Under “Functions” you can select the option “Check single login file”.
Now, test on your workplace (client) if single login (automatic login to BMD NTCS) works for the user for whom single login is enabled.
In this step, we reinstall BMDNetClient on the desired workplaces. Install the client as usual via the PGM share of the server. In our case, we can share by using \\BMDNTCSNEU (you can, for example, enter this link in the address field of Windows Explorer) → bmdntcs_pgm → BMDNetclient.exe.
Now, start the setup and install BMDNetClient. After installing BMDNetClient, you can start BMD NTCS via the desktop shortcut.
The next step is to check if you can start BMD NTCS on all systems (servers and clients) as before.
Should the login window of BMDNetClient not display any information, these are the possible causes.
If the NetClient that still refers to the old server name is installed on the computer and has not been uninstalled properly before starting BMD NTCS, a white or incomplete login dialogue may appear.
If this is the case, you have to start the client installation via the share on the new BMD NTCS server.
Then, check in the top section of the next window whether the new server name is displayed. This is to ensure that BMDNetClient.exe has been started via the correct share.
In the lower section of the window, you can check if you need additional options like local archive add-ons, etc. (You also have the option to add these later by running the client installation again.)
If you did not make the adjustments as described above, you will get a notification after restarting the server and starting BMD NTCS (including login).
In this case, check all INI files and paths again via DBUpdate.