Outlook/OWA redirects to old exchange server... not new

[jaybuffet]

Ok.. so I've been thrown into network admin position. Old exchange was dieing (hard drives crashing.. etc..). They had no backups or anything. Exchange services hung on the Starting state. This box is also DC.

So created a new DC, installed Exchange, copied over the edb/stm files, ran eseutil /p on them, so now i can actually see the mailboxes and public folders on new exchange.

So i ran dcpromo on old server to take away its active directory status.

Currently, old server still on network with exchange, all server stuck in hung position (Event log says Metabase update failed). Quick google couldn't find anything to solve that one.

New server up an dkicking as DC, but when you go to

http://newserver/exchange...

it redirects to

http://oldserver/exchange...

also in Outlook when modifying a profile.. I type in the server... hit Check Name... the server field is automatically populated with the old server name... another weird one is when on the new server.. if i go to

http://newserver_ip/exchange..

it too redirects...

Since old server not working.. all redirects fail bla h blah...


any help is much appreciated
Thanks
Jason

 

[tangostar]

On Exchange System Manager
Routing Group Members are both servers listed
if so can you make the new one master?

In your DNS are there still MX records for the old server?

 

[jaybuffet]

I think I may have solved it. Don't know if it was the right way or not... but used ADSIEdit to edit the users properties... attributes homeMDB, homeMTS, and msExchHomeServerName needed to be updated to the new server. I'm assuming thats what the ISAPI filer uses.

 

[netometer]

Hi!
Here is a brief movie how to migrate exchange 5.5 server.

http://www.netometer.net/samples/move55/step1/step1.html

NetoMeter

http://www.netometer.net

 

[jaybuffet]

They are both Exchange 2000.. ones a dieing box though

 

[tangostar]

that's good that you've fixed your problem. Now it is better if you don't have Exchange on a DC

 

[jaybuffet]

Why is that ?

 

[icvanstra]

jaybuffet,

to answer for tango... in a pristine world (i.e. you have enough servers) it is highly suggested that you not run Exchange and DC on the same server. Although MS says you can do it ... they also say you can run W2K on 128Mb of ram.

It will work, it's just not the preferred method.

have a good weekend.

eric

 

[netometer]

Hi!

1. Here is an MS article about how to move the information store database that was created on one Exchange 2K server to another Exchange 2K server in the same AD.

http://support.microsoft.com/?id=324127

They are talking about E2K Enterprise server but I think it should work with Standard Edition too. Just instead of creating a second Storage Group you have to use the existing one. I guess that their script is doing what jaybuffet has done manually with ADSIEDIT.

2. About Hosting a DC and Exchange on the same server
There a couple of considerations which come up:
2.1 It takes a long time for the Exchange Server to shut down – usually the AD services shuts down before the exchange services. This causes the DSAccess service to go through a couple of timeouts before it shuts down.
2.2 If Active Directory services are busy or not responding usually Exchange tries to contact another DC. If it is running on a DC it will not.
2.3 Security considerations

NetoMeter

http://www.netometer.net