Solved

LegacyExchangeDN attribute issues

Posted on 2006-10-20
6
342 Views
Last Modified: 2008-01-09
Before starting this question can I ask you not to attempt to answer this unless you are very confident you know how to help me.

Ok, the problem I have is this;

In our production exchange 2003 organisation it has come to light that the organisation name and the organisation name potion of the legacyexchangeDN attribute do not match.  This only came to light when I built a recovery server to restore the exchange IS into.  Although this is has not caused any problems so far in the production environment I want to try and rectify this to prevent future issues and correct this mismatch problem.

Can this be done in the production environment without affecting the current exchange databases? And how would I go about it?

Cheers



0
Comment
Question by:Nael_Shahid
  • 3
  • 3
6 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 17773335
The short answer is that you cannot change those values without disrupting the Exchange org. Last time I saw someone attempt it the entire domain had to be rebuilt. It is one of those settings that has to be set correctly when the Exchange org is created and once set cannot be easily changed.

If you really want to change it then it is a new AD Forest, domain and Exchange Org. Considering that users don't see it in day to day operation it isn't something I tend to bother with. I have clients who have changed their name three or four times (mergers, ltd to plc, flotations etc) and the domain is still in the original name.

Simon.
0
 

Author Comment

by:Nael_Shahid
ID: 17773494
Simon,

Ok thanks for that.

Is there anyway I can get these databases mounted in the recovery server then?

I have renamed the administrative group to mirror the production environment and administrative group potion of the legacyexchangeDN attribute, however the organisation potion of the attribute is incorrect.  I did try to change this portion of the attribute on the recovery server however I must be missing something as I get this error: (note I used LegacyDN.exe to make the change)

=======================================================
Event Type:      Error
Event Source:      MSExchangeIS
Event Category:      General
Event ID:      1088
Date:            20/10/2006
Time:            14:05:53
User:            N/A
Computer:      MAIL
Description:
The information store could not be loaded because the distinguished name (DN) /O=MCKEAG & CO SOLICITORS/OU=MCKEAGS/CN=RECIPIENTS/CN= of message database "First Storage Group\Mailbox Store (MAIL)" does not match the DN of directory /O=MCKEAGS SOLICITORS/OU=MCKEAGS/CN=RECIPIENTS/CN=.

 The database may have been restored to a computer that is in an organization or site different than the original database.

For more information, click http://www.microsoft.com/contentredirect.asp.

==============================================================================
0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 17773531
There are two ways of dealing with this...

The manual way: http://support.microsoft.com/default.aspx?kbid=273863
Then there is a tool that will let you do it as well... http://support.microsoft.com/default.aspx?kbid=324606

Don't be tempted to use either method on production systems - it will cause problems.

I am in the process of writing an article for recovery server use - although the use of a recovery server is limited now to just public folder data. You don't need one for mailboxes - use the RSG instead.

Simon.
0
Integrate social media with email signatures

Is your company active on social media? Do you also use email signatures? Including social media icons in your email signature is a great way to get fans for free. Let all your email users know you’re on social media quickly and easily, in a single click.

 

Author Comment

by:Nael_Shahid
ID: 17773703
Thanks for this Simon.
0
 

Author Comment

by:Nael_Shahid
ID: 17774678
Simon,

If your still monitoring this can you answer this for me.

With regard to the above; could I rename the entire exchange organisation back to its previous name and would this solve the problem?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 17774714
On the production site no.
On the recovery server you should have the Org with the same name as the Production site.
If the original Org wasn't the default name then you have to carry out some of the tasks in the KB articles - there is no getting away from it.

Simon.
0

Featured Post

Want to promote your upcoming event?

Are you going to an event? Are you going to be exhibiting at a tradeshow? Talking at a conference? Using a promotional banner in your email signature ensures that your organization’s most important contacts stay in the know and can potentially spread the word about the event.

Join & Write a Comment

Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now