Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Upgrading Exchange 2000 to Exchange 2007

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Installation >> Upgrading Exchange 2000 to Exchange 2007 Page: [1]
Login
Message << Older Topic   Newer Topic >>
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
Upgrading Exchange 2000 to Exchange 2007 - 29.May2007 2:24:25 AM   
alvinkum

 

Posts: 3
Joined: 29.May2007
Status: offline
Hi All,

Upgrading Exchange 2000 to Exchange 2007


Server A - win2000 PDC with exchange 2000 & many services (WINS, DNS, DHCP).
Server B - win2000 Data server.
Server C - New server to be installed with Win2003 X64 & exchange 2007, to replace exchange 2000 in server A.

Before I can DCPROMO.exe onto Server C, I know I need to run Adprep /ForestPrep and Adprep /DomainPrep at Server A to upgrade to Win2003 schema.
 
Question: 1) Will the ADPREP cause any damage to the Exchange2000 Schema?
Question: 2) Do I need to perform any command to upgrade the exchange 2000 schema before or after I run both AdPrep /ForestPrep & Adprep /DomainPrep?
 
Thanks & regards,
AK
Post #: 1
RE: Upgrading Exchange 2000 to Exchange 2007 - 29.May2007 2:01:25 PM   
farisnt

 

Posts: 383
Joined: 9.Jul.2006
Status: offline
Hi Alvinkum
What about the Adprep and Exchange 2003 on Windows 2003 Read this\
http://support.microsoft.com/kb/314649

and what about the Upgrad
read this
http://technet.microsoft.com/en-us/library/a313c016-0e51-466e-a3de-953e1e0d347d.aspx


_____________________________

Talk with all .. Learn from All
MCP - VB - A+

(in reply to alvinkum)
Post #: 2
RE: Upgrading Exchange 2000 to Exchange 2007 - 30.May2007 5:10:29 AM   
alvinkum

 

Posts: 3
Joined: 29.May2007
Status: offline
Hi Farisnt,

Thanks for the information provided.

I setup a test server win2K install with exchange 2000 and try executing the inetOrgPersonfix.idf command but I received an error. Please see below. I try looking up the web but can't found any article to this error.


C:\>Ldifde -i -f inetOrgPersonFix.ldf -c "DC=X" "DC=dummy, DC=com"
Connecting to "demo.dummy.com"
Logging in as current user using SSPI
Importing directory from file "inetOrgPersonFix.ldf"
Loading entries.
Add error on line 3: No Such Object
The server side error is "Directory object not found."
0 entries modified successfully.
An error has occurred in the program


C:\>Ldifde -i -f inetOrgPersonFix.ldf -v -c "DC=X" "DC=dummy, DC=com"
Connecting to "demo.dummy.com"
Logging in as current user using SSPI
Importing directory from file "inetOrgPersonFix.ldf"
Loading entries
1: CN=secretary,CN=Schema,CN=Configuration,DC=dummy, DC=com

Add error on line 3: No Such Object
The server side error is "Directory object not found."
0 entries modified successfully.
An error has occurred in the program

Thanks again for your help & advice.

AK



< Message edited by alvinkum -- 30.May2007 5:46:17 AM >

(in reply to farisnt)
Post #: 3
RE: Upgrading Exchange 2000 to Exchange 2007 - 30.May2007 6:26:43 AM   
alvinkum

 

Posts: 3
Joined: 29.May2007
Status: offline
I think I'm using the wrong script, it should be InetOrgPersonPrevent.ldf not InetOrgPersonFix.ldf as Adprep /forestprep is not execute yet.

Create the InetOrgPersonPrevent.ldf script by copying the following text including the trailing hyphen after "schemaUpdateNow: 1" to Notepad:

dn: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,DC=X
changetype: Modify
replace:LDAPDisplayName
LDAPDisplayName: msExchAssistantName
-

dn: CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,DC=X
changetype: Modify
replace: LDAPDisplayName
LDAPDisplayName: msExchLabeledURI
-

dn: CN=ms-Exch-House-Identifier,CN=Schema,CN=Configuration,DC=X
changetype: Modify
replace: LDAPDisplayName
LDAPDisplayName: msExchHouseIdentifier
-

dn:
changetype: Modify
add: schemaUpdateNow
schemaUpdateNow: 1
-


Will try out it later.


Regards,
AK

(in reply to alvinkum)
Post #: 4
RE: Upgrading Exchange 2000 to Exchange 2007 - 22.Jun.2007 3:04:25 PM   
prumford

 

Posts: 1
Joined: 22.Jun.2007
Status: offline
Hi AK,

Your solution works.

I'm in the same position (trying to prep my AD for a new 2003 Domain Controller as a prerequisite to upgrade from Exchange 2000 to Exchange 2007). I too have been struggling with this script. In fact, I’ve had a hard time understanding EXACTLY what the issue is and how to resolve it. I don’t think the Microsoft Knowledge Base articles are very clear. Having said that, I’m perfectly willing to admit that I might just be thick-headed and that maybe it is all very clear and I just have poor reading skills.

The basic problem here is that I think Microsoft Knowledge Base article 314649 (as previously linked in this discussion) has the wrong instructions. Specifically, Scenario 2 in this article claims to be for those who have Exchange 2000 and have not yet buggered their AD by running the adprep on Windows Server 2003. However Step 3 then talks about how to repair “mangled” objects in AD. Well if if they say that Scenario 2 is for those who haven’t mangled anything yet, then why are they telling me how to un-mangle my AD?

Anyway, to make matters worse, Scenario 2 Step 3 tells you to run a file called inetorgpersonfix.ldf. It didn’t work for me. I think this is for people who’ve already “mangled” their Active Directory. When I ran it, here were my results:

C:\WINNT\iop>ldifde -i -f inetorgpersonfix.ldf -v -c DC=X "DC=mydomain,DC=COM"
Connecting to "server1.mydomain.com"
Logging in as current user using SSPI
Importing directory from file "inetorgpersonfix.ldf"
Loading entries
1: CN=secretary,CN=Schema,CN=Configuration,DC=myals,DC=CA

Add error on line 3: No Such Object
The server side error is "Directory object not found."
0 entries modified successfully.
An error has occurred in the program

C:\WINNT\iop>

Instead, I had to use the inetorgpersonprevent.ldf file which I found on Microsoft Knowledge Base article 325379. Or you can use the inetorgpersonfix.ldf file if you wish and just take out the first three sections.

In my humble opinion, MSKB article 314649 is a little messed up. “Scenario 2” says that it’s for people who have not yet mangled their AD, but then Step #3 in that Scenario goes on as if you’ve already mangled it.

Paul

(in reply to alvinkum)
Post #: 5

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Installation >> Upgrading Exchange 2000 to Exchange 2007 Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts