locked
OCS Director RRS feed

  • Question

  • Can anyone point me to documentation on setting up an OCS director?

     

    I can't seem to find much in the deployment guides.

    Wednesday, May 2, 2007 12:04 AM

Answers

  •  Inventre wrote:

    Can anyone point me to documentation on setting up an OCS director?

     

    I can't seem to find much in the deployment guides.

     

    Hello,

     

    The OCS_EdgeServerDeploy.doc available for the public beta has the information about deploying the director that you are requesting.

     

    Here's the excerpt from that doc

     

    A Director authenticates inbound requests and distributes them among the servers in the Enterprise pool or to the appropriate Standard Edition Server.
     
    Office Communications Server 2007 supports the following Director configurations:
    A single Standard Edition Server that is configured as a Director.
    An array of Standard Edition Servers that are configured as a Director (requires an Enterprise CA).

    An Enterprise pool that is configured as a Director.

    You deploy a Director in a manner similar to the way that you deploy any other Office Communications Server 2007 server, and you configure it as a Director by using the Deployment Wizard.
    In a load balanced edge server topology (a scaled single-site topology or a multiple-site edge topology), the next hop server on the Director must target the virtual IP address of the Edge Server array’s internal load balancer. Some special configuration steps are required if you choose to deploy an array of Standard Edition servers as a Director. See Appendix A for more information.

    Deploy Your Director

    To deploy a Director in your organization, you need to set up certificates and DNS as you would for any internal Office Communications Server. The following procedure guides you through the process of configuring a Standard Edition Server as a Director.
    To configure a Standard Edition Server as a Director
    1. Configure your DNS records as described in the Office Communications Server 2007 Standard Edition Deployment Guide.
    2. Insert the Microsoft Office Communications Server CD. Setup starts and launches the Deployment Tool. If you are installing from a network share, navigate to the \Setup\I386 folder, and then double-click Setup.exe.
    3. Click Deploy Standard Edition Server.
    4. At Configure Server, click Run.
    5. On the Welcome to the Configure Pool/Server Wizard page, click Next.
    6. On the Server or Pool to Configure page, select the server from the list, and then click Next.
    7. On the SIP domains page, verify that your SIP domain appears in the list box. If it does not, click the SIP domains in your environment box, type your SIP domain, and then click Add. Repeat these steps for all other SIP domains that the Standard Edition Server will support. When you are finished, click Next.
    8. On the Client Logon Settings page, do one of the following:

    a. If the Communicator and Live Meeting clients in your organization will use DNS to locate the pool, click Some or all   clients will use DNS SRV records for automatic logon.
     b. Do not select the Use this server or pool as a Director for automatic logon check box if you are configuring a     Director for external access only. This setting allows internal clients to log on through a Director, and the c. Director then routes requests to the appropriate server or pool.
     If the Communicator clients in your organization will not use DNS to logon to the pool and you plan to manually    configure clients to connect to the pool, click Clients will be manually configured for logon.
    9. When you are finished, click Next.
    10. On the SIP Domains for Automatic Logon page, do one of the following:
     If in the previous step you selected Some or all clients will use DNS SRV records for automatic logon, select the check box for the domains that will be supported by the server for automatic sign-in, and then click Next.
     If, in the step 8, you selected Clients will be manually configured for logon, skip to the next step.
    11. On the External User Access Configuration page, click Do not configure external user access now, and then click Next.
    12. On the Ready to Configure Server or Pool page, review the settings that you specified, and then click Next to configure the Standard Edition Server.
    13. When the files have been installed and the wizard has completed, verify that the View the log when you click ‘Finish’ check box is selected, and then click Finish.
    14. In the log file, verify that <Success> appears under the Execution Result column. Look for <Success> Execution Result at the end of each task to verify Standard Edition Server configuration completed successfully. Close the log window when you finish.
    Deactivate Server Roles and Unnecessary Components (Optional)
    As a security best practice, you should deactivate and uninstall the server roles that that Director does not require. This practice involves deactivating and uninstalling the Web Conferencing, A/V Conferencing and Web Component roles on this server and deactivating the Address Book Server.
     
    To deactivate the roles not required for a Director
    1. Log on to the Director with an account that is a member of the local administrators group and a member of RTCUniversalServerAdmins.
    2. Open the Office Communications Server 2007 Administration tools: Click Start, point to All Programs, point to Administrative Tools, and then click Office Communications Server 2007.
    3. Select one of the following:
    • For a Standard Edition Server, expand Standard Edition Server, expand the Standard Edition that you just deployed:
    1. Right-click the FQDN of the server, point to Deactivate, and then click Web Conferencing and complete the wizard.
    2. Right-click the FQDN of the server, point to Deactivate, and then click A/V Conferencing and complete the wizard.
    3. Right-click the FQDN of the server, point to Deactivate, and then click Web Components and complete the wizard.
    • For an Enterprise pool, expand Enterprise pools, expand the pool that you just deployed:
    1. Expand Web Conferencing, right-click the FQDN of the server, and then click Deactivate and complete the wizard.
    2. Expand A/V Conferencing, right-click the FQDN of the server, and then click Deactivate and complete the wizard.
    3. Expand Web Components, right-click the FQDN of the server, and then click Deactivate and complete the wizard.
     
    To deactivate the Address Book Server
    1. Open a Command Prompt window: Click Start, point to Run and then type cmd.
    2. At the command prompt, type wbemtest.
    3. In Namespace, type root\cimv2, and then click Connect.
    4. Click Enum Classes, and then click OK.
    5. Select MSFT_SIPAddressBookSetting.
    6. Click Instances.
    7. Select your SQL database instance.
    8. Double-click  Outputlocation.
    9. In the Value field, click Null.
    10. Click Save Property.
    11. Click Save Object.
    12. Click Close.

     

     

    Thanks

     

    MIke Adkins OCS Beta Support Team

    Wednesday, May 2, 2007 9:06 PM

All replies

  •  Inventre wrote:

    Can anyone point me to documentation on setting up an OCS director?

     

    I can't seem to find much in the deployment guides.

     

    Hello,

     

    The OCS_EdgeServerDeploy.doc available for the public beta has the information about deploying the director that you are requesting.

     

    Here's the excerpt from that doc

     

    A Director authenticates inbound requests and distributes them among the servers in the Enterprise pool or to the appropriate Standard Edition Server.
     
    Office Communications Server 2007 supports the following Director configurations:
    A single Standard Edition Server that is configured as a Director.
    An array of Standard Edition Servers that are configured as a Director (requires an Enterprise CA).

    An Enterprise pool that is configured as a Director.

    You deploy a Director in a manner similar to the way that you deploy any other Office Communications Server 2007 server, and you configure it as a Director by using the Deployment Wizard.
    In a load balanced edge server topology (a scaled single-site topology or a multiple-site edge topology), the next hop server on the Director must target the virtual IP address of the Edge Server array’s internal load balancer. Some special configuration steps are required if you choose to deploy an array of Standard Edition servers as a Director. See Appendix A for more information.

    Deploy Your Director

    To deploy a Director in your organization, you need to set up certificates and DNS as you would for any internal Office Communications Server. The following procedure guides you through the process of configuring a Standard Edition Server as a Director.
    To configure a Standard Edition Server as a Director
    1. Configure your DNS records as described in the Office Communications Server 2007 Standard Edition Deployment Guide.
    2. Insert the Microsoft Office Communications Server CD. Setup starts and launches the Deployment Tool. If you are installing from a network share, navigate to the \Setup\I386 folder, and then double-click Setup.exe.
    3. Click Deploy Standard Edition Server.
    4. At Configure Server, click Run.
    5. On the Welcome to the Configure Pool/Server Wizard page, click Next.
    6. On the Server or Pool to Configure page, select the server from the list, and then click Next.
    7. On the SIP domains page, verify that your SIP domain appears in the list box. If it does not, click the SIP domains in your environment box, type your SIP domain, and then click Add. Repeat these steps for all other SIP domains that the Standard Edition Server will support. When you are finished, click Next.
    8. On the Client Logon Settings page, do one of the following:

    a. If the Communicator and Live Meeting clients in your organization will use DNS to locate the pool, click Some or all   clients will use DNS SRV records for automatic logon.
     b. Do not select the Use this server or pool as a Director for automatic logon check box if you are configuring a     Director for external access only. This setting allows internal clients to log on through a Director, and the c. Director then routes requests to the appropriate server or pool.
     If the Communicator clients in your organization will not use DNS to logon to the pool and you plan to manually    configure clients to connect to the pool, click Clients will be manually configured for logon.
    9. When you are finished, click Next.
    10. On the SIP Domains for Automatic Logon page, do one of the following:
     If in the previous step you selected Some or all clients will use DNS SRV records for automatic logon, select the check box for the domains that will be supported by the server for automatic sign-in, and then click Next.
     If, in the step 8, you selected Clients will be manually configured for logon, skip to the next step.
    11. On the External User Access Configuration page, click Do not configure external user access now, and then click Next.
    12. On the Ready to Configure Server or Pool page, review the settings that you specified, and then click Next to configure the Standard Edition Server.
    13. When the files have been installed and the wizard has completed, verify that the View the log when you click ‘Finish’ check box is selected, and then click Finish.
    14. In the log file, verify that <Success> appears under the Execution Result column. Look for <Success> Execution Result at the end of each task to verify Standard Edition Server configuration completed successfully. Close the log window when you finish.
    Deactivate Server Roles and Unnecessary Components (Optional)
    As a security best practice, you should deactivate and uninstall the server roles that that Director does not require. This practice involves deactivating and uninstalling the Web Conferencing, A/V Conferencing and Web Component roles on this server and deactivating the Address Book Server.
     
    To deactivate the roles not required for a Director
    1. Log on to the Director with an account that is a member of the local administrators group and a member of RTCUniversalServerAdmins.
    2. Open the Office Communications Server 2007 Administration tools: Click Start, point to All Programs, point to Administrative Tools, and then click Office Communications Server 2007.
    3. Select one of the following:
    • For a Standard Edition Server, expand Standard Edition Server, expand the Standard Edition that you just deployed:
    1. Right-click the FQDN of the server, point to Deactivate, and then click Web Conferencing and complete the wizard.
    2. Right-click the FQDN of the server, point to Deactivate, and then click A/V Conferencing and complete the wizard.
    3. Right-click the FQDN of the server, point to Deactivate, and then click Web Components and complete the wizard.
    • For an Enterprise pool, expand Enterprise pools, expand the pool that you just deployed:
    1. Expand Web Conferencing, right-click the FQDN of the server, and then click Deactivate and complete the wizard.
    2. Expand A/V Conferencing, right-click the FQDN of the server, and then click Deactivate and complete the wizard.
    3. Expand Web Components, right-click the FQDN of the server, and then click Deactivate and complete the wizard.
     
    To deactivate the Address Book Server
    1. Open a Command Prompt window: Click Start, point to Run and then type cmd.
    2. At the command prompt, type wbemtest.
    3. In Namespace, type root\cimv2, and then click Connect.
    4. Click Enum Classes, and then click OK.
    5. Select MSFT_SIPAddressBookSetting.
    6. Click Instances.
    7. Select your SQL database instance.
    8. Double-click  Outputlocation.
    9. In the Value field, click Null.
    10. Click Save Property.
    11. Click Save Object.
    12. Click Close.

     

     

    Thanks

     

    MIke Adkins OCS Beta Support Team

    Wednesday, May 2, 2007 9:06 PM
  • Any problem with deactivating IIS on a director?  I would think this would be a more secure way of disabling the Address Book server and other functions.  Will this affect the server's ability to function as a Director?

    Wednesday, August 1, 2007 1:42 PM
  •  

    Question :

     

    In our environment, we have about 15 SIP domains for different regions around the world.  The pool we are currently creating will only support one of the SIP domains.  If we remove the SIP domains this pool will not support from the list and continue we get an error that we could not remove two or three of them.  What would be your suggestion to use in our case?  Should we continue with the full list already populated, or should we continue with the three or four that it seems to require?  We are at step seven listed below:

     

    7. On the SIP domains page, verify that your SIP domain appears in the list box. If it does not, click the SIP domains in your environment box, type your SIP domain, and then click Add. Repeat these steps for all other SIP domains that the Standard Edition Server will support. When you are finished, click Next.

     

    Wednesday, January 9, 2008 12:19 AM