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

How to re-deploy Collaboration Servicesto another computer from a backup

How to re-deploy Collaboration Services
to another computer from a backup

You may need to re-deploy Collaboration Services on a new computer if the original computer is unavailable due to disaster or hardware failure. To do this, you will need the backup copy of the Collaboration Services installation folder created during a file backup. See Regular file backup .

To re-deploy Collaboration Services on a new computer
* 
NOTE: You must install Collaboration Services to the same path (drive and folder) as the previous installation and specify the same service account with the required permissions as described in the Deployment Guide. The rest of the settings you specify during setup, including creation of new public encryption key will not be in effect. Instead, the settings from the backup will be used.
1
Install Collaboration Services on a new computer.
2
During installation, if a Branch use the latest HQ key from the backup. If an HQ, create a new encryption key file. We are not going to use this key file.
3
Once Collaboration Services is installed, stop and disable all its services (Logging Service, Synchronization Service, and Watchdog Service) using the Services snap-in.
4
Import the entire HKEY_LOCAL_MACHINE\SOFTWARE\Aelita\AelitaCollaborationServices registry key and all subkeys from the backup using regedit.
5
Restore the contents of the Collaboration Services installation folder from the backup and overwrite all the files in the new installation.
6
Enable and start all the Collaboration Services services from the Services snap-in.
7
Start the Collaboration Services management console and create a new backup of configuration data. To do this, right-click the Collaboration Services root node and select Properties. In the Properties dialog box, click the Backup and Restore tab and click the Backup Now button.
8
Re-publish all the collections from all the sides involved (HQ and all branches). To decrease load on HQ server, re-publish collections separately one by one.
* 
NOTE: To republish all collections simultaneously, right-click the Publication node and select Re-publish | Everything.

Troubleshooting

This section describes the some issues you may face during Collaboration Services operations and explains how to resolve them:

Table 4. Troubleshooting
Symptoms
Possible reasons
solution
You see the following message in a particular synchronization partner's statistics:
“Synchronization partner is not responding”
The SMTP connection between forests is configured incorrectly,
- OR -
The encryption key was changed for one of the forests.
Check whether the SMTP channel is working by sending a test email between the service mailboxes of both forests in both directions.
Export the forests’ public key files and re-register both forests using the newly-generated public key files.
Some objects are not available from a collection your forest subscribes to.
The initial synchronization is still being performed.
Wait until the initial synchronization is completed. It could take up to a few days for large collections, depending on the servers’ hardware and network conditions.
One or more objects are not available from a collection your forest subscribes to, but the initial synchronization is already completed.
Some of the objects were accidentally deleted from the Collaboration Services container.
Initiate re-publication of the collection using the Request re-publishing command.
You cannot add newly-added custom attributes, or objects from a newly-added domain to the synchronization.
Collaboration Services reads a forest’s schema only once, during the service start-up. Thus, on-going changes to the schema cannot be detected.
Restart the synchronization service using the Services MMC snap-in.

Repair or uninstall

To repair or remove Collaboration Services
1
From the Start menu, select Control Panel | Add/Remove Programs | Quest Collaboration Services, and select Change.
2
If you need to Repair, click the Options button, select the check boxes next to the required repairs, and then click OK.
The repair wizard will guide you through the repair process.
– OR – 
To completely remove the application, select Remove.
Collaboration Services and the web management console (if installed locally) will be removed.

 

 

Appendix A: Customizing the format of synchronized data

Sometimes publishing or subscribing administrators might want to change the format or appearance of the data they publish or subscribe to. To do that, mappers can be used. A mapper is a plug-in component that changes the appearance of data that you publish or subscribe to.

If you use mappers when creating a collection, the mappers modify the data before it is published, so all subscribers get modified data. If you use mappers while subscribing to a collection, the mappers modify the published data before it is applied to your particular forest.

* 
NOTE: Mappers applied during publication do not modify the original Active Directory objects; only the information to be published is modified before it is distributed to other forests.

Collaboration Services is shipped with the following mappers:

•
displayName mapper
•
Suffix mapper
•
inetOrgPerson to contact mapper
•
SMTP address filter mapper
•
User to Contact mapper
•
Group to Contact mapper

There is one additional mapper available only in Subscriptions:

•
Attribute filter mapper
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen