Most of you guys must have experience the scenario when “Outlook connection lost….” even if you have Exchange server 2010 (with Edge, 2 clustered H&C and 2 DAG configured MB) and Outlook 2010 in place. The reason is that, when you are doing a maintenance on one of the H&C, and if the client is connected to that H&C, communication to the MB is lost. The reason for this is that the cluster load balancing on the H&C cluster handler is not in place, even if the cluster name is published in the DNS server.
In Exchange 2007, 5 server roles that performed distinct functions within the Exchange organization. One role in particular – the Client Access server role – introduced a variety of new Web services, including the Availability service, the Auto discover service and Calendar Concierge services.
In Exchange 2010, same 5 server roles exists. However, there are some significant architectural changes and some shift in responsibilities. The most significant change in Exchange 2010, two new services on CAS called the RPC Client Access and Address Book services establish the RPC (Repote Procedure Call) endpoint for MAPI(Messaging Application Programming Interface), NSPI(Name Service Provider Interface) and RFR (Request for Response) client access. This new functionality replaces the RPC endpoints in the Information Store. The RPC endpoint in the Information Store has not been removed in Exchange 2010, but it has been modified to only accept requests from CAS servers. The RPC endpoint for public folder database access remains on the Mailbox server, however, Outlook clients now communicate directly with the RPC Client Access service on the Mailbox Server for public folder database access, and not with the Information Store.
When CAS starts communicating with the Mailbox server, it makes sense to view it as the Client Access server communicating with the Mailbox database via the Mailbox server that hosts the database. This is especially evident in a load-balanced array of Client Access servers and/or where your environment is configured to use Database Availability Groups that are associated with a Client Access server or Client Access server array.
- In a non-load balanced environment, the mailbox database is associated with only a single Client Access server.
- In a load-balanced environment, the Mailbox database is associated with the load balanced array of multiple Client Access servers.
By default, before a Client Access array is configured,
- all databases are associated with a Client Access server in the environment
- the Outlook clients communicate directly with the Client Access server until the association with the database is updated to be the Client Access array.
In order for the clients to utilize a CAS array
- Create a Client Access array with an FQDN (Fully Qualified Domain Name).
- Load balance your CAS servers in a CAS array by whatever method you choose – Both Hardware LB or Windows Network LB are supported load balancers
- Add the Client Access servers within the AD site to a load balanced array and in DNS associate the unique FQDN to the Virtual IP of the load-balanced array.
- Configure your load balancing array to load balance the MAPI RPC ports – TCP 135, UDP/TCP 6005-65535; or set static ports
- Configure the databases to utilize the CAS array… Use the new-clientaccessarray cmdlet to create the CAS array object. Eg: New-ClientAccessArray –Name “Tromso CAS Array” –Fqdn tromso.site.com” –Site “SITEA”
How to Setup!!!..
Goto one of the CAS server where the NLB is ( to read more about New-ClientAccessArray cmdlet, click here )
 Check is there are any pre-created CAS Arrays. PS Command : Get-ClientAccessArray
 Create new Client Access Array. Run the Cmdlet in EMS New-ClientAccessArray -Fqdn server.contoso.com -Site “Redmond” -Name “server.contoso.com”
 Associate databases with this CAS Array –
Use this CMDLet to add mailbox database to CAS array. Add all mailbox databases at once – Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “CASNLB.contoso.com”
Now the best part –
Configuring Outlook 2010 using Auto Discover
If you already configured Outlook client, Close the outlook, then goto Control Panel->Mail and change the Server name to the new CAS NLB name
If you are going to use a new outlook configuration, Auto discover will return the new CAS NLB name.
Thats all folks!!! Enjoy!!!
Microsoft says it’s learned from user feedback about Office 2008 and has tweaked the user interface accordingly in Office 2011. Most notably, there’s a new Ribbon at the top of each document window. The Mac version of the Ribbon doesn’t replace any menu bars, but it does replace Office 2008’s controversial Elements Gallery, which took some fire from Mac users for its size and inflexibility. This new Ribbon is designed to give users quick access to each program’s most commonly used tools. Unlike the Elements Gallery, the ribbon is customizable and, if you want more screen space, completely collapsible. Now users who has volume license can start download the new version from their site and for the rest, it will arrive in time for the 2010 holiday season.
The other big news in Office 2011 is the demise of Entourage and the return of Outlook. The new Outlook will support PST imports (allowing you to move an Outlook installation, including all your old e-mails, from a Windows PC to a Mac). It will also support Microsoft’s Information Rights Management (IRM), which allows senders to specify what recipients can do with messages (print, forward, and so on). Previously-Windows only, IRM is required in some corporate settings.
Microsoft has re-engineered the Outlook message database system to be a series of small files, so it’s more easily backed up with Time Machine and searched in Spotlight. “Outlook’s new database is more reliable, faster, and fully supports Time Machine and Spotlight.
Visual Basic was dropped from Office 2008 in part because it was too technically difficult to port it to the Mac’s then-new Intel CPUs. Microsoft says it began work on that port as far back as 2008—before the last Mac Office shipped. That work is now complete. And the Mac suite will be using the most up-to-date version of Visual Basic, so it’ll be much more compatible with Office for Windows than the Visual Basic in previous versions of Office for Mac.