Chat now with support
Chat mit Support

Collaboration Services 3.10.1 - User Guide

Getting started with Collaboration Services Organizing objects for synchronization Resolving synchronization conflicts Managing the synchronization process Transport management Fine-tuning and maintenance Backup, restore, and troubleshooting Appendix A: Customizing the format of synchronized data Appendix B: Collaboration Services events

Authorization through administrative groups and Internet Information Server (IIS)

The second security level is authorization through Collaboration Services administrative groups and IIS.

To restrict access to administration tasks, Collaboration Services automatically creates and uses two local groups on every Collaboration Services server:

•
ACS Administrator
Members of this group have unrestricted access to the service configuration and can perform all service administration tasks.
•
ACS Users
Members of this group can only view current service settings and statistics; they do not have permission to change any settings or to invoke re-publication.

When the service is installed on a member server or a workstation, local computer groups are created. The administrator can redefine group membership using the Computer Management tool.

If the service is installed on a domain controller, domain local groups are created. Users can be added to or removed from these groups using the Active Directory Users and Computers administrative tool.

* 
NOTE: Members of the local Administrators group on the Collaboration Services server are also implicitly allowed to perform all synchronization service administration tasks, even if they are not members of the Collaboration Services Administrators group.

Web management console

To perform administrative tasks, you need to connect to the Collaboration Services service using the web management console.

To open the Collaboration Services web management console
•
Select Start | Programs | Quest Software | Collaboration Services on the computer where the Collaboration Services service is installed.
Figure 1. The web management console main window

Configuring Collaboration Services

The Configure Branches Wizard, which allows for registering branches in the collaboration structure, automatically displays when you first open the user interface at the HQ forest. For details, see Configuring branch forests .

All the branches and the HQ forest are called synchronization partners.

Configure secure data communication

Collaboration Services provides secure communication between forests by using data encryption and signing. Collaboration Services uses public key files. Each public key file contains the following:

•
Data encryption key
•
SMTP address of the service mailbox for one forest

During Collaboration Services setup, you specify the following:

•
File name and location where the HQ public key file should be saved
•
Password to protect the file

All messages from the HQ forest are encrypted using the encryption key in the HQ public key file.

The public key file of each branch forest is required for the administrator of the HQ forest to register the branch forests in the collaboration structure. The Export Key Wizard, which allows for exporting the branch public key, automatically appears when you first open the user interface in a branch.

To change the settings for data encryption
1
Right-click the Collaboration Services node in the tree, select Properties, and click General.
If for some security reason your encryption key cannot be used any longer, you should generate a new key by clicking the Generate New button.
* 
NOTE: After generating a new encryption key, you must generate a new public key file and distribute it to the other forests so they can update your forest’s key using the Configure Branches or Configure HQ wizard. Until then, communication with other synchronization partners will not be possible.
* 
NOTE: The HQ public key file is not created immediately; rather, it is automatically generated and saved upon setup completion, after the synchronization service is installed and started.
To export the existing public data encryption key to a public key file, click Export.
If running on Windows 2003 platform (or later), you can change the data encryption algorithm. By default, RC4 128-bit symmetric key encryption is used; you can choose to use an AES 256-bit encryption algorithm instead.
* 
NOTE: All synchronization partners should use the same data encryption algorithm. If it is changed, then after all partners make the same change to the selection on this dialog box, all keys must be re-exported and re-registered, and then all collections must be re-published.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen