PREMNAIR'S Blog

"..Unnatural work produces too much stress.."

Exchange2010 – OAB/Outlook clients not downloading updated OAB

Issues:

  • Outlook on Cache mode not updating..Disabling Cached mode on client manually fixes the problem.
  • OWA is not affected at all. All changes are instantly reflected in OWA.
  • Deleteing the .oab files in the user app data folder fixes the problem

This is not  a solution to this issue.

Create new OAB and perform the following tasks:

  1. Create new OAB from EMC.
  2. Make sure Web based and Public Folder distribution is enabled.
  3. Restart MS Exchange System Attendant and File Distribution Service.
  4. Update the OAB from EMC and Set it As Default.
  5. Associate the new OAB to Mailbox Database.
  6. Check the location for the .LZX files C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB
    and C:\program files\Microsoft\Exchange Server\V14\ClientAccess\OAB\
  7. Make sure you don’t have web.config file @ .LZX file location.
  8. I hope you are doing full download of the OAB in Outlook.
  9. When you download the OAB, Make sure you uncheck the box“Download changes since last send/recieve”
  10. “Global Address Book” is the only option
After you restart the File Distribution Service on the CAS server, you should be getting the same files from the OAB generating server to the C:\program files\Microsoft\Exchange Server\V14\ClientAccess\OAB\ on the CAS server . You might want to set the logging level to high to see if any errors are generated on the OAB generating server.
 
  • Set-EventLogLevel –Identity LABMBX\MSExchangeSA\* -Level High 
  • Set-EventLogLevel –Identity “LABCASHT\MSExchangeFDS\*” -Level High
 the first one will get the OAB events and the 2nd will get the File Distribution Service events. Dont forget to set the logging back to defaults. After setting the logging, regenerate the OAB and then restart the FDS, check for errors in the corresponding event logs.
 
Wait for 24hours to get the replication

USEFUL links

  • How to troubleshoot the OAB Generation process..click here
  • How Exchange 2007 OAB Files are replicated to a Client Access Server for download…Click here
  • Managing Offline Address Books…Click here
  • Understanding why error code 0X8004010F is thrown when trying to download an OAB..Click here
  • Outlook client OAB download process..Click here
  • Administering the offline address book in Outlook 2003 and Outlook 2007…Click here

April 25, 2012 Posted by | Exchange server 2010, Microsoft, OAB, Public Folder, Software | , , , , , | Leave a comment

Exchange server 2010 CAS array to MAPI load balance – Detailed

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

  1. Create a Client Access array with an FQDN (Fully Qualified Domain Name).
  2. 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
  3. 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.
  4. Configure your load balancing array to load balance the MAPI RPC ports – TCP 135, UDP/TCP 6005-65535; or set static ports
  5. 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 )

[1] Check is there are any pre-created CAS Arrays. PS Command : Get-ClientAccessArray

[2] Create new Client Access Array. Run the Cmdlet in EMS New-ClientAccessArray -Fqdn server.contoso.com -Site “Redmond” -Name “server.contoso.com”

[3] 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!!!

March 28, 2011 Posted by | Active Sync, DAG, ECP, Entourage, EWS, Exchange Management Console, Exchange Management Shell, Exchange server 2010, HTTPS, Hyper-V, IMAP, IP, Mailbox Server Requirements Calculator, Mails, Microsoft, OAB, Office, Office 2010, Office 2011, Office for Mac, Office Professional Plus, Outlook, Outlook Webapps, OWA, POP3, Protocols, Public Folder, Software, TCP, Transport architecture | , , , , , , , , , , , , , , | Leave a comment

Old public folder – How to remove from Exchange server

It is difficult to delete old public folder from EMC. How to do it, use the ADSIEDIT to clear the old ones.

Right click on the folder you want to delete from CN=Exchange Administrative Group, CN=Databases,  and click delete. The go to Active directory Sites and Services and initiate the replication across the domain.

Go to EMC and refresh.

Thats it.

