[Vinojd1]

For what it's worth, here's what we've learned here about implementing Outlook on a Terminal Server for common use by multiple users attaching via Remote Desktop: Outlook gets installed on the terminal server, but then must be configured for each user individually to integrate the RE sunchronization COM add-in. To do that, each individual must be temporarily made part of the Administrator group on the terminal server, their network login used to get onto the server to open outlook (while in their profile) and add in the RE Outlook .dll for synchronization. Once that is done, exit from user's login, log onto the terminal as admin (or an ID with admin rights to that terminal server) and move user into Power User group on the server. Cumbersome, but the only way to do it. In addition, if users wish to keep some of their contacts segregated by whatever distinction (state, city, zip code, based on a specialized query from RE), you can create unique folders under contacts (naming them whatever they wish to coincide with the distinction they designate), run synchronization (which wil pull them into the default Contacts folder [Microsoft limitation]) and then MOVE them into the individualized contacts folders BUT, it is subject to this caveat:
You can synchronize only with contacts in the default Contacts folder in Outlook. New contacts added through the integration are also placed in this folder. If you move linked contacts out of this folder, the connection with Raiser’s Edge constituents is broken