Integrated security for a remote server is not supported by the database migration tool: if you specify a remote database server, the migration tool will assume you are using explicit security, and will configure adTempus accordingly. If explicit security is not enabled on SQL Server, adTempus will fail to start because it will not be able to connect to the database.
After you have completed the rest of the migration process (ignoring the failure of the adTempus service to start), you must make the configuration changes described below.
Stop the adTempus service, if it is running, before proceeding.
In the Windows Services
tool, display the properties for adTempus. On the Log
On page, change the service to run under a user account.
The account you select must meet the following requirements:
The account must have the necessary permissions for the adTempus database in SQL Server (must have full permission to read and write data).
The account must be a member of the Administrators group on the computer where adTempus is running.
The account must have the following rights:
Act as part of the operating system
Create a token object
Replace a process level token
To grant the rights, edit the "User Rights Assignment" in the Local Security Policy. If your computer is a member of a domain, or is a domain controller, you may also need to grant these rights in the domain or domain controller security policies.
On the computer where adTempus is installed, run the Registry Editor and go to the key HKEY_LOCAL_MACHINE\Software\Arcana Development\adTempus\Database. Then make the following changes:
Delete the "UserID" and "Password" values under the key.
Edit the "ConnectionString" value, which will look similar to this:
provider=SQLOLEDB; server=myserver;Database=adtempus_test1
Add the following to the end of the value:
; Integrated Security=SSPI
The value will now appear similar to the following:
provider=SQLOLEDB; server=myserver;Database=adtempus_test1; Integrated Security=SSPI
Now start the adTempus service.