• RSS
  • Twitter
  • FaceBook

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

Phantom E2K Server after migration

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2000] >> Migration >> Phantom E2K Server after migration Page: [1]
Login
Message << Older Topic   Newer Topic >>
Phantom E2K Server after migration - 16.Aug.2002 10:04:00 PM   
clynn

 

Posts: 30
Joined: 19.Feb.2001
From: Farmington Hills, MI
Status: offline
My comapny was beginning to have server issues. The box E2K was on was starting to crash. We got a new box, and loaded the same programs on it. I was able to move all the mailboxes over before it finally crashed for good.

Now the 1st Server, Zeus, is unplugged from the network (it wouldn't boot anyway), but I see residual images of it in active directory. I was not able to decommision it as a DC in time. What can I do to completely remove it from the network.

Some of the users get their mail through Outlook 2002 by connecting directly to the exchange server. I have tried removing the email accounts, and creating new ones with the new server name, Chronos. I still get delays in Outlook, and I notice it is still trying to connect to Zeus. What's up with that?

If anyone can help me with this, it would be great. Let me know if you need more info.

Chris
Post #: 1
RE: Phantom E2K Server after migration - 17.Aug.2002 4:01:00 AM   
Guest
You really need to remove w2k DCs correctly, and that is to dcpromo down. When you don't dcpromo down, then that leaves orphaned DCs/objects in AD, which will cause problems. Other DCs will always try to contact a DC that no longer exists, etc. In such a situation you will have to use NTDSUTIL, a w2k utility, to remove the orphaned DC from the domain. Use w2k HELP to get info on NTDSUTIL. Its a clunky utility.

The first E2k box was the first E2k server, so the Site Folders are homed there, OAB, freebusy, etc. If it no longer exists, and can't be brought up, you can use the GUIDGEN utility to reset the Site Folders on the new E2k box. If you still see the orginal E2k box in ESM, you can remove it via ADSIEDIT, in the W2k Support Tools. Path in ADSIEDIT is:

Configuration --> Services --> Microsoft Exchange --> Myexchangeorganization --> Administrative Groups --> Servers. (I think this is approximately correct).

Delete Zeus. Replicate to all DCs. But, I don't know if you should do this w/out maybe contacting MS and have them walk you through this, because your 1st W2k box, unless you manually changed things, is the fsmo role holder, schema master, infrastructure master, etc.. If you had another DC at the time when all this happened, you can SEIZE those roles w/ NTDSUTIL. I suppose you did, because you wouldnt have an AD otherwise. Basically you need to do these things:

1. Seize the fsmo roles so they are on another DC or DCs, since the 1st W2k DC is history.

2. Remove the E2k server from AD, which is relatively simple, just deleting the server object in ADSIEDIT.

3. Run GUIDGEN to reset the Site Folders. This too, relatively easy.

4. Redo all your OL profiles to point to the new E2k box, if you weren't able to move mailbox to it, and therefore enable OL clients to automatically redirect their profiles.

(in reply to clynn)
  Post #: 2

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2000] >> Migration >> Phantom E2K Server after migration 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


Follow TechGenix on Twitter