Verify that an existing Microsoft SQL Database meets Pre-Requisites to use Integrated Windows Authentication to access a remote SQL Server
User Account and domain prerequisites
• The Shavlik Protect console and SQL Server must be joined to the same domain or reside in
different domains that have a trusted relationship. This is so the console and the server can compare credentials and establish a secure connection.
• For security purposes, Shavlik recommends using Windows authentication where possible.
• On the SQL Server, verify that a machine account has been created that represents the Protect Console. It will be in the domain\machinename format. The machine account is the console's machine name and must contain a trailing $ . You should be able to see the machine account under the Security node under Logins. If the machine account exists, right click the machine account and select Properties. Verify that Window authentication is selected and the default database is the one that you use for Protect. Normally the database name is ShavlikScans if you created the database from a Protect 8 installation and Protect if you started with Protect 9. If the machine account does not exist, follow instructions in the Document "Manually Configuring a Remote SQL Server to Accept Machine Account Credentials" Manually Configuring A Remote SQL Server To Accept Machine Account Credentials
A machine account representing the Protect Console must also exist for the specfic Protect database.
For an explanation of the permissions specified above, reference Protect SQL Account Configuration for least privilege requirements http://community.shavlik.com/docs/DOC-1463
The machine accounts described above should have been created automatically during product installation. If the account information is missing follow Instructions in the Document "Manually Configuring a Remote SQL Server to Accept Machine Account Credentials" Manually Configuring A Remote SQL Server To Accept Machine Account Credentials