
Congure remote database security
If the database was installed remotely from the Security Manager service, the database must be congured to
allow access by the service.
The Security Manager service runs as NT AUTHORITY/NETWORK SERVICE. When the service accesses the Security
Manager database across the network, it uses the service computer’s credentials, which is an account named
<Domain Name>\<Computer Name>$. The dollar symbol ($) symbol must be appended to the computer name.
For the Security Manager service to access the database, use Microsoft SQL Server Management Studio to add
the computer account to the logins for this database instance, add this account as a user for the database, and
make this account an owner of the database.
NOTE: Microsoft SQL Server Management Studio Express is a free tool available from Microsoft. The tool for
Microsoft SQL Server 2014 or Microsoft SQL Server 2014 Express can be obtained from the Microsoft download
site.
In the following steps, the computer account is AUTH\hpsmserver$, where AUTH is the domain name,
hpsmserver is the computer name, and the dollar symbol ($) is appended to the computer name.
1. Log on to the computer where the Microsoft SQL Server instance is installed.
2. To start Microsoft SQL Server Management Studio, click Start, and then select All Programs. Select
Microsoft SQL Server, and then click SQL Server Management Studio.
3. Select the database instance where the Security Manager database is installed.
4. Expand the Security folder.
5. Right-click Logins, and then select New Login.
6. Enter the account name in the Login name eld. In this example, the login name is AUTH\hpsmserver$.
7. From the Select a page panel, click User Mapping.
8. From the Users mapped to this login table, select the check box for HPIPSC.
9. From the Database role membership for: HPIPSC panel, select the check box for db_owner.
10. Click OK to save the changes and then exit.
42 Chapter 2 Install, upgrade, congure, or uninstall Security Manager ENWW
Komentáře k této Příručce