Typically this means installing the updates to CAS array members one at a time, allowing each one to complete the update and (if necessary) reboot before updating the next member.This tutorial demonstrates how to update a Client Access Server array without causing the entire array to go offline at once.For this tutorial Update Rollup 4 for Exchange Server 2010 RTM is being installed.The first step is to remove the server that is about to be updated from the Network Load Balancing (NLB) cluster.This next batch of commands requires only Exchange Online powershell session (see step 2 above).This last command gets object IDs of all user objects from Office 365 directory where Office attribute is set to “Flexecom”, then uses this object ID list to query Exchange Online mailboxes where External Directory Object ID attribute matches one of the object IDs from Office 365, then finally pipes the mailboxes into a commandlet that performs address book assignments. but it really isn’t all that complicated once you do it one or two times, and it does work great!This next post is going to talk in detail about GAL segmentation setup in Office 365.The original idea was borrowed from this Microsoft blog post, but since not all of the steps were covered there in sufficient detail, I am expanding them here, and adding two specific examples: how to segment GAL based on distribution lists membership, and how to segment GAL based on Office attribute.
This step could be done on one of your ADFS farm servers that has Windows Azure Active Directory Power Shell (WAAD Posh) installed.
There are two ways to take a CAS array member our of the NLB cluster: The difference between the two is that Stop will immediately stop the server regardless of who is currently connected to it, while Drainstop will put the server in a state where it will not accept new connections but will continue serving existing connections until they disconnect.
For urgent updates a Stop command may be necessary, but for planned maintenance a Drainstop has the least potential impact on active client connections to the CAS array.
Verify No Mailboxes Exist on Exchange 2010 Server 3.
Verify any applications are used for Email relaying with Exchange 2010 Server in Receive Connectors 1.