New Features | Features | Add-On Products | Product Literature | System Requirements
SureSync Support : Windows 2000 & Windows NT 4 DCOM Setup
Note: This document applies to SureSync 4.If you are running Windows XP or Windows 2003 please click here for setup instructions for your operating system.
If you plan to run the SureSync scheduler as a service you must configure DCOM on the machine which will run the scheduler. This is usually the same machine where you run your SureSync jobs.
The SureSync User Account
DCOM is a component of Windows which allows an application to execute using the file permissions of a specified user. You will need to specify a user for the SureSync components to run under in DCOM before running the scheduler as a service. You will want to select or create this account before beginning configuration of DCOM. The user account must have permissions to access the files you are planning to synchronize. We recommend the use of a domain administrator account. If multiple domains are being used then a trust must exist so the account will be recognized on all machines involved in the synchronization.
Note: If you are running the SPIAgent add-on you can specify different accounts to access each machine with. In this instance you can specify a local administrator account for SureSync to use in DCOM and then specify different accounts for agents on the remote machines in Tools\Server Settings.
Once you have selected a user account you must specify the advanced user rights of “log on as batch job” and “logon as service” to the chosen identity. For Windows NT 4.0 this would be specified in the User Manager by going to the "Policies" menu and selecting "User Rights". For Windows 2000 and above it is specified by going to Start\Programs\Administrative Tools\Local Security Policy and then going to “Local Policy” and finally “User Rights Assignment.”
Starting the DCOM Configuration Utility
Start the DCOM configuration program (DCOMcnfg.exe) by going to " Start > Programs > SureSync > DCOM Configuration".
DCOM Configuration - Applications
Warning: Do not attempt DCOM configuration until you have selected a user account as mentioned above. Do not attempt to run the scheduler as a service until DCOM configuration has been completed. The scheduler will not run as a service properly until DCOM configuration has been completed. If you have already selected "Configure scheduler to run as a service" under Tools\Options in SureSync please uncheck that option can click apply before continuing.
When the DCOM configuration utility loads it will open to the "Applications" tab. Scroll down the list of applications until
you find those beginning with the characters "SPI". You will need to configure
"SPIAlrtM.SPIAlertServer", "SPISureSyncFile4.SPIFileSync", and "SPISureSyncSched3.SPIScheduler".
You also need to configure "SPISyncRun.SPISyncJob" if you are planning on using the SyncRun command line utility to run synchronizations.
To configure these components, simply double-click each entry. Then select the "Identity", select "This user", and click the "Browse" button to select your chosen account. Once you have found the account click "Add" and then "OK" to save it. You must then type the correct password for this identity into both password boxes and click "OK".
Remember that Windows does not check these passwords against any list other than the "confirm password" box. Also remember that when the password for this identity changes, you will need to re-configure each application.
DCOM Configuration - Default Properties
On the default properties tab verify that the "Default Authentication Level" is set to "Connect" and that the "Default Impersonation Level" is set to 'Identify".
DCOM Configuration - Default Security
The final step in DCOM configuration is to configure Default Security. This is done on the "Default Security" tab. You must configure "Default Access" and "Default Launch" security.
Note: This is not necessary if you choose to specify launch and access permissions for each SureSync component individually. To do this you would go to the "Applications" tab in DCOM, select each of the three SureSync components, go to the "Identity" tab and specify the same rights mentioned below for launch and access permissions. We recommend using Default Security Permissions to make configuration easier.
For both "Default Access" and "Default Launch" the requirements are the same. Click the "Edit Default" button and add the following identities to the list: the built-in account SYSTEM, the built-in account INTERACTIVE, and the account you configured for the SPI components on the "Applications" tab of DCOM, and any other user accounts which you plan to launch SureSync under.
Note: Some of these identities and others may already be present. Do not remove identities which are already present unless you're sure no other application is using them. Various programs use DCOM and removing rights could cause problems with applications expecting those rights.
Completing Configuration
Now that DCOM configuration is completed, start SureSync and select "Options" from the "Tools" menu. Then on the "General" tab check "Configure Scheduler to run as a service" and click "Apply". You should then receive a message stating that the service was successfully installed. Once this is done bring up services in Windows and start the "SureSync Scheduler Start" service.
Congratulations! You have completed DCOM configuration and set the scheduler to run as a service. The scheduler should now automatically run after a reboot of your machine. It will also stay running when no one is logged into the machine.
Problems
Improperly configured DCOM entries can yield some unobvious errors. If you get errors like "cannot connect to filesync object", you should review your DCOM information.
If you suspect DCOM problems, always check the Windows System Event log for DCOM messages. These will commonly show as "permission denied", "access denied", "unknown user", etc. SureSync may or may not reflect this information in the Job Log.
Contacting Support
If you continue to have problems, please do not hesitate to contact our technical support department for assistance. Click here to contact our Technical Support Team.