LegacyExchangeDN attribute issues

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



Nael_ShahidAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SembeeCommented:
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.
Nael_ShahidAuthor Commented:
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.

==============================================================================
SembeeCommented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Nael_ShahidAuthor Commented:
Thanks for this Simon.
Nael_ShahidAuthor Commented:
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?
SembeeCommented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.