BMD NTCS: Changing the server name of a BMD NTCS installation (incl. SQL instance)

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.
 
 

1. Preparations

Please consider before proceeding with the first steps: 

• Expect downtime
  • Due to the adjustments made, you have to plan for some downtime. Depending on resources and performance of your server, downtime can take up to several hours.
• Database backup is optional (for instructions on backing up your database please refer to www.bmd.com/en → Technical documentation) 
• Are other databases active on the server? 
  • BMD cannot be held responsible for the functionality of these databases!
• New server name

2. Uninstalling BMDNetClient

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.

• Start BMDNetClient.exe by right-clicking and selecting “Run as administrator”.
• If the Client is already running, you can restart BMDNetClient.exe via Tools → “Restart as administrator”. 

• Then click on File → Uninstall NetClient. If you use Office add-ins, you have to close all Office applications before uninstalling.

• After successful deinstallation you can continue with the next step.

3. Deleting maintenance plans

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.

• Start SQL MGMT Studio, click on “Management” and select the respective maintenance plan.
• By right-clicking and selecting “Delete”, you can delete the respective plan.
• The new maintenance plan will be set up later, after renaming the server.
   

4. Changing the computer name

Adjust the settings of the computer name (Control panel - System) accordingly. 

• In our example we use the new name “BMDNTCSneu”.
• To apply the new name it is necessary to restart the computer.
   

5. Adjusting configuration files

First, you have to adjust the respective INI files used by BMD NTCS.

5.1. BMD.ini

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).

• Change all server name entries to the new server name.
• To make sure that you do not miss any entries, you can use the “Search and Replace” function of the editor (notepad).
• Enter the old server name.
• Enter the new server name underneath.
• Click on “Replace all”.
• Then save the file. 

5.2. BMDGLOBAL.ini

BMDGLOBAL.ini is in the same directory as BMD.ini. 

• Again, you have the option to use “Replace” to rename the entries as described above.
• Save the file after changing the names. 

5.3. BMDClient.ini 

You can find BMDClient.ini in the folder ProgramData (hidden). 

C:\ProgramData\BMDNTCS\BMDClient.ini 

• Again, you have the option to use “Replace” to rename the entries as described above.
• Save the file after changing the names. 

5.4. BMDSOAPService.ini 

Cab be found in the installation directory of BMD NTCS. 

• Again, you have the option to use “Replace” to rename the entries as described above.
• Save the file after changing the names. 

5.5. BMDSYNCService.ini 

If Exchange synchronisation is enabled, you have to adjust BMDSYNCService.ini accordingly..

• Again, you have the option to use “Replace” to rename the entries as described above. 
• Save the file after changing the names.

6. Changing the paths in the database

Next, you have to adjust the BMD NTCS paths, since they still refer to the old server name. 

• Start BMDDBUpdate.exe in the BMD NTCS installation directory.
• Make sure to select the correct instance name as your database.
• Specify BMD as the user in the login window and do not enter a password, since Windows login will be used. Then click on “Login”. 
• Note: select the respective database here.

If you get a notification that there is an available update, you can skip it. Next, the following window opens:

• Select the option “Change server name and network path” under Extras → Miscellaneous service routines → Change server name and network path.

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).

• The next step is to enter the old server name in the field “Current path name” and the new server name in the field “New path name”. Then, click on “OK”.  Please double-check the spelling of the new server name.

• Next, click on “OK”.
• After doing this, you can check again whether the paths have been set correctly.
• Just enter the new server name in the field “Current path name” to see the entries with the new name in the preview.
• Then close the DBUpdate window by clicking on “Close”.

7. SQL MGMT Studio login

When logging in to SQL Server Management Studio, you now need to use the new server name to establish a connection.

7.1. Registering the new computer name in the SQL Server

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!

• Right-click on BMD database → New Query

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”: 

• Next, enter the following command (insert the respective server name here to register the new server—in this example it is BMDNTCSNEU):
  sp_addserver 'newname\bmd', local
  GO

• Then, restart SQL Server (Restart service). 
• Use the following command to check whether the process was successful. 
  SELECT @@SERVERNAME AS 'Server Name' (replace “Server Name” with your new server name) 

The results should no longer include entries of the old server name.

7.2. Setting up a BMD maintenance plan 

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”.

8. Starting services

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.

9. Starting  BMD NTCS

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.

10. Checking single login (optional)

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.

11. Installing BMDNetClient

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. 

12. Checking if you can start BMD NTCS on all systems

The next step is to check if you can start BMD NTCS on all systems (servers and clients) as before.

13. Troubleshooting: 

13.1. BMDClient login window does not display any information

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.)

• Now, start the installation by clicking on the button “Install”. 
• Please note that installing the client can take a few minutes. 

• After a successful installation, you will be notified. You can then close the BMDNetClient installation window. 

• You can delete any remaining desktop shortcuts to the old BMD NTCS server. In our example, the new desktop shortcut looks like this: 

13.2. Database error / SQL

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.