Walkthrough: Connect your internal server with your Edge Servers
Topic Last Modified: 2009-07-11
To connect your internal server with your Edge Server
- Log on to your internal Standard Edition server with an account that is a member of the RTCUniversalServerAdmins group.
- Start the Deployment Wizard by going to setup\amd64\ and double-clicking setupSE.exe.
- On a Standard Edition server, click Deploy Standard Edition Server.
- Next to Configure Server or Configure Pool, click Run.
- On the Welcome page of the Pool/Server Configuration Wizard, click Next.
- On the Server or Pool to Configure page, select the pool or server that you want to configure, and then click Next.
- Continue through the wizard, specifying the settings that are appropriate to your pool or server configuration.
- On the External User Access Configuration page, click Configure for external user access now.
- On the Routing External SIP Traffic page, do one of the following:
- If you plan to route all traffic sent to and from the Edge Servers through a Director, click Route traffic through a Director and, if this is the Director, select the Use this pool or server as the Director for routing external traffic check box, click Next, and then perform the remaining steps in this procedure.
- If you do not plan to route all traffic sent to and from the Edge Servers through a Director, click Route directly to and from internal pools and servers.
- Click Next.
- On the Trusted Access Edge and Web Conferencing Edge Servers page, do one of the following:
- If you are using a Director and are running the wizard on the Director to configure external user access, the entries on this page are not displayed. Proceed to step 13.
- If you do not use a Director, you must enter the internal FQDNs required for your Access Edge service and Web Conferencing Edge service and click Add after each. The FQDNs that you enter on this page are added to the list of authorized Edge Servers on the Edge Server tab in Global Properties. For Litware Inc., this value is ocsedge.litwareinc.com.
- Under Specify the Access Edge Server that internal servers will use to route traffic, do one of the following:
- If you are using a Director, you do not need to specify the Edge Server.
- If you are not using a Director, select the FQDN of the Access Edge service on the Edge Server to which you want all outbound traffic routed from your internal servers.
- If you are using an Edge Server array, enter the FQDN of the VIP that the Access Edge service uses on the internal load balancer.
- Click Next.
- On the Web Conferencing Edge Server page, do the following:
- In Internal FQDN, type the FQDN of each internal interface that the internal servers will use to connect to the Web Conferencing Edge service. For Litware Inc., this value is ocsedge.litwareinc.com.
- In Internal FQDN, type the FQDN of each internal interface that the internal servers will use to connect to the Web Conferencing Edge service. For Litware Inc., this value is ocsedge.litwareinc.com.
- In External FQDN, type the FQDN of each external interface that the external users will use to connect to the Web Conferencing Edge service. For Litware Inc., this value is lm.litwareinc.com.
- Click Add after typing each pair of FQDNs.
- Click Next.
- On the Trusted A/V Edge Servers page, type the FQDN of the internal interface that will be used to connect to the A/V Edge Server in the FQDN box, type the port number to be used for the internal interface in the Port box, and then click Add. For Litware Inc., this value is ocsedge.litwareinc.com. The port to be used is 5062.
- On the A/V Edge Server Used by This Server or Pool page, type the FQDN of the internal interface of the A/V Edge service on the Edge Server that this server or pool will use for A/V authentication. For Litware Inc., this value is ocsedge.litwareinc.com.
- Click Next.
- On the Ready to Configure Server or Pool page, review the settings that you selected, and then click Next.
- On the completion page, click Finish.