No LB, we have not been able to get our Netscaler to work correctly frontending either Exchange.
On Fri, Apr 3, 2015 at 9:11 AM, Jonathan Raper <[email protected]> wrote: > I would ask the same question as MBS. > > I am working on a similar setup with 2013, O365, and 2007. > > I have two Citrix NetScaler VPX 1000 load balancers in an active/passive > configuration that front end my two 2013 servers, which are identical in > configuration. > > That way, I can take down either 2013 server and no one has a clue that > I am doing anything at all. > > Jonathan > > Sent from my Verizon Wireless 4G LTE smartphone > > > -------- Original message -------- > From: "Michael B. Smith" > Date:04/03/2015 10:02 AM (GMT-05:00) > To: [email protected] > Subject: RE: [Exchange] Exchange 2013 server maintenance question > > Is there a LB in front of the 2013 servers? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Todd Lemmiksoo > *Sent:* Friday, April 3, 2015 8:55 AM > *To:* [email protected] > *Subject:* [Exchange] Exchange 2013 server maintenance question > > > > We have a hybird Exchange setup with two Exchange 2013 CAS/Mailbox servers > fronting our Exchange 2010 CAS servers with two Exchange 2010 Mailbox > servers (DAG). I have a small pilot group in O365, no mailboxes on the > Exchange 2013 servers remaining mailboxes are on the 2010 DAG. > > When I put one of the Exchange 2013 CAS/Mailbox servers into maintenance > mode and reboot the server; what impact will the users experience in > Outlook or OWA? > > > -- > > T. Todd Lemmiksoo > > ------------------------------ > Note: This message and any attachments is intended solely for the use of > the individual or entity to which it is addressed and may contain > information that is non-public, proprietary, legally privileged, > confidential, and/or exempt from disclosure. If you are not the intended > recipient, you are hereby notified that any use, dissemination, > distribution, or copying of this communication is strictly prohibited. If > you have received this communication in error, please notify the original > sender immediately by telephone or return email and destroy or delete this > message along with any attachments immediately. > -- T. Todd Lemmiksoo
