Exchange Organization name is Invalid

In trying to migrate from Exchange 2003 to Exchange 2010 on a Windows 2008 R2 Server, I am encountering a problem that the Organization name contains Parentheses ().

The Exchange Server is Running in Mixed Mode on Windows Server 2003. About 150 Users and 200 Gig of Data.
This is the Only Exchange Server in the Domain, and it is resident on the Domain Controller.

Is there an easy way to remove the Parentheses from the Organizational name, or to rename the Organization.
Jacques SmithAsked:
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.

Simon Butler (Sembee)ConsultantCommented:
The Exchange Org name is fixed, you cannot change it.
Therefore your only option is a new Forest and then do a cross forest migration.

What surprises me is that you managed to get them in to the name in the first place - they have been invalid since Exchange 2000 days.

Simon.
0
Jacques SmithAuthor Commented:
It was originally and Exchange 5, then migrated to 5.5, 2000 and then Finally 2003. For Some Reason there was no problem in the Migration to 2003, and it has worked perfectly for the last 10 years. Also the Microsoft Exchange Pre-Deployment analyser did not pick up any issues.

I was looking at a simple way, it sounds quite complicated doing a new forest and then cross forest migration. Is there no way to migrate the "Old" Exchange into a new Exchange Server in the Current Active Directory, in a fairly straightforward procedure.

In a Lab environment:
I have already done a migration of the Active Directory onto a new 2008R2 Server, and everything is fantastic, except that the Exchange picked up a problem with the invalid characters.
0
Satya PathakLead Technical ConsultantCommented:
Can you Paste here a complete error message which you are getting.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Jacques SmithAuthor Commented:
Error Message Posted as Requested
2015-04-12-18-55-12.jpg
0
Carol ChisholmCommented:
Hi Jacques
Listen to Sembee, he knows what he is talking about.
There are many things we did in Exchange 5.5 which don't work any more.
I would also recommend you do a bit of reading on the future of Exchange, as we are already on Exchange 2013 SP1 CU something or other.
If you are going to "future proof" your environment you need to look at public folders and all sorts of other fun stuff.
0
Simon Butler (Sembee)ConsultantCommented:
"It was originally and Exchange 5, then migrated to 5.5, 2000 and then Finally 2003. For Some Reason there was no problem in the Migration to 2003, and it has worked perfectly for the last 10 years. "

Exchange 2003 installer didn't do the checks for the name - it was a lot more forgiving.
The name would be fine for working with Exchange 2003, no problems at all, but things move on and the checks become a lot better.

I have done a similar migration in the past and the decision to go to a new forest wasn't taken lightly, but it was something that was done as it allowed a lot of garbage to be removed from the domain, having a huge spring clean. It does have to be planned very carefully, but it will allow you to go to Exchange 2013 immediately, rather than bouncing to Exchange 2010 first, new domain controllers, possible a new name, new conventions. I have seen old domains and they are usually a mess of permissions and structure, often based off NT 4 or even 3.51 conventions and need to be updated.

Simon.
0

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
Seth SimmonsSr. Systems AdministratorCommented:
The Exchange Server is Running in Mixed Mode...

in addition, needs to be native mode for a 2010 migration
right click the org, go to properties, click change mode button
0
Jacques SmithAuthor Commented:
Thanks for the advice, Probably what I did not want to hear.

So now to do a bit of reading up on cross Forest migration
0
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.