지금 지원 담당자와 채팅
지원 담당자와 채팅

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

HQ forest installation

The first step in Collaboration Services deployment is to set up the HQ forest.

* 
NOTE: Carefully consider which forest will serve as the HQ forest, since the Collaboration Services structure can not be changed later without re-deployment.
To set up the HQ forest
1
Using the setup account, log on to the computer where you want to install Collaboration Services and run the Quest Collaboration Services Installation Wizard.
Alternatively, you can run the installation from the command line using the runas command with the appropriate parameters.
* 
NOTE: It is recommended to close all Windows applications before running the setup.
2
On the Welcome screen, click Next.
3
Read and accept the license agreement and click Next.
4
Specify User Information, provide the license file, and then click Next.
5
Select which Collaboration Services features to install and either accept the default path for installation or specify a different folder, and then click Next.
* 
NOTE: It is not recommended to install Collaboration Services on a system volume.
6
Specify the credentials for the service account to be used to start the Collaboration Services service. Click Test to check whether the specified account has a valid mailbox, and click Next.
* 
NOTE: The service account must be mailbox-enabled, and it must be a member of the Local Administrators group on the computer where you install Collaboration Services. The account’s mailbox will be used by the Collaboration Services server for data exchange between the HQ and branch forests. The address of this mailbox will be included in the HQ public key file.
NOTE: The Service Account should have Full Control to the Active Directory container specified in Step 7c below.
7
Specify the partner configuration options:
a
Choose the partner configuration. Since Collaboration Services is being deployed in the HQ forest, select the HQ option.
b
Supply the forest’s description. This description and the service mailbox address will be the only information about your forest available to the administrators of other forests.
c
Select an Active Directory container to store the stub objects created by Collaboration Services for purposes of mail redirection. For more information on how the stub objects are created and used, see the Mail forwarding .
d
Collaboration Services uses the Active Directory extension attributes to mark objects as synchronized and assign collection membership to them. Select any of the 15 extension attributes available. Ensure the selected attribute is not used by any other software.
8
Click Next.
9
Configure notification by specifying who is to receive email messages with all the errors and warnings generated by service.
10
Enter the email address of the recipient in the Send notifications to box (or click Browse to select it), and click Next.
* 
TIP: The email address specified for receiving notifications can be changed using the Email sub-page of Logging page of the Collaboration Services Properties dialog box. For more information about notifications, refer to the Logging section of the Quest Collaboration Services User Guide.
Collaboration Services provides secure communication between forests by using data encryption and signing. Collaboration Services uses public key files, each containing a data encryption key and the SMTP address of the service mailbox for one forest.
11
On the Public Key page, configure the HQ Public Key by specifying a file name and location where the HQ public key file should be saved, and supply a password to protect the file. Click Next.
* 
NOTE: All messages from HQ will be encrypted using the encryption key in the specified public key file.
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.
12
Click Next and wait while the wizard completes the installation of Collaboration Services to the HQ forest.
13
Click Finish to complete the wizard.
* 
NOTE: After you complete the installation of Collaboration Services to the HQ forest, securely transfer the HQ public key file to the branch forest administrators so they can install an instance of Collaboration Services in their forests.

Branch forest installation

Once the HQ forest has been deployed, one instance of Collaboration Services should be installed in each branch forest.

* 
NOTE: Installation of Collaboration Services to the branch forest is not possible without the HQ forest’s public key file.
To install Collaboration Services on a branch forest
1
Using the setup account, log on to the computer where you want to install Collaboration Services and run the Quest Collaboration Services Installation Wizard.
Alternatively, you can run the installation from the command line using the runas command with the appropriate parameters.
* 
NOTE: It is recommended to close all Windows applications before running the setup.
2
On the Welcome screen, click Next.
3
Read and accept the license agreement, and click Next.
4
Specify the user information, provide the license file, and then click Next.
5
Select which Collaboration Services features to install and either accept the default path for installation or specify a different folder, and click Next.
* 
NOTE: It is not recommended to install Collaboration Services on a system volume.
6
Specify the credentials for the service account to be used to start the Collaboration Services service. Click Test to check whether the specified account has a valid mailbox, and click Next.
* 
NOTE: The service account must be mailbox-enabled and must be a member of the Local Administrators group on the computer where you install Collaboration Services. The account’s mailbox will be used by the Collaboration Services server for data exchange between the HQ and branch forests. The address of this mailbox will be included in the branch public key file.
NOTE: The Service Account should have Full Control to the Active Directory container specified in Step 7c below.
7
Configure the Partner by specifying the following:
a
Choose the partner configuration. Since Collaboration Services is being deployed in the branch forest, select the Branch option.
b
Supply the forest’s description. This description and the service mailbox address will be the only information about your forest available to the administrators of other forests.
c
Select an Active Directory container to store the stub objects created by Collaboration Services for purposes of mail redirection. For more information on how the stub objects are created and used, see the Mail forwarding .
d
Collaboration Services uses the Active Directory extension attributes to mark objects as synchronized and assign collection membership to them. Select any of the 15 extension attributes available. Ensure the selected attribute is not used by any other software.
8
Click Next.
9
Configure Notifications by specifying who is to receive email messages with all the errors and warnings generated by service.
10
Enter the email address of the recipient in the Send notifications to box (or click Browse to select it), and click Next.
* 
NOTE: The email address specified for receiving notifications can be changed using the E-mail sub-page of Logging page of the Collaboration Services Properties dialog box. For more information about notifications, please refer to the Logging section of the Quest Collaboration Services User Guide.
Collaboration Services provides secure communication between forests by using data encryption and signing. Collaboration Services uses public key files, each containing a data encryption key and the SMTP address of the service mailbox for one forest.
11
On the Public Key page, click Browse to specify the HQ forest public key file location and provide the password for this file. Click Next.
12
Click Next and wait while the wizard completes the installation of Collaboration Services to the branch forest.
13
Click Finish to complete the wizard.
* 
NOTE: As soon as Collaboration Services is deployed to the branch forest, export the branch public key file and securely transfer this file to the HQ forest so its administrator can register the installed branch forest in the collaboration structure. For details, see “Prepare for Use” on page 31.

Using the ACS Users and ACS Administrators groups

When Collaboration Services is installed on a server, two local groups are automatically created:

•
ACS Users members can view configuration and the current statistics information, but are not allowed to modify any settings.
•
ACS Administrators members have full control over Collaboration Services configuration.

Use these groups to restrict access to Collaboration Services configuration and make the statistics information available to appropriate people in your organization.

* 
NOTE: If Collaboration Services is installed on a domain controller, ACS Users and ACS Administrators will be created as domain local groups.

Test local access

To open Collaboration Services interface on the computer where the service is installed
•
Select Start | Programs | Quest Software |Collaboration Services.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택