Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
라이브 도움말 보기
등록 완료
로그인
가격 산정 요청
영업 담당자에게 문의
제품 번들을 선택했습니다. 귀하의 요청에 더 적합한 서비스를 제공해 드릴 수 있도록 개별 제품을 선택해 주십시오. *
지금은 채팅에 회신할 수 있는 기술 지원 엔지니어가 없습니다. 즉각적인 서비스를 받으려면 당사의 서비스 요청 양식을 사용하여 요청을 제출하십시오.
다음 문서의 설명에 따라 문제를 해결할 수 있습니다.
After you verify that the test collection is synchronizing properly for several days, you can start synchronization for all users. You can either create new collections, or edit the test collection settings to include all users.
If you have manually changed the default timeouts when publishing the test collection, do not forget to adjust the options back to the recommended values.
You may want to fine-tune the interaction between Active Directory, Exchange, and Collaboration Services instances using the synchronization settings. The default settings are good for most environments; however, you may want to optimize them for your own environment. For example, if your Active Directory data is updated rarely, you can increase the Query AD for changes value. Or you may want to restrict Active Directory and Exchange server access during the busiest production hours by using scheduling.
When creating a collection, either proceed with the All attribute preset (it is selected by default), or individually select the attributes to be published for each object class, depending on your requirements.
When publishing all users to be synchronized, it is not recommended to specify any user accounts explicitly or through group membership for performance reasons. Collaboration Services provides dynamic object selection so you can use the OU structure and LDAP filters to select the objects to be published.
By default, group members are not synchronized when you publish a group. You can change the group’s settings to make the group members be synchronized; however, this is not recommended for large groups due to performance reasons. If you want to publish large groups, publish them separately from their members. For large deployments, it is also recommended to place users and groups in separate collections and synchronize these collections in the following order: first the user collection, and then the group collection.
Verify that the stub user accounts are created in the proper location and that users are published in the Exchange GAL. The stub objects for each collaboration partner are created in the dedicated OUs (within the OU specified during the setup).
You can monitor the stub objects as follows:
You can monitor the creation of free/busy and calendar information using Microsoft Outlook or Outlook Web Access.
You can also use Collaboration Services statistics and events to view the current state of the service and the synchronization status.
The initial synchronization may take considerable time. This time depends on numerous conditions, including Collaboration Services settings (such as bandwidth quotas and timeouts), the total number of published objects, and network and server load.
계열사 지원 사이트에서 Quest *제품*에 대한 온라인 지원 도움말을 볼 수 있습니다. 올바른 *제품* 지원 콘텐츠 및 지원에 연결하려면 계속을 클릭하십시오.
The document was helpful.
평가 결과 선택
I easily found the information I needed.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center
Quest Software 포털은 더 이상 IE 8, 9, 10을 지원하지 않습니다. 브라우저를 최신 버전의 Internet Explorer나 Chrome으로 업그레이드하는 것이 좋습니다.
IE 11로 업그레이드 여기를 클릭
Chrome으로 업그레이드 여기를 클릭
IE 8, 9 또는 10을 계속 사용할 경우 당사가 제공하는 뛰어난 셀프서비스 기능 모두를 최대한으로 활용하실 수 없습니다.