[ExchangeList] Re: Before Upgrading to 2003 Server - LDF Problem

  • From: "Michael B. Smith" <michael@xxxxxxxxxxxx>
  • To: <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 12 May 2006 10:46:05 -0400

Item (3) is not correct.

 

Certain features of Exchange 2003 require Windows 2003 AD; but Exchange
2003 will, in general, work on Windows 2000 AD quite happily.

 

But I absolutely agree with your other conclusions and recommendations.

 

________________________________

From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of John T (Lists)
Sent: Monday, May 08, 2006 5:34 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Before Upgrading to 2003 Server - LDF
Problem

 

You have 3 problems that are combing to create a super problem:

 

1. Exchange 2000 & 2003 are integrated/rely on Active directory. When
Exchange is installed on a DC, it is a permanent bond that can not be
broken. As far as Exchange is concerned, there is no other DC in the
world.

 

2. Exchange 2000 will not run on Windows Server 2003. Therefore, to
upgrade to Exchange 2003, you must first upgrade Exchange 2000 to
Exchange 2003, and then upgrade the OS.

 

3. Exchange 2003 requires Windows 2003 Active Directory.

 

Super Problem: Since to upgrade to Exchange 2003 you have to first
access Windows 2003 Active directory, and since Exchange is installed on
a DC and it is a permanent bond, you must first upgrade the OS to
Windows 2003 BUT you can not do that because Exchange 2000 will not run
on Windows 2003 and therefore you will not be able to upgrade it to
Exchange 2003.

 

So, IMHO, the recommended course of action is to create a new server
running Windows 2000 and Exchange 2000 and NOT a DC. Migrate mailboxes
to that server. Demote the current Exchange server, uninstall Exchange
and drop the server from the domain. Now, upgrade your Active directory
to Windows 2003. Upgrade Exchange 2000 to 2003 and then upgrade the
underlying OS to Windows 2003.

 

Yes, a lot of work and time. But then again, that is why MS publishes
white papers ahead of time telling people not to install Exchange onto a
DC.

 

John T

eServices For You

 

"Seek, and ye shall find!"

 

-----Original Message-----
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of sunil shah
Sent: Monday, May 08, 2006 1:13 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Before Upgrading to 2003 Server - LDF
Problem

 

John,

  Are you suggesting that I shold install 2003 server as member server
in existing Domain, then upgrade the schema running exchang 2003
/forestprep and /adprep and install exchange 2003 server on member
server in existing exchange site.  Then run replication of public
folder, system folder and all then move mail box using AD user and
redefine the storage group in Active Directory User MMC????

  Thanks for you suggestion...Please Clarify me...

 

Sunny

 

________________________________

From: John T (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx] 
Sent: Monday, May 08, 2006 3:35 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Before Upgrading to 2003 Server - LDF
Problem

OK, I see a major problem here. You have Exchange installed on a DC.
That is both not recommended and problematic.

 

Any way of first installing Exchange on a member server, removing it
from the DC and rebuilding that to get that problem out of the equation?

 

John T

eServices For You

 

"Seek, and ye shall find!"

 

-----Original Message-----
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of sunil shah
Sent: Monday, May 08, 2006 12:11 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Before Upgrading to 2003 Server - LDF
Problem

 

Bruce,

  I know that.  I am having problem running inetorgpersonprevent.ldf
which is in MS KB 314649.  As per MS they suggest to run that prior to
introducing Windows 2003 Domain in existing windows 2000 domain.  So
when I am running that I am receiving following error. (All the way at
the end of this email)

 

Sunny

 

________________________________

From: Bruce J. Rose [mailto:brose@xxxxxxxxxxx] 
Sent: Monday, May 08, 2006 3:08 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Before Upgrading to 2003 Server - LDF
Problem

 

Must have Exchange 2003 to run on Windows 2003

 

________________________________

From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Taylor, George
Sent: Monday, May 08, 2006 2:59 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Before Upgrading to 2003 Server - LDF
Problem

 

Hopefully someone else can give a much better answer than I.  I have not
been through this with my system yet, we go to AD 2003 in a couple
weeks.  I did assist another admin friend of mine on a smaller system
and here is what I remember.

 

She had AD 2000 w/ Exchange 2000, nothing 2003 had been touched yet.
What she did was:

 

Insured she had Schema Admin rights

Insured she was on the console of the Schema master

Enabled Schema updates on the Schema master

Ran the ldifde command with the ldf script copied from a MS KB article

    Sorry, don't remember the exact article right now, but can look it
up for you if needed.

Verified that the 3 or 4 identifiers that get mangled were now correct

Ran the 2003 forestprep and domainprep

 

 

Hope this helps some,

 

George Taylor

Systems Programmer

Regional Health Inc.

 

 

________________________________

From: sunil shah [mailto:sunny@xxxxxxxxxxxxx] 
Sent: Monday, May 08, 2006 12:39 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Before Upgrading to 2003 Server - LDF
Problem

Yes George, I check the group Schemaadmin and administrator is the
member of it.  Also mmc schema snapin I check the permission and admin
has full right.  

 I found the article that tells me that If I have not run 2003 Server
/forestprep then this mangle will not occure if I run Exchange 2003
/forestprep first.  Is that true?  Anyone out there have accomplish this
without running "inetorgpersonprevent.ldf" and running exchange 20003
/forestprep ????

  MS Article KB=325379 Under Title Active Directory forests are not
vulnerable to mangled LDAPDisplayNames for these attributes in following
Case...

  Please anyone who can confirm will be greatly appreciated.

 

Sunny

 

________________________________

From: Taylor, George [mailto:gtaylor@xxxxxxxx] 
Sent: Monday, May 08, 2006 10:16 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Before Upgrading to 2003 Server - LDF
Problem

 

Looks like a rights issue, are you sure your running it as a Schema
Admin?  Just being a member of the Domain Admins group won't do it,
you'll need to be a member of Schema Admins, your "real" administrator
account is by default..  

 

George Taylor

Systems Programmer

Regional Health Inc.

 

 

________________________________

From: sunil shah [mailto:sunny@xxxxxxxxxxxxx] 
Sent: Monday, May 08, 2006 8:04 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Before Upgrading to 2003 Server - LDF Problem

Hi everyone,

  I have asked this before and asking again.  Current setup - 3 Server
all DC and running windows 2000 Enterprise server.  The first server
that was installed with windows 2000 Ent. And Exchange 2000 Ent. With
AD, DNS and IIS (do not ask me why because was already setup before I
joined the company).  On this server I have copied the
inetorgpersonprevent.ldf and try to run it I am getting following error.
I have setup the schema update in mmc also for the server also.  But
when I run the intetorgpersonprevent.ldf, I receive following.

 

Any one has any Idea.?????

 

Connecting to "ds1.amtsolution.com"

Logging in as current user using SSPI

Importing directory from file "inetorgpersonprevent.ldf"

Loading entries

1:
CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=amtsolution,dc=c
om

Entry DN:
CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=amtsolution,dc=c
om

change: modify

Attribute 0) lDAPDisplayName:msExchAssistantName

 

Add error on line 1: Busy

The server side error is "The role owner attribute could not be read."

0 entries modified successfully.

An error has occurred in the program

 

As per other suggestion, I went to other DC and  try on that server and
I receive following error

Connecting to "acctsrv.amtsolution.com"

 

Logging in as current user using SSPI

Importing directory from file "inetorgpersonprevent.ldf"

Loading entries

1:
CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=amtsolution,dc=c
om

Entry DN:
CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=amtsolution,dc=c
om

change: modify

Attribute 0) LDAPDisplayName:msExchAssistantName

 

Add error on line 1: Referral

The server side error is "A referral was returned from the server."

0 entries modified successfully.

An error has occurred in the program

Other related posts: