Chatta subito con l'assistenza
Chat con il supporto

Collaboration Services 3.10.1 - Deployment Guide

About this document About Collaboration Services Architecture and functionality Before you begin Platform considerations Pre-installation planning Prepare for use Collaboration Services upgrade Installation checklists Re-installing Collaboration Services Troubleshooting

Security

Collaboration Services provides a high level of security. A special dedicated Exchange mailbox in each forest is used for communication with other synchronization partners. All interactions between the services are encrypted.

Each synchronization partner has a password-protected public key file. The public key file (*.akf) contains the email address of the Collaboration Services mailbox used by the partner and the public key for data decryption.

The public key file of the HQ forest is generated during the installation of Collaboration Services in the HQ forest. When you install Collaboration Services in a branch forest, Collaboration Services prompts you for the HQ public key file. Installation of a new branch is impossible without the HQ public key file.

After a branch is installed, the branch administrator needs to export and securely transfer the branch’s public key file to the HQ forest administrator, who can then register the branch in the collaboration structure.

Mail forwarding

For each published object, Collaboration Services creates a stub object (disabled user account) in the forests that subscribe to the published object’s collection. For mail-enabled users and contacts included in the collection, the redirectors are already established, and therefore, Collaboration Services simply sets and populates the proxy addresses and the target address of the original object to the corresponding attributes of the stub object.

For mailbox-enabled users, Collaboration Services assigns the following addresses to each stub object:

•
The targetAddress attribute of the stub object is set according to the namespaces settings in the publishing forest. For more information, see the Namespaces Usage section of the Quest Collaboration Services User Guide.
•
The primary SMTP address of the original object is assigned as a primary SMTP address of the stub object.
•
The secondary SMTP addresses of the original object, if they exist, are assigned as secondary SMTP addresses of the stub object.
Figure 4. Mail forwarding

A user who wants to send a message to a user from another forest just selects the recipient (Collaboration Services stub) from the Global Address List (GAL) and sends the message. As soon as a message is sent, Exchange server verifies the targetAddress attribute value and redirects the message to the other forest.

* 
NOTE: You need to have all necessary connectors established from your Exchange organization to the original object’s organization so Exchange server can redirect messages correctly.

External mail always comes directly to the original object and does not use the Collaboration Services stubs.

Administrative interface

All Collaboration Services administration is performed through a web interface. Extensive statistics provided by the web interface help you track the synchronization activities and provide all the information needed for effective administration.

Figure 5. Web interface

 

 

Before you begin

This section describes what you need to do before installing Collaboration Services. The pre-installation checklist will also help with these preparations.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione