New 2000 exchange server from a 5.5

New 2000 exchange server from a 5.5 (Full Version)

All Forums >> [Microsoft Exchange 2000] >> Installation

Message

Viper62 -> New 2000 exchange server from a 5.5 (8.Dec.2005 10:21:02 PM)
I have been with this company for a while now and have taken over a 5.5 exchange server that reallys seems to have been improperly setup from the get go. I have pursuaded them to order exchange 2000 and now what I would like to do is setup a whole new server and do a clean install of 2000 exchange on it and just move the mailboxes and db's over. I have done something similar a while back when 2000 was the new thing out there and it was quite and involved procedure. Now my domain is 2000 but it only has one AD - I would like to make this new exchange server a backup AD but I know this all can be tricky to do or at least it was a few years back. So I would like some advice as to how to do this the best/safest way. If anyone can be of assistance it would be greatly appreciated and if any further information is needed just let me know. Mike

pjhutch -> RE: New 2000 exchange server from a 5.5 (15.Dec.2005 1:19:12 PM)
When you say one AD - do you mean one domain or a domain with one Domain Controller (DC)? Yes, its possible to install Exchange on another domain controller although its not recommended, a member server would be preferred. To make a another DC, just run DCPromo. If migrating Ex 5.5 then you need an Active Directory Connector installed to migrate settings etc from the old Exchange 5.5 organisation to the new server. Then you can install Exchange.

Viper62 -> RE: New 2000 exchange server from a 5.5 (15.Dec.2005 5:31:42 PM)
Yes that is what I meant - I have one domain that has only one DC - I would like to make the new mail server a backup DC if you would. I would like to then just import all the mailboxes and contacts (the db stuff) over to the new mail server and then do away with the 5.5 server and switch everyone to the new mail server. Its this process that I have heard is a real bear and the domain that I inherited is a Single Label Domain as well. Thanx for you input and if you have links to any FAQ's for doing this it would be greatly appreciated. Mike

pjhutch -> RE: New 2000 exchange server from a 5.5 (15.Dec.2005 5:37:32 PM)
Here's some useful links: http://www.msexchange.org/tutorials/Exchange-55-Directory-Migration-Exchange-2003.html (applies to 2K as well) http://www.msexchange.org/tutorials/Exchange_2003_Upgrade_Checklist.html (same for 2K) http://support.microsoft.com/default.aspx?scid=kb;en-us;555262 http://support.microsoft.com/default.aspx?scid=kb;en-us;259912 http://support.microsoft.com/default.aspx?scid=kb;en-us;327928

Viper62 -> RE: New 2000 exchange server from a 5.5 (22.Dec.2005 5:21:43 PM)
One of the problems with the current installation of Exchange 5.5 is that the Administrator module does not work. It will not find the Exchange server and I have researched and tried several things in the past to no avail. One of the many reasons I want to do a fresh install.

pjhutch -> RE: New 2000 exchange server from a 5.5 (23.Dec.2005 11:53:22 AM)
For the Exchange Admin to work, the program needs to be running with: a) PC Joined to the Domain b) WINS, DNS correctly configured. c) Server/Workstation working and RPC available d) Need at least Account Operator and Exchange Admin priviledges.

Viper62 -> RE: New 2000 exchange server from a 5.5 (29.Jan.2006 9:17:17 PM)
Ok I am now working on trying to implement this. I have checked the things you stated but still can not open the Exchange 5.5 Administrator. I get the following error when I try: DS_E_COMMUNICATIONS_PROBLEM and it also does not seem to have an ADC installed. My plan is to do a "move mailbox" setup where I have new hardware that I am going to install Exchange Server 2000 on but from what I can see I will still need to access the 5.5 Administrator to set it up for the mailbox move unless there is a way around that. What I want to do is this clean install of Exchange 2000 on new hardware and move all the mailboxes over to the 2000 Exchange box in my all 2000 server domain. Any help would be greatly appreciated so I can move forward with this. Thanx...

pjhutch -> RE: New 2000 exchange server from a 5.5 (30.Jan.2006 10:13:34 AM)
DS_E_COMMUNICATION_ERROR means that it cannot connect to the Directory Services (DS) on Exchange 5.5. The lack of a properly configured ADC would be the most likely error, you need to get that up and configured before doing anything else with all the Connectors setup. For Exchange 5.5 admin to work, you need 'Client for Microsoft Networks' installed, TCPIP, PC joined to the same domain where Exchange is installed. You also need Exchange Admin rights to access Exchange configuration as well (you can set these at Organisation, Site and Configuration levels). See http://www.msexchange.org/tutorials/Exchange_2003_Upgrade_Checklist.html (Applies to 2000 as well) http://www.msexchange.org/tutorials/Exchange-55-Directory-Migration-Exchange-2003.html http://support.microsoft.com/kb/555262/en-us http://support.microsoft.com/kb/259912/en-us http://support.microsoft.com/kb/312632/en-us

Viper62 -> RE: New 2000 exchange server from a 5.5 (30.Jan.2006 5:47:08 PM)
I am using the Administrator on the server where Exchange 5.5 is installed. I have installed the ADC that I found listed when I searched for it on MS site regarding Exchange 5.5 but that in itself did not resolve the issue. Everything else seems to be correct but I will let you know that this domain was configured as a Single Label domain when the person set it up. I took over a mess if you would and have been straightening out problems ever since. I can ping the IP and the Netbios name just fine. Yesterday I started setting up the new server and ran dcpromo and made it a secondary DC in the existing domain. I have a single site, single domain all at one location so that should simplify things somewhat. It wont even let me browse for the Exchange server via the Administrator's module. I have found a similar error in online research but its pertaining to a hotfix for a particular problem that does not match mine other than the error. Thanx so much for all your help...

Viper62 -> RE: New 2000 exchange server from a 5.5 (30.Jan.2006 5:56:01 PM)
Also a quick question regarding my current Exchange 5.5 server - does that server need to have Active Directory installed on it? Because it doesnt...

pjhutch -> RE: New 2000 exchange server from a 5.5 (30.Jan.2006 6:19:17 PM)
No, all the server needs is to be 'joined' to a domain thats all so it can access domain accounts.

Viper62 -> RE: New 2000 exchange server from a 5.5 (30.Jan.2006 6:26:46 PM)
Ok - its joined so now I just need to figure out why that Administrator has never worked.

Viper62 -> RE: New 2000 exchange server from a 5.5 (30.Jan.2006 11:24:56 PM)
I just tried configuring the ADC and got the following message: Unable to contact the exchange server, please ensure that your connections are configured correctly. Im using the same account for the AD server and Exchange. The account belongs to all the needed groups and the only other thing is I changed how it updates as set by default to "From windows to exchange". When I click ok to save it - it gives the above error. Also now my error when trying to connect via the 5.5 Administrator is DS_E_COMMUNICATIONS_PROBLEM (instead of ERROR). Also when trying to install Exchange 2000 I get the following error: The component "Microsoft Exchange Messaging and Collaboration Services" can not be assigned the action "Install" because. - Active Directory has not replicated all the necessary permissions for the deleted items container. Please wait for replication to complete before running setup. I got this Sunday several times and I manually replicated from AD Sites and Services. I dont know if that single label domain stuff is causing this. Could there be something I am missing in my DNS?

Viper62 -> RE: New 2000 exchange server from a 5.5 (31.Jan.2006 5:39:36 PM)
I am running DNS on the Exchange server and because AD is not installed its configured for Standard Primary for the type. It does not have all the records that are in the primary DNS server. I have made sure that my main DC and itself is in there though. Im thinking that the problem must be there somewhere but not sure what to look for exactly.

pjhutch -> RE: New 2000 exchange server from a 5.5 (31.Jan.2006 6:17:13 PM)
For Exchange to work you need all the DCs and ALL the Exchange servers to have MX and A (Host) records in DNS.

Viper62 -> RE: New 2000 exchange server from a 5.5 (31.Jan.2006 6:32:13 PM)
Here is my dcdiag output for my domain: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\CRCAD Starting test: Connectivity *** Warning: could not confirm the identity of this server in the directory versus the names returned by DNS servers. If there are problems accessing this directory server then you may need to check that this server is correctly registered with DNS ......................... CRCAD passed test Connectivity Testing server: Default-First-Site-Name\MAILSERVER Starting test: Connectivity ......................... MAILSERVER passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\CRCAD Starting test: Replications ......................... CRCAD passed test Replications Starting test: NCSecDesc ......................... CRCAD passed test NCSecDesc Starting test: NetLogons ......................... CRCAD passed test NetLogons Starting test: Advertising ......................... CRCAD passed test Advertising Starting test: KnowsOfRoleHolders ......................... CRCAD passed test KnowsOfRoleHolders Starting test: RidManager ......................... CRCAD passed test RidManager Starting test: MachineAccount ......................... CRCAD passed test MachineAccount Starting test: Services ......................... CRCAD passed test Services Starting test: ObjectsReplicated ......................... CRCAD passed test ObjectsReplicated Starting test: frssysvol There are errors after the SYSVOL has been shared. The SYSVOL can prevent the AD from starting. ......................... CRCAD passed test frssysvol Starting test: kccevent An Warning Event occured. EventID: 0x80000443 Time Generated: 01/31/2006 11:42:48 (Event String could not be retrieved) ......................... CRCAD failed test kccevent Starting test: systemlog ......................... CRCAD passed test systemlog Testing server: Default-First-Site-Name\MAILSERVER Starting test: Replications ......................... MAILSERVER passed test Replications Starting test: NCSecDesc ......................... MAILSERVER passed test NCSecDesc Starting test: NetLogons ......................... MAILSERVER passed test NetLogons Starting test: Advertising ......................... MAILSERVER passed test Advertising Starting test: KnowsOfRoleHolders ......................... MAILSERVER passed test KnowsOfRoleHolders Starting test: RidManager ......................... MAILSERVER passed test RidManager Starting test: MachineAccount ......................... MAILSERVER passed test MachineAccount Starting test: Services ......................... MAILSERVER passed test Services Starting test: ObjectsReplicated ......................... MAILSERVER passed test ObjectsReplicated Starting test: frssysvol ......................... MAILSERVER passed test frssysvol Starting test: kccevent ......................... MAILSERVER passed test kccevent Starting test: systemlog An Error Event occured. EventID: 0x0000165B Time Generated: 01/31/2006 11:29:29 (Event String could not be retrieved) An Error Event occured. EventID: 0x0000169E Time Generated: 01/31/2006 11:33:45 (Event String could not be retrieved) ......................... MAILSERVER failed test systemlog Running enterprise tests on : crc Starting test: Intersite ......................... crc passed test Intersite Starting test: FsmoCheck ......................... crc passed test FsmoCheck Here is the Netdiag for my DC ......................................... Computer Name: CRCAD DNS Host Name: crcad.crc System info : Windows 2000 Server (Build 2195) Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel List of installed hotfixes : KB820888 KB822343 KB822831 KB823182 KB823559 KB824105 KB824151 KB825119 KB826232 KB828035 KB828741 KB828749 KB832353 KB832359 KB835732 KB837001 KB839645 KB840987 KB841356 KB841533 KB841872 KB841873 KB842526 KB842773 KB870763 KB871250 KB873333 KB873339 KB883939-IE6SP1-20050428.125228 KB885250 KB885834 KB885835 KB885836 KB888113 KB890046 KB890859 KB891781 KB893066 KB893086 KB893756 KB893803v2 KB894320 KB896358 KB896422 KB896423 KB896424 KB896688-IE6SP1-20051004.130236 KB896727-IE6SP1-20050719.165959 KB897715-OE6SP1-20050503.210336 KB899587 KB899588 KB899589 KB899591 KB900725 KB901017 KB901214 KB902400 KB904706 KB905414 KB905495-IE6SP1-20050805.184113 KB905749 KB905915-IE6SP1-20051122.175908 KB908519 KB908523 KB912919 Q147222 Q828026 Update Rollup 1 Netcard queries test . . . . . . . : Passed Per interface results: Adapter : Local Area Connection Netcard queries test . . . : Passed Host Name. . . . . . . . . : crcad IP Address . . . . . . . . : 192.168.254.11 Subnet Mask. . . . . . . . : 255.255.255.0 Default Gateway. . . . . . : 192.168.254.1 Primary WINS Server. . . . : 192.168.254.11 Dns Servers. . . . . . . . : 192.168.254.11 192.168.254.10 AutoConfiguration results. . . . . . : Passed Default gateway test . . . : Passed NetBT name test. . . . . . : Passed WINS service test. . . . . : Passed Global results: Domain membership test . . . . . . : Passed NetBT transports test. . . . . . . : Passed List of NetBt transports currently configured: NetBT_Tcpip_{458088CB-9BBC-416D-81D7-A40CA48CC745} 1 NetBt transport currently configured. Autonet address test . . . . . . . : Passed IP loopback ping test. . . . . . . : Passed Default gateway test . . . . . . . : Passed NetBT name test. . . . . . . . . . : Passed Winsock test . . . . . . . . . . . : Passed DNS test . . . . . . . . . . . . . : Failed [WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.254.11'. Please wait for 30 minutes for DNS server replication. [WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.254.10'. Please wait for 30 minutes for DNS server replication. [FATAL] No DNS servers have the DNS records for this DC registered. Redir and Browser test . . . . . . : Passed List of NetBt transports currently bound to the Redir NetBT_Tcpip_{458088CB-9BBC-416D-81D7-A40CA48CC745} The redir is bound to 1 NetBt transport. List of NetBt transports currently bound to the browser NetBT_Tcpip_{458088CB-9BBC-416D-81D7-A40CA48CC745} The browser is bound to 1 NetBt transport. DC discovery test. . . . . . . . . : Passed DC list test . . . . . . . . . . . : Passed Trust relationship test. . . . . . : Skipped Kerberos test. . . . . . . . . . . : Passed LDAP test. . . . . . . . . . . . . : Passed Bindings test. . . . . . . . . . . : Passed WAN configuration test . . . . . . : Skipped No active remote access connections. Modem diagnostics test . . . . . . : Passed IP Security test . . . . . . . . . : Passed IPSec policy service is active, but no policy is assigned. The command completed successfully I am half tempted to just start this network over from scratch... Anyway any help would be greatly appreciated.

pjhutch -> RE: New 2000 exchange server from a 5.5 (1.Feb.2006 10:10:42 AM)
On the DNS server, is Dynamic updates enabled for automatic Host entries? On the DNS, is there a Host record, a _msdcs folder with CNAME and SRV records for the DC? On the DC, in tCPIP properties make sure its own IP address is in the DNS list. Also, make sure in Advanced, DNS tab, that 'Register this connection's address in the DNS' is enabled. See http://support.microsoft.com/kb/824449/en-us http://support.microsoft.com/kb/291382/en-us

Viper62 -> RE: New 2000 exchange server from a 5.5 (2.Feb.2006 6:23:22 PM)
Yes - I have checked all these things prior. I upgraded the old DC to a new box and transfered all schema and everything to the new server. Everything seemed to have worked and there were no evident problems. The old server was decommissioned and then I noticed for the first time that this was a single label domain when I tried adding a new computer to my network. I found the MS kb article instructing to minor additions to the registry to allow computers to commuincate with single label domains. I found an issue where the 32 digit number under the _msdcs folder in DNS was of the old server so I researched and used DCDIAG, NETDIAG and ADSIEDT to do a cleanup. I had many DNS errors and resolved it to what you see now and I have tried the manual registration of the DNS after stopping NETLOGON and clearing all DNS CACHE and then restarting NETLOGON. Somewhere there is like one thing wrong causing all this grief and I just am not sure where to look for it. Again thanx so much for all your advice and help. Ok I went through the whole net stop/start and re-registration of dns and checked my event log and found the following (which is what I had been getting) Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5790 Date: 2/2/2006 Time: 2:23:18 PM User: N/A Computer: CRCAD Description: The description for Event ID ( 5790 ) in Source ( NETLOGON ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: MINOR-CONN, Access is denied. . Data: 0000: 22 00 00 c0 "..� Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5723 Date: 2/2/2006 Time: 2:20:59 PM User: N/A Computer: CRCAD Description: The session setup from the computer MINOR-CONN failed because there is no trust account in the security database for this computer. The name of the account referenced in the security database is MINOR-CONN$. Data: 0000: 8b 01 00 c0 ?..� Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5774 Date: 2/2/2006 Time: 2:42:44 PM User: N/A Computer: CRCAD Description: Registration of the DNS record 'dce7117a-9732-4a6c-ba1f-797e32ae3328._msdcs.crc. 600 IN CNAME crcad.crc.' failed with the following error: DNS RR set that ought not exist, does exist. Data: 0000: 2f 23 00 00 /#..

pjhutch -> RE: New 2000 exchange server from a 5.5 (3.Feb.2006 10:05:54 AM)
Looks like the computer account in the domain is missing. You will need to remove the server from the domain and re-add it, this should also fix the DNS problem as well.

Viper62 -> RE: New 2000 exchange server from a 5.5 (3.Feb.2006 5:12:05 PM)
Its THE DC - it holds the schema and everything. There would be no way to do that... Not that I know of.

Page: [1] 2 next > >>