Wednesday, July 15, 2009

Don't collocate CWA with OCS...but if you want to, read on....

So I've come across this several times before.....the client is starting to frown when you say that CWA needs to be installed on a separate server and the 'village of servers' begins to grow. The following steps will illustrate how to install CWA on the same server as OCS. There are a few key steps necessary so be sure to read in detail:

Before I get into the specifics, CWA is not officially supported in a collocated configuration. Now onto the meat.....the 2 primary things you need to watch out for is the multitude of IP's you need on the server and how DNS will react to this. Ultimately you're binding as many as 3 IP's to the same NIC which will accept connections to the OS for port 443 among other things. To avoide collision you need to separate OCS from CWA logically as follows:

  • Install OCS as you normally would (Enterprise or Standard; it doesn't matter).
  • If you're setting up CWA for both Internal and External clients you will need 2 additional IP addresses. Add these IP's to the same NIC used for OCS. Oh and if you're using NIC teaming, you may as well undo the team and go back to one card as this isn't a supported configuration (Audio/Video issues will be seen with teamed NIC's).While you're in the TCP/IP properties of your NIC, be sure to uncheck the DNS registration option.
  • If you added the IP's before disabling automatic DNS registration you may need to go back into your DNS server and remove all the A records corresponding to your server. If not, simply remove the single A record for your server. Then, manually add the A record back in to ensure it isn't 'expired' from the DNS server.

Now you're ready to modify OCS:

  • Open the OCS Admin tool.
  • Expand the pool (or server node if you're using Standard Edition) and right-click the node and choose Properties, then Front End Properties.
  • On the General tab, double-click the Addresses section and change the address to reflect the same one you entered in DNS for the server name (pool IP).
  • Next, click the IM Conferencing tab and change the IP address drop-down to the pool IP.
  • Next, click the Telephony Conferencing tab and do the same then click OK to close the window.
  • Right-click the server name again in the OCS Admin tool, navigate to Properties, then Web Conferencing Server properties.
  • Change the IP address to reflect your pool IP then click OK to close the window.
  • Right-click the server again and choose Properties, then A/V Conferencing properties.
  • Change the IP address to reflect your pool IP then click OK to close the window.
  • Right-click the server again and choose Properties, then Application Sharing properties.
  • Change the IP as you've done above.
  • Finally, open IIS and set the port 80 and 443 listeners for the Default Web Site to the pool IP.
  • Reboot your OCS server and make sure all services start properly.

You're now done with the OCS portion and need to begin on the CWA preparation and installation.

  • Create your DNS entries for CWA. If you have a split horizon DNS you'll want to create an internal A record entry (i.e. cwa.contoso.com) pointing to the second IP of the OCS server. Then you'll want to create another A record entry (i.e. cwa.contoso.com) pointing to the public IP being NAT'd to the third IP of the OCS server. What you end up with is something like:

    10.1.1.10 = ocsserver.contoso.com
    10.1.1.11 = cwa.contoso.com
    215.123.154.222 NAT'd to 10.1.1.12 = cwa.contoso.com

That should be it. Now you have IIS bound to specific IP addresses hosting different web sites (Web Components for OCS, CWA for Internal, and CWA for External).

Cheers!

No comments:

Post a Comment