サポートと今すぐチャット
サポートとのチャット

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

Unsubscribing from a collection

* 
NOTE: In Collaboration Services 3.6.1 and later the Always create mailbox check box is set by default for Calendar collection subscriptions. Note that the first Exchange server and the first mailbox store are selected automatically from the Exchange environment. If you do not want to use either of these then change them by selecting the drop down icon.
The Exchange server and Mailbox store can be changed later if needed. Once the server and store are changed, it may take up to 24 hours for the move to be completed by Collaboration Services.
To unsubscribe from a collection
•
Select the Collection node in the management tree and select Unsubscribe.
* 
NOTE: If you unsubscribe from a collection, the stub objects created in your forest for that collection's members are hidden from the GAL in your forest. The stub objects are not deleted from the Active Director container they were created in. The stub objects will be automatically deleted after the time interval specified by the Retention time for removed objects parameter. The default period is 30 days.
To change the retention period for these objects
1
In the management console, right-click Collaboration Services and select Properties.
2
Select the Synchronization | Active Directory | General page.
3
Modify the Retention time for removed objects parameter.
* 
TIP: By configuring the Retention time for removed objects parameter, you can delay deleting the stubs for a specified number of days; this will help improve overall collaboration performance and decrease the load on the production environment because if the object is added to another collection during this period, the stub objects will be re-used.

Removing a collection

To remove a collection you published
•
Right-click the collection name in the management tree and select Remove.
* 
NOTE: A collection can be removed only by its publisher.

When a collection is removed by publisher, the following is performed:

1
All subscribing partners get a notification.
2
The stub objects created by Collaboration Services are immediately removed from the Global Address List in all subscribing forests.
3
The stub objects are not deleted from the Active Director container they were created in. The stub objects will be automatically deleted after the time interval specified by the Retention time for removed objects parameter. The default period is 30 days.

Viewing collection settings andsynchronization statistics

Viewing collection settings and
synchronization statistics

The collection settings and synchronization statistics are displayed in the right pane when you select a collection in the management tree. To see the overall statistics for all collections currently published or subscribed to by your forest, select the Publication or Subscription nodes.

The report shows, in particular:

•
General information about the collection: collection name, description, publisher, creation date.
•
Collection membership information: number of objects included in the collection and membership scan statistics.
•
Statistics on Active Directory objects synchronization (if it is configured for the collection): the number of objects added, modified or deleted per week, month, or year; synchronization status and state; and the date and time of the last synchronization.
•
Statistics on Calendar and Free/busy information synchronization (if it is configured for the collection): the number of objects for which this information was synchronized, the number of updates sent, the synchronization status and state, and the date and time of the last synchronization. For more details on synchronization, see Managing the synchronization process .

Advance security of stub objectscreated by the collection

Advance security of stub objects
created by the collection

By default, Collaboration Services creates stub objects with the Password Not Required (PASSWD_NOTREQD) option enabled. This may violate your organization’s security policy and may cause audit software to report a password issue. To resolve this, you will need to update the attribute. In addition, the password should be set to a random value so that the stubs cannot be used to exploit the environment through unauthorized access.

•
Default setting: userAccountControl attribute is set to 546 (0x222): NORMAL_ACCOUNT = 512; ACCOUNTDISABLE = 2; PASSWD_NOTREQD = 32
•
Updated setting: userAccountControl attribute set to 514 (0x202): NORMAL_ACCOUNT = 512; ACCOUNTDISABLE = 2

In Collaboration Services, you can use a registry key to clear the PASSWD_NOTREQD option and set a random password for each stub object as it is created. If the stub already exists, it will clear the option and set the password on the next republish of the collection.

To enable the random generation of a password
•
Create a string value, REG_SZ, called StubAccountPassword in the registry under HKLM\SOFTWARE\Wow6432Node\Aelita\AelitaCollaborationServices
– OR – 
HKLM\SOFTWARE\Aelita\AelitaCollaborationServices for 32 bit systems

The StubAccountPassword should comply with the password complexity policy. Collaboration Services will add a random string and digits to it and generate a password. For example, Z1f9j7Yab$!.

As a best practice, the password template:

•
should not contain common names or number combinations.
•
should not contain meaningful word that will fail the password policy.
•
can contain rules such as; Cannot include firstname, lastname, birthday, and/or userID.

 

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択