How do I figure out which CAS server my users are pointing too?
I currently have 2 servers and plan on adding a 3rd and setting up SCR. Im new to the company and inherited everything...Server1 has CAS and Hub role. Server2 has Mailbox and CAS. I plan on adding server3 and making that just a mailbox server and then removing the CAS role from server2. How do I figure out which CAS my users are using and can\should I point them to server1 before removing the CAS role on server2?
May 21st, 2009 8:42pm

Are the two CAS servers setup in an NLB configuration?If so, you should be able to shut the one down.If not, the clients *should* be pointing to a URL for their CAS - something along the lines of https://webmail.company.com. If they hard code a server name, then they are not following best practices.Internally, if you remove the CAS role, the mailbox servers should be able to function just fine, as they know of the other CAS and will use that one.You can check the IIS logs on each CAS, and that should show client connections.Karl
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2009 10:04pm

To add to Karl's comment. You can use the IIS logs to determine the connections. A software like Microsoft Excel or Log parser is good to determine the connections from different clients. (http://www.msexchangegeek.com/#awp::?p=15). There is no command in shell to determine it. If there is any I am not aware if it.MMilind Naphade | MCTS:M | http://www.msexchangegeek.com
May 22nd, 2009 1:41am

Hi Jack, For OWA/POP3/IMAP4 client, you need to update DNS record to have them point to Server1. For example, if the user access OWA by using https://mail.doamin.com/owa, you should point the mail.domain.com to Server1. Note: You may need to update the certificate on Server1 to include mail.domain.com in Common Name or Alternative Certificate Name. For internal domain joined Outlook 2007 client, I would like to explain that the Outlook connects to mailbox Server directly to retrieve messages. Nevertheless, it also needs to contact CAS server to retrieve Free/Busy status, download OAB files and so on. The domain joined Outlook client connects to DC to get the Autodiscover URL from SCP record. Then, it connects to Autodiscover service and obtains the URL for OAB, Free/Busy and so on. As all the information is saved in DC, I think that basically we do not need to change anything. For Outlook 2007 Anywhere client, I think that you need to update the A record for autodiscover.domain.com to point to the Server1. It is because external Outlook 2007 client is not able to contact DC to query SCP record. Note: You may also need to update the certificate on Server1. For more detailed information regarding Autodiscover and Certificate, I suggest you refer to following articles: Certificate Use in Exchange Server 2007 http://technet.microsoft.com/en-us/library/bb851505.aspx White Paper: Exchange 2007 Autodiscover Service http://technet.microsoft.com/en-us/library/bb332063.aspx White Paper: Exchange 2007 Client Access and SSL http://technet.microsoft.com/en-us/library/cc164344.aspx Mike
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2009 11:14am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics