Title: RE: Exchange 5.5 on 2000 server (recovery server)

Allen,

        We went from an Exch 5.5 NT4 Server to an Exch 5.5 W2k Server, exactly the way you mentioned.

Don Guyer
Information Systems
Citadel Federal Credit Union
[EMAIL PROTECTED]
Ph: 800.666.0191 x7072
Fax: 610.380.6083
www.citadelfcu.org


-----Original Message-----
From: Allen Crawford [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 24, 2002 4:00 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 5.5 on 2000 server (recovery server)


I am planning on testing this soon, but since I'm anxious, does anyone know
if you are running an NT 4, Exchange 5.5 server, can you use a Windows 2000,
Exchange 5.5 server as a recovery server?  In other words, if I have
Exchange 5.5 running the same service pack and patches and everything, could
I just do an online restore to that server?  This is assuming the old one
goes down and I rename the recovery server to the same name as the original.

 -----Original Message-----
From:   JENSEN, TIMOTHY C [mailto:[EMAIL PROTECTED]]
Sent:   Wednesday, April 24, 2002 2:57 PM
To:     MS-Exchange Admin Issues
Subject:        RE: Exchange 5.5 on 2000 server

Yes.  I have 15 MSX 5.5 SP4 boxes all running W2K enterprise.  Most have
been upgrades from NT4 too.  Nothing but good things to say about it so far.
Especially the terminal service : )

Tim Jensen
Cingular Wireless, Chicago

-----Original Message-----
From: Tony Flannery [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 24, 2002 2:17 PM
To: MS-Exchange Admin Issues
Subject: Exchange 5.5 on 2000 server


Does Exchange 5.5 run happily on Windows 2000 server ?  Has anyone
experienced problems with this configuration ?

Thanks,

Tony.

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

Reply via email to