How do you change from using SQL Authentication to NT Authentication without reinstalling ARS?
Page 1 of 1
How do you change from using SQL Authentication to NT Authentication without reinstalling ARS?
I'm using SQL Server with AR Server and during the inital install, we chose SQL
Server Authentication and specified the password for SA. The SQL Server is going
to change to use Windows NT authentication only, how can I change AR Server to
use NT Authentication with SQL Server without reinstalling ARS and choosing NT
Authentication?
Server Authentication and specified the password for SA. The SQL Server is going
to change to use Windows NT authentication only, how can I change AR Server to
use NT Authentication with SQL Server without reinstalling ARS and choosing NT
Authentication?
giby.varghese@gmail.com- Posts : 107
Points : 222
Reputation : 3
Join date : 2009-11-11
Re: How do you change from using SQL Authentication to NT Authentication without reinstalling ARS?
In short, you will need to do the following:
1. Create a domain account for the AR Server to use to communicate with the SQL Server.
2. Add the domain account as a Login on SQL Server.
3. Make the domain account Login on SQL Server the DBO of the ARSystem database.
4. Add the following parameter to the ar.cfg file:
SQL-Secure-Connection: T
5. Stop the Remedy Action Request System Server service and change the service to start as the domain
account.
6. Start AR services.
In detail:
Step 1: Create a domain account for the AR Server to use to communicate with the SQL Server.
Normally, this domain account would be domain\ARAdmin, however it can be anything you like but should be
dedicated to the purpose of communicating with SQL Server.
Note: AR Mail Services would be an exception. The same account could be used to send email notifications with
MAPI.
Step 2: Using Enterprise Manager, go to the Security folder and highlight Logins. Right-click and choose New
Login. Enter the name of the NT account and specify the domain. Make the default database ARSystem.
Note: Optionally you can just login to SQL Server as the domain account using Query Analyzer. This will
automatically put it in the Security->Logins and then you just have to make it's default database the ARSystem
database.
Step 3: Using Query Analyzer, run the following stored procedure to change the dbo to be the domain\username
you added in step 2:
sp_changedbowner 'domain\ARAdmin', true
Note: This command will fail if all objects in the ARSystem database are not owned by DBO. If this is the case,
note KB 12317.
Step 4: In the AR Server install directory in a sub-folder called CONF, add the following line to the bottom of the
list of parameters:
SQL-Secure-Connection: T
Step 5: Open the services window and stop the Remedy Action Request System Server service. Right-click on
the service and choose Properties. On Windows NT, you have only one window. On Windows 2000, you have a
window with 4 tabs. Go to the LogOn tab. Change the service to start from the Local System Account to the domain\username account you created in Step 1.
Step 6: Start Remedy services.
At this point, the operation should be complete. One consideration may be NTFS directory permissions. It may be
necessary to grant the domain account you created in Step 1 Full Control of the AR Server install directory and
all sub-directories. Also, this account should have Full Control access to the Remedy license file which is normally
located in C:\Program Files\Common Files\Remedy or C:\Program Files\Common Files\AR System.
Related KBs: 12399, 12237, 12317
1. Create a domain account for the AR Server to use to communicate with the SQL Server.
2. Add the domain account as a Login on SQL Server.
3. Make the domain account Login on SQL Server the DBO of the ARSystem database.
4. Add the following parameter to the ar.cfg file:
SQL-Secure-Connection: T
5. Stop the Remedy Action Request System Server service and change the service to start as the domain
account.
6. Start AR services.
In detail:
Step 1: Create a domain account for the AR Server to use to communicate with the SQL Server.
Normally, this domain account would be domain\ARAdmin, however it can be anything you like but should be
dedicated to the purpose of communicating with SQL Server.
Note: AR Mail Services would be an exception. The same account could be used to send email notifications with
MAPI.
Step 2: Using Enterprise Manager, go to the Security folder and highlight Logins. Right-click and choose New
Login. Enter the name of the NT account and specify the domain. Make the default database ARSystem.
Note: Optionally you can just login to SQL Server as the domain account using Query Analyzer. This will
automatically put it in the Security->Logins and then you just have to make it's default database the ARSystem
database.
Step 3: Using Query Analyzer, run the following stored procedure to change the dbo to be the domain\username
you added in step 2:
sp_changedbowner 'domain\ARAdmin', true
Note: This command will fail if all objects in the ARSystem database are not owned by DBO. If this is the case,
note KB 12317.
Step 4: In the AR Server install directory in a sub-folder called CONF, add the following line to the bottom of the
list of parameters:
SQL-Secure-Connection: T
Step 5: Open the services window and stop the Remedy Action Request System Server service. Right-click on
the service and choose Properties. On Windows NT, you have only one window. On Windows 2000, you have a
window with 4 tabs. Go to the LogOn tab. Change the service to start from the Local System Account to the domain\username account you created in Step 1.
Step 6: Start Remedy services.
At this point, the operation should be complete. One consideration may be NTFS directory permissions. It may be
necessary to grant the domain account you created in Step 1 Full Control of the AR Server install directory and
all sub-directories. Also, this account should have Full Control access to the Remedy license file which is normally
located in C:\Program Files\Common Files\Remedy or C:\Program Files\Common Files\AR System.
Related KBs: 12399, 12237, 12317
giby.varghese@gmail.com- Posts : 107
Points : 222
Reputation : 3
Join date : 2009-11-11
Similar topics
» ARERR 313, 332, 333; when opening Change request
» How does the Mid-tier's "Definition Change Check Interval" work?
» How does the Mid-tier's "Definition Change Check Interval" work?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum