Chat now with support
Chat with Support

Collaboration Services 3.9 - 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:

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.

Web management console

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

Select Start | Programs | Quest Software | Collaboration Services on the computer where the Collaboration Services service is installed.

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:

During Collaboration Services setup, you specify the following:

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.

1
Right-click the Collaboration Services node in the tree, select Properties, and click General.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating