Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 231
  • Last Modified:

Upgrade from Exchange 5.5 to Exchange 2000

I have NT4 server and Exchange 5.5 installed on this server. Now i need to upgrade e-mail system to Windows 2000 with Exchange 2000 Enterprise server. I have new server hardware with Windows 2000 installed, but i can`t join Exch2k to existing exchage group, becouse Exchange 5.5 on NT server without ServicePacks. I can`t install there SP, becous there something wrong with Echange. When i try to install SP, setup says that Exchange server have that SP and setup exits.
Can someone tell me steps to migrate exch accounts from Exchange 5.5 to Exchange 2000 over another exchange 5.5 with SP`s, and can i leave Active directory domain in mixed mode?
0
Stupicz
Asked:
Stupicz
  • 9
  • 8
1 Solution
 
marc_nivensCommented:
The easiest fix is to figure out why the service pack will not install.  Even if its already installed, it should give you a reinstall option.  Can you give us the exact error you're getting and when in setup you're getting it?
0
 
StupiczAuthor Commented:
Yes, i can only reinstall, but when i push reinstall button, setup says, that can`t find World Wide Web Publishing service or something like that.
0
 
marc_nivensCommented:
Can you give the exact error, text, number, and all?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
marc_nivensCommented:
Also if you have uninstalled IIS lately, go delete this registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Setup\Web Connector
0
 
StupiczAuthor Commented:
Yes, i found that key. OK, i will try to set up SP3 after key deletation after some hours, also then i  will see correct error mesages.
0
 
StupiczAuthor Commented:
Thank You marc. Now i have sucesfully installed Exch 5.5 SP4.
Now i try to set up Exch 2000 and join to a existing group, but first time i had errors about AD and DNS. I resloved this problem, now i need to set up Exchange 2000 again and join to existing 5.5 exchange group, but setup says "0x8007203A (8250) The server is not operational"
For information: Exch 5.5 is installed on NT4, Exch 2000 - on Win2000
0
 
marc_nivensCommented:
Make sure the LDAP port for the Exchange 5.5 server is 389.  You will need to check this on both Site/Protocols/LDAP and Server/Protocols/LDAP.
0
 
StupiczAuthor Commented:
Yes. Exchange 5.5 LDAP ports are 389. Also i deleted anything in AD, that contains information about Exchange servers.
0
 
marc_nivensCommented:
Have you verified that you can ping the 5.5 server by name?
0
 
marc_nivensCommented:
Also verify that the 5.5 servers Org and Site name do not contain any of these characters: ~`!@#$%^&*()_+={[}]|\:;"'<,>.?/.
0
 
StupiczAuthor Commented:
wow!
I can ping, but ower interface, that are connected to internet. Now i made updates in DNS server to reslove 5.5 server over LAN. Now everything looks fine - setup is runing :)
0
 
marc_nivensCommented:
Good to hear!
0
 
StupiczAuthor Commented:
hmm...
Server is installed, but setup can`t start MSExchangeSA (MS Exchange System Attendant) service. The service did not  return an error.. :(
Any ideas?
0
 
marc_nivensCommented:
Start the System Attendant, let it fail, then check the application event log for warnings or errors.
0
 
StupiczAuthor Commented:
Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1005
Date:            26.10.2004
Time:            13:24:49
User:            N/A
Computer:      STRIX
Description:
Unexpected error There is no Microsoft Exchange Organization in that domain. ID no: c1030a8c Microsoft Exchange System Attendant  occurred.

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

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 
marc_nivensCommented:
Sounds like either DNS issues or AD replication issues.  Verify that your Exchange Server's DNS settings point only to an Active Directory DNS server, no entries for an ISP DNS server.  Also, force replication between the domain controllers in that domain.  
0
 
StupiczAuthor Commented:
OK. Thank You for helping :)
0

Featured Post

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

  • 9
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now