Your original post – you mentioned “receive connectors”. Is hub transport also installed?
From: [email protected] [mailto:[email protected]] On Behalf Of Dave Lum Sent: Tuesday, September 9, 2014 3:32 PM To: [email protected] Subject: RE: [Exchange] Patching Exchange I saw this script and planned on running it this evening, sweet! There is no array, it’s an “old CAS” and new CAS. The story is two different people tried to patch/update the current CAS server but were unsuccessful after several hours, hence them telling me to just build a new one and slide it into place. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Tuesday, September 09, 2014 11:19 AM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] Patching Exchange Run the script I posted on my blog today. It lists almost everything relevant to CAS. Pretty much everything should match on the two servers (except for the server names). http://theessentialexchange.com/blogs/michael/archive/2014/09/09/reporting-on-client-access-server-configurations.aspx Do you have an existing ClientAccessArray? (That information is reported as part of Get-ClientAccessServer and Get-ClientAccessArray.) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dave Lum Sent: Tuesday, September 9, 2014 1:58 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] Patching Exchange Steps done today on the new CAS: Change the Autodiscover URL in the Service Connection Point Modified the InternalUrl and External attributes of the EWS Modified the InternalUrl attribute for Web-based Offline Address Book distribution Doing queries of Get-ClientAccessServer, Get-WebServicesVirtualDirectory, and Get-OABVirtualDirectory I see the new CAS now has the same entries as the current CAS (https://webmail.ochin.org in front of those services now). As near as I can tell, doing the steps I have listed below and doing a VIP swap at our firewall are all that remain to being the new box into production. MX record will remain the same as we have Spam Titan’s in front of our Exchange boxes. Tests to verify would be OWA login, ActiveSync login, and Outlook client login (and confirm mail traffic each direction). Anything jump out at anyone as to what I’m missing? The Set-MailboxDatabse command is what will point the mailbox servers at the new CAS, correct? Dave From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Monday, September 08, 2014 6:31 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Exchange] Patching Exchange Build new server Add to domain Install exchange server's CAS role Verify base operation with owa login Do DNS stuff Retire old server Miller time On Sep 8, 2014, at 17:20, "Dave Lum" <[email protected]<mailto:[email protected]>> wrote: As always, thank you all so much! This also means we won't be trying to go from single CAS to CAS array, we'll be sliding a new CAS server in place of the old one. Is it advised to build a new one with the same name, or is it trivial to point to a new CAS server? I currently have a new Exchange 2010 CAs server built and patched, but it’s not fully ready. If it’s easier to build an identically-named/IP CAS box I can do that too, but it would require more downtime. Here are the steps I can find going to a different CAS server name: * Update DNS Alias for autodiscover.domain.org<http://autodiscover.domain.org> * Update DNS for for rpc.domain.org<http://rpc.domain.org> * Remove the "Host A" record from the old client access server in DNS * run Get-MailboxDatabase -Server ex1.domain.org<http://ex1.domain.org> | Set-MailboxDatabase -RpcClientAccessServer ex2.domain.org<http://ex2.domain.org> * Configure Receive connectors identical to the old CAS box I’m missing something I’m sure. Anyone have a link that has step-by step? Dave From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Monday, September 08, 2014 2:30 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] Patching Exchange CAS *must* come first in Exchange 2010. http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of William Robbins Sent: Monday, September 8, 2014 5:24 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Exchange] Patching Exchange We've seen issues where if the CAS isn't updated first/at same level it will fail to connect to the mailboxes. - WJR 🙈🙉🙊 On Mon, Sep 8, 2014 at 4:03 PM, Dave Lum <[email protected]<mailto:[email protected]>> wrote: I have a three-server Exchange Exchange 2010 environment currently - one CAS and two mailbox servers. They are all currently at SP2 update0. Without getting into the why I'm asking, is there any risk in brining the mailbox servers to E2010SP3UR7 while leaving the CAS server where it is? It would be a short-term (few days) scenario but my guy says there may be some reasons to not to have them too far off patching levels. Comments? Dave
