Network Installation

Lucid Recall can be installed as a client server based network install. Lucid's network edition software uses Microsoft® SQL Server to host the database. An 'Express' version of SQL Server is available free from Microsoft® see Microsoft SQL Server® 2008 R2 SP1 - Express Edition. Ensure that the version you download and install is correct for your server and has the management studio available.

If you have an existing version of SQL Server it may be suitable for hosting a Lucid product database. However, if your SQL Server already hosts a critical application such as SIMS or Sophos we would advise that you host the Lucid Recall database on a different SQL Server instance. One of the features of Microsoft SQL Server is that you can install multiple copies of it on the same server or computer. You can name these copies as ‘instances' so they can easily be identified by their name.

If you have only one server and that is a Domain Controller please read the important Security Note "Installing SQL Server on a Domain Controller" from Microsoft®.

Installing SQL server

Installing SQL Server 2008 R2

Figure 1: The Downloaded SQL Server Installation File

Double Click the install file that you have downloaded. Here, we have SQLEXPRWT_x64_ENU.exe and we saved it to the desktop. This will extract the required install files and present the following SQL Server Installation Center menu (see Figure 2). For this procedure we are going to create a new SQL Server installation, so we will choose the top option, New installation or add features to an existing installation.

Figure 2 - Beginning the installation of SQL Server 2008 R2

You will see the following screen now and at various points during the install, this is just telling you that the install is proceeding.

Figure 3: SQL Server Installation Progress Report Dialog

At this point you may be presented with a ‘Rules Check' screen. If all of the Installation rules have been passed the installation will automatically proceed to the next stage, Licence Terms. If any of the rules fail, then you may have to take remedial action, see the MSDN Article: Installation Rules. Next, you will be presented with the Licence Terms dialog box. Assuming that you accept the licence terms, click the ‘I accept' tick box. You also have the option of sending usage data to Microsoft. Click Next to continue.

Figure 4: License Terms

You will be presented with the Feature Selection dialog next (see Figure 5). It is recommended that you install all of the features available in the Feature Selection screen. Therefore, click Select All and then the Next button to continue the install.

Figure 5: Feature Selection

The next screen is the Instance Configuration dialog (see Figure 6), where you can choose the name of your SQL Instance. The default instance name is SQLExpress. If this instance is only going to be used for Lucid products it may be appropriate to rename it to LucidSQL. Click the radio button next to label ‘Named instance' and type in a different name in the text box, e.g. LucidSQL. Then click the Next button to continue.

Figure 6: Choosing A Name For Your Instance

Next is the Server Configuration screen (see Figure 7).

Figure 7: Configuring The Two Services

There are two services required by SQL Server to run on your server. The first of these is called SQL Server Database Engine, which, by default, is set up to run on the Account: NT AUTHORITY\NETWORK SERVICE. The second service is the SQL Server Browser. This service communicates across the network to let other computers know that the SQL Server instance is up and running. This runs under the Local Service account by default. The SQL Server Browser Service Startup Type is disabled by default, change this to Automatic.

If your server is a Domain Controller you will need create new accounts and give them appropriate permissions as you cannot run SQL Server services on a domain controller under a local service account or a network service account. See Installing SQL Server on a Domain Controller for further information.

The next stage is Database Engine Configuration where you can choose the Authentication Mode for SQL Server users.

Figure 8: Database Engine Configuration

Lucid use Mixed Mode, so it is important to click on the radio button adjacent to this option (see Figure 8). To complete this panel, please choose a strong password for the System administrator (sa) account for this SQL Server and enter it on the screen. Note: the password you've just created will be needed again later. If you now want to add other users to the list of System administrators you can do this on the same screen (see Figure 8). Click Next to continue. At the next screen Error Reporting (see figure 9) you can learn more about how you can maintain and update your SQL Server in the future. There is also a tick box which will allow you to send Windows and SQL Server error reports to Microsoft.

Figure 9: Error Reporting

Click Next to continue. The installation will now copy and install various files. You will be presented with the Installation Progress screen.

Figure 10: Installation Progress

You will then be presented with the Installation Complete window.

Figure 11: Installation Complete

You are now at the end of the installation. In Figure 11 you can see there is a web link to useful information for Updates. The base install of SQL Server is now complete, so you can click on the Close button.

Configuring SQL Server

Once you have installed SQL Server, there are a number of settings which need to be set or checked.

Enabling Remote Connections

You must ensure that the SQL Server instance will allow Remote Connections, otherwise your workstations will not be able to connect to the server. To do this run SQL Server Management Studio. Click on Start > All Programs > SQL Server 2008 R2 > SQL Server Management Studio. Enter the Server Name (server name and instance name) that you created earlier. Change the Authentication mode to SQL Server Authentication. Use the ‘sa' Login and enter the password that you created earlier. Click on the Connect button.

Figure 1: Connect To Server

Right click the SQL Server instance from the Object Explorer pane, (see Figure 13) and choose Facets.

Figure 2: Choosing Facets From The Context Menu

Change the Facet to Server Configuration. Ensure that RemoteAccessEnabled is set to True.

Figure 3

SQL Server Configuration Manager

This tool is installed onto the computer's All Programs menu and is used to enabled SQL services and protocols.

Locate it from the Programs listing under the group called Microsoft SQL Server 2008 R2.

Having launched the tool you will see the services required to be run on the server.

The two services: SQL Server and SQL Server Browser need to be enabled and to be running.

If you first look at the settings for SQL Server 2008 Services, both the SQL Server Browser and the SQL Server services for the database instance are not enabled by default after installation.

They can be started or stopped or otherwise configured by right-mouse clicking over them. You can choose to configure both services to run automatically when the computer is started.

To Stop or Start a service, right mouse click on the item under the column header ‘State' and use the small menu which appears to Stop and Start the service.

To change the account under which you are running a service, right mouse click on the item beneath the column header ‘Log On As' and select Properties.

Next, check that the protocols are enabled. It is recommended that you enable TCP/IP and Named Pipes for the SQL Server instance (see below)

Also enable TCP/IP and Named Pipes for the SQL Native Client 10.0 (see below).

Note: If you have installed SQL Server 64 bit edition, there will be two SQL Native Clients installed, a 32 bit and the default 64 bit.

After changing the protocols, restart both SQL Server and SQL Server Browser services as explained above.

Installing SQL Server on a Domain Controller

For security and performance reasons, Microsoft recommend that you do not install SQL Server on a domain controller.

However, If you decide to install SQL Server on a domain controller then as security precaution please review the MSDN article Security Considerations for Installing SQL Server.

Regarding a failover cluster, SQL instances are not supported where cluster nodes are domain controllers.

Read-only controllers (RODC) are a new type of Domain Controller in the Windows 2008. SQL Server is not supported on a read-only domain controller.

Microsoft's current resolution on Promotion and Demotion of Domain Controllers is not to support it. If the server is already a domain controller, SQL Server can be installed. But once SQL Server has been installed, the user will not be permitted to change the DC to a member machine.

According to Books Online regarding installing SQL Server on a Domain Controller 2008:

  • You cannot run SQL Server services on a domain controller under a local service account or a network account.
  • After SQL Server is installed on a computer, you cannot change the the computer from a domain member to a domain controller. You must uninstall SQL Server before you can change the host computer to a domain controller.
  • After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member
  • You must uninstall SQL Server before you change the host computer to a domain member.

When installing SQL Server on a Domain Controller, you will encounter a rule check result that states the following:

Rule "Computer domain controller" generated a warning

Installing SQL Server 2008 on a domain controller is not recommended.

You can continue with the installation at this point. If you do continue you will more than like hit the following error:

Microsoft (R) SQL Server 2008 Setup (10.00.XXXX.XX)

The following error occurred:

Network Service or Local Service is not permitted for the SQL Server Service on a domain controller.

Specify a different account.

You have to create and use a domain Windows account for the service instead of the local built-in accounts like LocalSystem and NetworkService.

Changing the account used by SQL Services

To change the account used by the SQL Server or SQL Server Browser services right mouse click on the 'Log On As' column header.

Now Select 'This account'.

Select 'Browse' and then 'Advanced'.

Click on 'Find Now' to show a list of all available accounts.

Select the domain account you wish to use and click on 'OK' You will then be required to enter the password for that account before it is applied. The SQL service will now run under that domain account.