February 12, 2011 Posted by | Active Directory, Exchange Management Console, Exchange Management Shell, Exchange server 2010, Exchange Server Profile Analyzer, Mailbox Server Requirements Calculator, Mails, Microsoft, Public Folder, Windows Server 2008 R2 | , , | Leave a comment

Exchange server 2010 – Symantec 2010 – DAG Backup failed – Scenario/Solution

Here is a typical scenario of a DAG backup failure from Symantec.

If you come across an email alert from the Backup administrator like below,

Not to be panic…click on the attachment and see what the error is..and it should be like below

Then go to details…

Exchange server 2010 DAG backup failed!!! ohhhhhh.. Try to ping the DAG IP address. If no response, Logon to Mailbox server, and open Failover cluster manager.

Remember, DAG’s basics is on clustering. Click on Cluster events

Goto to the Services -> click on Cluster Services and then click Restart.

This will happen when the mailbox server faces “Dirty Shutdown” or Network connection lost.

January 16, 2011 Posted by | DAG, Exchange server 2010, Microsoft, Public Folder, Software, Symantec, Windows Server 2008 R2 | , , , , | Leave a comment

Public folder email forwarding issue!!!

When you have a mail enabled  public folder in your exchange server 2007/2010 environment, you might face issues with email forwarding from the public folder from your user account, where you will get an error “Operation failed”.

Resolution :

  1. Logon to outlook with administrator(Domain) credemtial
  2. Goto the Public folder
  3. Select the folder where you are facing the issue
  4. Right click
  5. Select Properties
  6. Goto Permission TAB
  7. Add users
  8. Check mark the appropriate rights on the “Write” permission area..normally “Edit all” will do the work
  9. Click apply and click ok.

July 19, 2010 Posted by | Exchange Server 2007, Exchange server 2010, Microsoft, Office, Office 2010, Office 2011, Office for Mac, Office Professional Plus, Outlook, Outlook Webapps, OWA, Public Folder, Software | , , , , | Leave a comment

Configure EWS, Autodiscover, OWA, OAB, ECP on Exchange Server 2010

As you all know that the service connectivity for a mail server is the  main concern to all of us. In Exchange server 2010, the connectivity is as same as Exchange server 2007. Once you migrate or install the new version, this should be tested with the proper credentials and certificate..or else, you will end up with your mail server IP going to the blacklist, because of the wrong pointers and configurations. First of all, do the internal test. Go to your computer start bar, right side where Date and time is showing, you will find the Outlook icon, hold Ctrl + right click on the outlook icon and click “Test Email Auto Configuration…”

Select the “Use AutoDiscover” and click Test..

Above one is a success one..If failed, do the below. The Exchange Web Service (EWS) is the web service that allows access to the Out of Office service. If either the internal or external URL for the EWS is missing or incorrect, OOF will fail and other services may not work as expected. Using Exchange Management Shell, check the URLs assigned to the web service virtual directory using the Get-WebServicesVirtualDirectory command

First goto CAS server

Type the following Power Shell command for EWS (Exchange Web Service)

Copy code Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

You will get the result like below

Identity    : ECAS1\EWS (Default Web Site)
InternalUrl : https://mailv.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mailv.domain.com/ews/exchange.asmx

Identity    : ECAS2\EWS (Default Web Site)
InternalUrl : https://mailv.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mailv.domain.com/ews/exchange.asmx

If this is not correct, you need to fix it.. This has to be done on Powershell command on the CAS server.

To do that…Copy code

[PS]C:\Windows\system32>Set-WebServicesVirtualDirectory -Identity “ECAS1\EWS (Default Web Site)” -InternalUrl https://mail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$true

[PS]C:\Windows\system32>Set-WebServicesVirtualDirectory -Identity “ECAS2\EWS (Default Web Site)” -InternalUrl https://mail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$true

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

Identity    : ECAS1\EWS (Default Web Site)
InternalUrl : https://mail.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mail.domain.com/ews/exchange.asmx

Identity    : ECAS2\EWS (Default Web Site)
InternalUrl : https://mail.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mail.domain.com/ews/exchange.asmx

