Thursday, 15 November 2012

Exchange 2010 Public Folder is not visible in Outlook and OWA ?

I have faced this issue in one of my reputed client environment. I will definetly share the public folder topology they are using but not client name :).
So client has 2 Exchange Server , 1 is in US which primary Exchange 2010 Server and other is in Australia which is secondary  or DR (Disaster Recovery) site and only comes in picture when primary one is unavailable.
Since few days their DR site was unavailable so synchronization has been stopped between both PF databases which lead to a problem that is Public folder has been inivisible(or not displaying ) from outlook and owa pane.
when user was trying to view it.. the error was , it can't display the same.
To fix the issue we followed below steps :-

a) Go to Exchange Management console .
b) opened Public Folder management Console and created new Public folder.
c) Checked at Outlook and OWA and found that new PF is visible at both place.
d) Checked the Replication tab of PF database from Public folder management console and found that they have added other site database to synchronize and now every public folder database is trying to reach that site. Hence that site was unavailable so that was the reason their public folder had become unavailable.
e) We removed that database and apply the setting.
f) We check at OWA and Oultook now all public folder were visible without any error.

Amit Rawat
View Amit Rawat's profile on LinkedIn

Thursday, 8 November 2012

Exchange 2010 database drive is full due to Transition logs.

Hi Folks,
Today i am going to discuss a scenario which i faced in a client environment, they have single exchange 2010 environment. They are new on exchange 2010 as they did transition 2 week back from Exchange 2007.
They had around 600 + mailboxes and they did moved them over night which lead to geneate heavy numbers of transition logs on Exchange 2010 and soon their exchange 2010 hard drive was full and database got dismounted. At that moment they didn't have solution what to do . Here we come in picture and followed below steps to provide them solution and got them out from this problem without loosing any data.
Before jumping into action , there are few points we all need to take care of as follows:-

a) Always take full backup of source server  before starting the transition.
b) Always take full  backup of target server after moving the mailboxes.
c) Keep thing in mind if your data size is 1 Gig.. then 1 Gig logs will be generated on source and target server.
d) If you think you don't have enough space for logs then please enable circular logging which will overwrite the logs file.(but this feature is not recommended for production

Here are the steps to fix the issue and make database up.
We had moved all logs file in another drive and then try to mount the database. Database got mounted . we immediately restart the IS service and all logs are started creating. All users outlook connections were restored.

Amit Rawat
View Amit Rawat's profile on LinkedIn

Exchange 2007 Vs Exchange 2010.

We had already discussed about Exchange 2003 vs Exchange 2007, Now lets discuss about Exchange 2007 vs Exchange 2010.
Exchange 2010 has some great features and few as same as Exchange 2007 has.
Lets talk about Exchange 2007 features in a glance..
a) 5 new roles. Edge/Hub/Cas/Mailbox/Unified.
b) Clustering CCR/LCR/SCC/SCR.
c) 50 storage capacity.
d) Outlook anywhere.
e) 32 bit for lab and 64 bit for production.
f) Exchange management console and Exchange management Shell.
There so on...

Lets talk about Exchange 2010, what are the best/new features it has.
a) No more clustering.
b) Introduced DAG (Data Availability Group).
c) only 64 bit management tool.
d) No more storage group.
e) Can make 100 databases.
f) 24x7 online defragmentation.
g) Personal Archiving.
h) Enhanceement in OWA features.

Amit Rawat
View Amit Rawat's profile on LinkedIn

Wednesday, 7 November 2012

Exchange 2003 Vs Exchange 2007.

One of my friend asked me question that what are the differences between "Microsoft Exchange 2003 and Exchange 2007". i thought let them consolidate in a blog so that other virtual friend also can take advantage of it.

Microsoft launched many great features in Exchange 2007 those were not available in Exchange 2003.

Let me start what all features are in Exchange 2003 those are no more available in Exchange 2007

a) Routing groups,Link state routing, routing objects are no more in Exchange 2007 because it uses Active directory site-based routing.
b) Intelligent Message Filter feature is no more available in Exchange 2007.
c) Recipient Update Service (RUS) is not more available in Exchange 2007. We need to use Update-AddressList and Update-EmailAddressPolicy shell cmdlets in Exchange 2007 for the same.
d) POP3 /IMAP4 graphical user interface management is not more available in exchange 2007.
e)  SMTP virtual server instances is no more available in Exchange 2007.

Now lets talk about Exchange 2007 features..
a) no more 32 bit exchange application in it. (32 bit is only for testing purpose).
b) Exchange management Shell. you can only do 40% stuff from Exchange Shell.
c) New Exchange Management Console.
d) Unified Messaging  support.
e) Resource mailbox features.
f) Antispam tools.
g) New phase of clustering SCR/CCR/LCR.
h) Outlook Anywhere.
i) Atlast but not least 5 new roles of Servers as follows:- i) Edge transport ii) Hub Tranport iii) CAS iv) Mailbox  v) Unified messaging.

Amit Rawat
Email me :-

Tuesday, 6 November 2012

OAB error : 0x8004010f in Exchange 2010.

I am sharing a case which i faced with one of my client exchange and same we have fixed it.
Problem was ...After transitioning of Exchange  2007 to Exchange 2010. Users were not able to download OAB , most of time either process stuck or hang and give failure result with error code 0x8004010.

Here are the steps what we did to fix the same :-
a) First of all we have removed the Web.config file from OAB folder of new server.
b) We ran command (C:windows\System32\inetsrv\appcmd set config "default web site/OAB" /section:httpredirect /enabled:false-commit:apphost) to disable redirection from OAB virtual directory.

c) We deleted and recreated the OAB Virtual Directory.
d) We took the registry backup and removed the registry WinhttpSettings
(HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinhttpSettings)

e) We added the self replica and updated the Default Offline Address Book and restarted the System Attendant and File Distribution services.
f) We found OAB version 2, 3a and 4 has been created but there was no self replica was added.

g) We deleted all the OAB created by Customer and created altogether new OAB successfully and pointed to database.

h) We were getting event id 9107 that states that OAB generation has been finished but not getting OAB version 2,3a,4.
i) We found LZX files getting generated under the new GUID folder under "ExchangeOAB" folder.
j) We started MS Exchange IS service then we were able to download the OAB successfully

Amit Rawat
View Amit Rawat's profile on LinkedIn

Monday, 5 November 2012

Exchange Backpressure !

I am sure most of you are aware about subject mentioned terms, That is "Back-pressure"... Question is what is "Back-pressure" in exchange.
Let me explain you.. Back-pressure is feature of Exchange server which help you to avoid or prevent any kind of service failure.
How it works ??
let say there is no space in your hard disk so in this case there are 100 % chances of services crash and       shutdown the server unexpectedly .Chances are server doesn't return in previous state even after creating enough space.. Reason Service is crashed and corrupted due to unexpected shutdown or service failure.
therefore Microsoft provided a feature called "Back-pressure" which is obviously a Resource monitoring feature of Microsoft Exchange Transport Service which is exist on Hub Transport and Edge transport Server.
So for example ... you system is out of memory and it is going to crash ... Back-pressure comes in picture and make services unavailable rather then shutting them unexpectedly down.
this way System Admin can create space and then start the service.
Exchange Transport service can detect hard disk space and memory status, which work different on both exchange version.
 Exchange 2007 :- Incoming mails will be stopped and start bouncing in state of Back pressure.

Exchange 2010:- Incoming mails will be still accepted but very slow due to which mail could be bounced.

PS: - This feature is for HUB Transport Server and Edge Server

Amit Rawat
View Amit Rawat's profile on LinkedIn