Outlook Integration Technical Information

Server

• Works with Exchange 5.0 and later.
• It does not need to run on the Exchange server (although it can), but must be run on a stable workstation.
• The login account at that workstation must have administrator rights to the Exchange server, to enable it to remotely login to the various user accounts.
• Outlook 2000 SP2, Outlook 2002 SP1, or later must be installed at that machine.
• An Outlook profile must be created at that machine for every user whose calendar is to be synchronized.
• The workstation must be able to make an ADO connection to the backend database.

Client

• The client layer creates a new tab visible in Outlook that shows the detailed information for the matter associated with that task/appointment.
• The client side files are automatically updated and maintained by the system’s standard execution procedures for remote installation and administration. (This process requires that the client machine have permission to access the registry – using regsvr32.exe.)

CityLaw/CountyLaw
There are a variety of settings which are used to customize the synchronization process. Those include (but are not limited to):

• Days / Hours of operation of the server component (allowing it be down during automated backups)
• Who to notify when synchronization appears to have stopped functioning
• What interval to use for the synchronization from the system’s master calendar into Outlook
• Whether or not to set reminders on appointments / tasks when inserted by the synchronization process
• Option to restrict changes in Outlook from propagating back over to the system (in essence, to use the ‘CityLaw’ / ‘CountyLaw’ tab in Outlook for additional information purposes only).

All source code is available for review by the IS staff.
More technical information is available in the installation documentation.