Too many things have happened in my life since I last wrote .. I got married .. :) .. I hope everyone will understand that I had much more to do than write .. Another thing that changed, Is the job. I have just started to get settled in my job and life .. Both of them were moving at the speed of light.
Something that did not change is the place where I stay. House number and street address have changed. But the city and state remain as it is.
Life after marriage is much more complicated than exchange. It can be an outage / P1 / Critsit ( meaning : ask someone at MS Support ) if your new boss ( I mean your wife ) is not supportive and understanding.
Getting back to the technical world. One of the errors that I found on the exchange box was :
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9536
Date: 7/10/2009
Time: 3:55:58 PM
User: N/A
Computer: EXBOX01
Description:
An ambiguous Mailbox Guid ecebdef2-4230-4f223-c839-bedfee88849f was found on 0x2 mailboxes in the DS. The store cannot map this Mailbox Guid to a unique user.
In order to find the culprit, Download the tool : ADFind and run this command
adfind -gc -b "" -binenc -f " msExchMailboxGUID={{GUID:ecebdef2-4230-4f223-c839-bedfee88849f}}" -dn
You will know what to do now. Delete the mailbox, reconnect, purge etc. It can vary as per your environment.
Wednesday, July 22, 2009
Friday, January 23, 2009
Exmerge via Script
We can perform bulk exmerge from different mailbox stores on the same exchange server and also schedule it. This sounds cool .. isn't it .. This is true as well.
So how will we do this .. All we need is legacyDN for all users for whom we need to perform exmerge.
How to get it ? One way is to write a script and the other way is csvde
I will explain the second one and if you need the first way then mail me ..
csvde -s-d "ou=users,ou=china,dc=rishimakeiteasy,dc=com" -l displayname,legacyexchangeDN -f exmergedata.txt
The output file exmergedata.txt will have the contents that you need. Open the file is excel and get the desired result. The input file only needs the legacyexchangeDN value.
Step 1 : Create a input file e.g exmergeusers.txt and add all legacyexhangeDN values one per line.
Step 2 : Open exmerge.ini file from the exmerge folder and make the changes to the following sections -
MergeAction
Should be set to the default (which is MergeAction=0) this means that EXMERGE is looking to export only.
SourceServerName
This value needs to the set to the name of the Exchange server that we are going to extracting data from - for example SourceServerName=MyServer
DataDirectoryName
The is the directory where you wish for the PST files to be placed - be mindful that the location needs to have enough space to accomodate the exported files.
FileContainingListOfMailboxes
The FileContainingListOfMailboxes value should be teh patch where you save exmergeusers.txt
Step 3 : Create a batch file e.g exmergestart.bat. Contents of the file are :
C:
CD c:\program files\exchsrvr\bin\
EXMERGE -F EXMERGE.INI -B
Now you are ready to trigger the batch file also it can be added to a schedule task. Remember to do this is off production hours.
So how will we do this .. All we need is legacyDN for all users for whom we need to perform exmerge.
How to get it ? One way is to write a script and the other way is csvde
I will explain the second one and if you need the first way then mail me ..
csvde -s
The output file exmergedata.txt will have the contents that you need. Open the file is excel and get the desired result. The input file only needs the legacyexchangeDN value.
Step 1 : Create a input file e.g exmergeusers.txt and add all legacyexhangeDN values one per line.
Step 2 : Open exmerge.ini file from the exmerge folder and make the changes to the following sections -
MergeAction
Should be set to the default (which is MergeAction=0) this means that EXMERGE is looking to export only.
SourceServerName
This value needs to the set to the name of the Exchange server that we are going to extracting data from - for example SourceServerName=MyServer
DataDirectoryName
The is the directory where you wish for the PST files to be placed - be mindful that the location needs to have enough space to accomodate the exported files.
FileContainingListOfMailboxes
The FileContainingListOfMailboxes value should be teh patch where you save exmergeusers.txt
Step 3 : Create a batch file e.g exmergestart.bat. Contents of the file are :
C:
CD c:\program files\exchsrvr\bin\
EXMERGE -F EXMERGE.INI -B
Now you are ready to trigger the batch file also it can be added to a schedule task. Remember to do this is off production hours.
Blackberry users are not able to send emails or perform address lookup
I am back from a well deservered break and as I wrote in the last blog .. My travel to the woods was great .. the bad part was that I was not well during my stay at the woods .. Life is changing at a great speed .. Both professionally and personally.
I will write about my self after a month ... Lets get on with some t/s.
I encountered a problem that Blackberry users were not able to send emails but were able to recieve. Another thing missing was that the GAL lookup. This was strange and was happening with all users.
On checking the event logs and BB logs I found this :
Event Type: Warning
Event Source: BlackBerry Messaging Agent DNT037 Agent 4
Event Category: None
Event ID: 20265
Date: 1/22/2009
Time: 5:31:50 PM
User: N/A
Computer: DNT037
Description:
{TPI00761} MAPIMailbox::~MAPIMailbox - DeleteAllDeviceSearches (0x00000000) failed
This points to connnectivity of BES server to the exchange. Thus, we need to restart BB services and the issue is resolved.
On digging deep I came to a conclusion that this happens after Exchange servers are patched and rebooted. So as a practice whenever exchange servers are rebooted that should be followed by a reboot of the BES server.
I will write about my self after a month ... Lets get on with some t/s.
I encountered a problem that Blackberry users were not able to send emails but were able to recieve. Another thing missing was that the GAL lookup. This was strange and was happening with all users.
On checking the event logs and BB logs I found this :
Event Type: Warning
Event Source: BlackBerry Messaging Agent DNT037 Agent 4
Event Category: None
Event ID: 20265
Date: 1/22/2009
Time: 5:31:50 PM
User: N/A
Computer: DNT037
Description:
{TPI00761} MAPIMailbox::~MAPIMailbox - DeleteAllDeviceSearches (0x00000000) failed
This points to connnectivity of BES server to the exchange. Thus, we need to restart BB services and the issue is resolved.
On digging deep I came to a conclusion that this happens after Exchange servers are patched and rebooted. So as a practice whenever exchange servers are rebooted that should be followed by a reboot of the BES server.
Subscribe to:
Posts (Atom)