Now you can see that the URL has been fixed. This is for Web Services.

Now for Autodiscovery….

[PS] C:\Windows\system32>Get-AutodiscoverVirtualDirectory

To see the settings

[PS] C:\Windows\system32>Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri

RESULT

[PS] C:\Windows\system32>Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri
Identity                       : ECAS1
AutoDiscoverServiceInternalUri : https://mailv.domain.com/Autodiscover/Autodiscover.xml

Identity                       : ECAS2
AutoDiscoverServiceInternalUri : https://mailv.domain.com/Autodiscover/Autodiscover.xml

To FIX it..

[PS] C:\Windows\system32>Set-ClientAccessServer -Identity ECAS1 -AutoDiscoverServiceInternalUri https://mail.domain.com/Autodiscover/Autodiscover.xml
[PS] C:\Windows\system32>Set-ClientAccessServer -Identity ECAS2 -AutoDiscoverServiceInternalUri https://mail.domain.com/Autodiscover/Autodiscover.xml 

 Now for the Outlook Web Apps, Exchange Control Panel, Exchange ActiveSync, Offline Address book…you have to go to Exchange Management Console (EMC)

  1. Goto one of the CAS server
  2. Open EMC
  3. Goto Server Configuration
  4. Select Client Access
  5. On the Middle top pannel, you can see the CAS server listed.
  6. Select one, on the bottom pannel, you will see like below.

Select each tab and then right click on the object and change the path as required. Once you done with the first CAS servr, do the same for the second as well.

Thats it…you are good to go for production.

July 3, 2010 Posted by | Active Directory, Active Sync, ECP, EWS, Exchange Management Console, Exchange Management Shell, Exchange server 2010, Internet Information Services (IIS), Microsoft, OAB, Office, Office 2010, Office 2011, Outlook, Outlook Webapps, OWA, Public Folder, Software, Transport architecture, Windows Server 2008 R2 | , , , , , , , , | 9 Comments

Exchange Server 2010 Service Pack 1 – Sneak-peak

Exchange Team Blog that provides the first public details about Exchange Server 2010 Service Pack 1 (SP1).  SP1 will of course include fixes and enhancements in the areas customers have helped us identify (including code from all of the Exchange 2010 post RTM update rollups we’ve released to date).  But SP1 will also include some new features and functionality changes, as well….cool

  • A new search preview helps with early case assessment by providing you an estimate on the number of items in the result set-with keyword statistics-before e-mail located in the search are copied to the designated discovery mailbox.
  • And, a new search result de-duplication option, when checked, only copies one instance of a message to the discovery mailbox.

Look at the below  menu for the DAG…what a cool feature it will be

With the release of Exchange Server 2010 last November, Microsoft introduced integrated archiving capabilities aimed at helping you preserve and discover e-mail data. In SP1, this has enhanced its archiving functionality based on the great feedback you’they got since the launch. This includes adding the flexibility to provision a user’s Personal Archive to a different mailbox database from their primary mailbox. This means your organization can now more easily implement separate storage strategies (or tiered storage) for less frequently accessed e-mail. And, we didn’t just stop there! We’ve also added new server side capabilities so you can import historical e-mail data from .PST files, directly into Exchange, as well as IT pro controls to enable delegate access to a user’s Personal Archive.

To help streamline the implementation of retention policies, SP1 updates the Exchange Management Console with new tools to create Retention Policy Tags, so you can automate the deletion and archiving of e-mail and other Exchange items. New optional Retention Policy Tags give you even more flexibility in defining your organizations retention management strategy….coooool

Can’t wait to get hold of this…Announcement blog from Microsoft Exhange Team …click here Yes Virginia, there is an Exchange Server 2010 SP1

Learn more about our approach to archiving by reading the Archiving with Exchange 2010 whitepaper.

Scott Schnoll’s weblog…click here

