There may be a few reasons you wish to migrate NetHelpDesk from one SQL instance to another. These include:
· Upgrading from an older version of SQL Server.
· Migrating from an old server to a new one.
· Moving NHD to its own Instance.
There are three options when migrating in NetHelpDesk:
Use an existing SQL Server instance on a different machine, perhaps a dedicated SQL Server, and manually import an existing SQL Server NetHelpDesk database, and manually create/adjust shortcuts.
Create a new SQL Server instance on a different other machine, perhaps a dedicated SQL Server, and manually import an existing SQL Server NetHelpDesk database, and manually create/adjust shortcuts.
Use an existing or a create a new SQL Server instance on a different machine, and upsize a Microsoft Access NetHelpDesk database into a SQL Server NetHelpDesk database.
Whichever option you choose, and whatever the reason, migrating NetHelpDesk is easy to do, and the installer is not needed.
Some initial considerations when migrating from one SQL Server Instance to another:
1. NetHelpDesk supports all versions of SQL Server from Microsoft, version 7 onwards. We merely use 2008 R2 below as an example, and our team can assist if you get stuck.
2. If Microsoft SQL Server is not yet installed on the machine you choose, instructions on how to do this are detailed in this guide.
3. If the SQL Management Studio tool is not yet installed either, a free edition of Database Tools and Management Tools is available for download on the Microsoft website. This is recommended for queries and so on. Alternatively, you can access copies of SQL Management Studio 2008 R2 via our links below:
32 Bit: nethelpdesk.com/sqlms32
64 Bit: nethelpdesk.com/sqlms64
4. NetHelpDesk recommends that you do not use Windows Authentication. Use SQL Server Authentication instead, using a SQL Server Administrator or “sa” account.
The sa account will automatically have full access to the instance you are using, and the databases within that instance. Using the “sa” login credential will ensure everyone on your domain can access NetHelpDesk without issue.
5. The installer will create its own “sa” account for its own SQL instance for you. However, when manually setting up, if you are unaware of the “sa” login credentials, or not sure if one has been created, speak with your SQL Administrator about this account. Alternatively, our Support team can assist with getting this resolve for you.
6. If using an existing instance of SQL Server, and did not setup a ‘sa’ account, the user login you use must have full access to the instance.
7. Some customers are not comfortable using the same sa credentials. You can create another account, or use a separate instance. We can help with all of this. The important thing is the high level of access to the NetHelpDesk DB.
Most important of all: Take a backup of your existing SQL Server database.
As good practice, all activity to the database should be stopped (Agents logged out, NHServer processes stopped), and a copy of your database made.
1. On your existing SQL Instance, launch SQL Server Management Studio, and log in with the sa credentials as detailed above, right click on the NetHelpDesk database, and create a backup.
2. Make sure the backup you make is “Full” and save it to Disk, wherever you like. SQL Management Studio suggests a path, but you can add a new one, and remove this suggested path.
3. Call the file whatever you like, but we suggest something like: “NHDBackupYYYYMMDD.bak”, replacing YYYYMMDD with the year, month and day respectively.
4. Once you have a .bak file of your database, you can now go to your new instance of SQL Server, and there are a few things you need to do first:
For Option M1, if the SQL Server instance is pre-existing, it will need some configuration checks before restoring the NetHelpDesk pre-configured database to it.
Launch SQL Server Management Studio, and login using a high level access login to the instance. If the “sa” account exists, you’ll need to be able to log into the instance with it. When logged in:
1. Right click on the Instance name at the top of the treeview, and select Properties.
2. In the “Select a page” options, select Security and ensure that server authentication is set to SQL Server and Windows Authentication mode.
Launch SQL Server Configuration Manager:
1. In SQL Server Services screen, check the SQL Server Browser’s Start Mode, and if set to Disabled to Automatic. This is changed in the “Service” tab in the Server Browsers properties, accessed by double clicking the entry.
2. In SQL Server Network Configuration > Protocols for (INSTANCE NAME) and double click the TCP/IP protocol name, and on the Protocol tab, set Enabled to Yes.
3. In IP Addresses tab, scroll to bottom of list and under IPAll; ensure:
a) TCP Dynamic Ports is Blank (not zero).
b) Ensure TCP Port is specified as 14331. Click Apply to save.
4. Go back to SQL Server Configuration Manager > SQL Server Services > Restart the SQL Server Service for your instance for changes to take effect.
5. If you have Firewall software (Windows or 3rd Party software) running on the Server, add an exception/incoming rule to allow TCP Port 14331.
Now locate the backup created earlier.
1. Open SQL Management Studio and log into your instance using your “sa” or relevant high level access account.
2. Right click on Databases and left click Restore Database.
3. In the Destination for restore section, in the To database field, enter a name for the database (e.g. NetHelpDesk).
4. In the Source for Restore section, select From device, and set the path by browsing using the ellipsis button.
5. Click Add on the Specify Backup screen.
6. Navigate to the NetHelpDesk.bak file downloaded in Step 1 above
(e.g. …\NetHelpDesk\SQL\NetHelpDesk.bak). Click OK.
7. Ensure the checkbox in the Restore column is selected.
8. Click OK, and then click OK. Again.
9. Once completed, the database will be ready to connect to.
With Option SQL2 or Option SQL 3, the data link file, which links the NetHelpDesk interfaces to the SQL Server database, will need to be updated. The data link file is called NetHelpDesk.udl, and one is automatically created and configured for you if following the installer.
If not, you will have to do this manually. To achieve this:
1. In the …\NetHelpDesk\Win folder, a sample SQL compatible UDL file called SQLServer.UDL can be found.
2. Copy this file and paste into the root of the …\NetHelpDesk folder, and rename it to be called NetHelpDesk.udl.
3. If one already exists, replace that existing file with this one.
4. Double click the file to launch the OLE DB Core Services program to edit.
5. In the Connection tab, specify the name of the server or the IP address, followed by “,14331” or whatever TCP port number you have specified in the Configuration Manager.
6. We strongly recommend that you Use a specific username and password, and use the ‘sa’ account mentioned previously.
7. If you must Use Windows NT Integrated Security, make sure that the users connecting have full access to the SQL Server instance, similar to the ‘sa’ account mentioned previously. If not, the connection will not work.
8. Select the SQL database created above, whether upsized or empty.
9. Test the connection, and you will see the confirmation screen below.
10. If the test does not succeed, switch off the firewall on the server, to ensure this is not blocking connectivity.
11. Any other errors will be mostly due to permissions issues with the login(s) you are using. If using the “sa” account, these rarely, if ever, happen.
Should you have any questions regarding any steps in this guide, please speak with the NetHelpDesk Support Team.
NetHelpDesk is available on a range of devices with industry-leading functionality available throughout.