June 27, 2010 Posted by | Active Sync, Calendar, DAG, ECP, Edge Server, EWS, Exchange Management Console, Exchange Management Shell, Exchange Online, Exchange server 2010, Internet Information Services (IIS), IP Block List, Lync Online, Microsoft, New Service Pack, OAB, Office, Office 2010, Office 2011, Office 365, Office Professional Plus, Outlook, Outlook Webapps, OWA, Public Folder, Social Connectors, Software, Transport architecture | , , , , | 2 Comments

Microsoft Outlook Web apps – Administrator login – new features

Did you know that when you have Exchange 2010 server in your organization and you login through Outlook Web Apps, with administrator account, you have a lot of options to manage and view the entire organization, rather than going through EMC!!!!!

Logon to Outlook Web apps in your organization, and select options on the right side of the screen on top

You get this screen, from there Select “Select what to manage:” and from the drop down menu, select My Organization..and then go to Reporting on the Left pane

Here you can view the queues, delevery status of each users, Public folder status, Mail enabled public folder status etc…!

BUT IF YOU LOGIN AS A NORMAL USER, ALL YOU CAN SEE IS AS BELOW..LIKE

Your organization contact details, Tools for organize mails, Groups belogs to, Settings,  Syncronized phone device to this account, etc…

and a cool feature of Outlook web apps is thaton the right side of the window, where help button is, click on the down arrow of the help icon and you will see “About”..click there and you will see the connectivity of your account with exchange server (good for administrators) like below one

Enjoy!!! i am enjoying it

June 19, 2010 Posted by | ECP, Exchange Management Console, Exchange Online, Exchange server 2010, Microsoft, OAB, Office, Office 2010, Office Professional Plus, Outlook, Outlook Webapps, OWA, Public Folder, Software | , , , | Leave a comment

Exchange server 2007 to 2010 Live migration!!!! Live blog!!! Live Platform…real time scenario!!!

Please find on my blog, one page dedicated to this task…you can see it on my blog top page… or click here

             TO                                          

 MIGRATION…Started on June 8, 2010 ….Today 20th of June..all the objects has been replicated to Exchange 2010..Now the decommissioning starts..Finish too

June 10, 2010 Posted by | Active Sync, Calendar, DAG, DELL, ECP, Edge Server, EWS, Exchange Management Console, Exchange Management Shell, Exchange Pre-Deployment Analyzer, Exchange Server 2007, Exchange server 2010, Exchange Server Profile Analyzer, Facebook, Firewall, Forefront, HTTP, HTTPS, IMAP, Internet Information Services (IIS), iOS4, IP, IP Block List, iPhone, iSCSI, Linkedin, Log Parser, Mailbox Server Requirements Calculator, MailTips, Microsoft, OAB, Office, Office 2010, Office 2011, Office for Mac, Outlook, Outlook Webapps, OWA, Phone, POP3, Protocols, Public Folder, Remote Connectivity Analyzer, SAN, SAN Certificate, Sender Policy Framework, Social Connectors, Software, Threat Management Gateway, Transport architecture, Twitter, Windows 7 phone, Windows Server 2008 R2 | , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , | Leave a comment

Exchange 2010 Mailbox role – installation failed

Error

Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()

This error occurs because the federated built-in e-mail account that links to the computer account no longer exists. Or, the federated built-in e-mail account in the Active Directory directory service is corrupted.

Resolution..go to Active Directory server

  1. Click Start, click Run, type adsiedit.msc, and then click OK.
  2. Locate the Default Naming Context node, and then locate to the CN=Users container.
  3. Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click Delete.
  • Rerun the Exchange Server 2010 Mailbox role setup application.
  • Create a new federated e-mail account by using the following command: (No change in the below command…just type as it is)
    New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
  • Useful link : http://support.microsoft.com/kb/978776

    May 20, 2010 Posted by | DAG, Exchange Management Console, Exchange Management Shell, Exchange server 2010, Mailbox Server Requirements Calculator, Microsoft, OAB, Public Folder, Transport architecture | , | Leave a comment

       

    Follow

    Get every new post delivered to your Inbox.

    Join 420 other followers

    %d bloggers like this: