HackLife
asked on
Exchange 5.5 & W2k + Exchange 2003?
Situation:
I have a clustered Exchange 5.5 network in a single site with Windows 2000 member servers and domain controllers. I want to install another exchange server strictly for journaling and archiving. I prefer not to continue using Exchange 5.5, because I am planning on upgrading these later this year. I would like to use Exchange 2003.
Question:
What is the best way I can install a new Exchange, preferably a 2003 version, without causing problems with the Exchange 5.5 system?
I have a clustered Exchange 5.5 network in a single site with Windows 2000 member servers and domain controllers. I want to install another exchange server strictly for journaling and archiving. I prefer not to continue using Exchange 5.5, because I am planning on upgrading these later this year. I would like to use Exchange 2003.
Question:
What is the best way I can install a new Exchange, preferably a 2003 version, without causing problems with the Exchange 5.5 system?
http://www.microsoft.com/technet/prodtechnol/exchange/guides/PlanE2k3MsgSys/40968c49-43bb-4d8b-bb40-eb6996b764ae.mspx
ASKER
I appreciate your input, but the key here is that I don't want to upgrade the 5.5 yet and interfere with that setup. I don't want to install ADC to sync 5.5 with AD. I just want the Exchange 2003 to be installed and journaling turned on.
Exchange 2003 will not work without AD; Exchange 2003 will not see Exchange 5.5 without ADC & SRS server.
ASKER
What if I install Exchange 2003 with its own AD? Maybe in a separate AD site? I don't need anything from the original network except to receive mail.
Yes, you could do that but if you want 5.5 and 2003 to talk to each other it will not happen. If you want 2003 all by itself then it will work just for journalling. WHy do you only want it for journalling?
ASKER
Archiving email.
2003 all by itself is correct. It will connect the local Active Directory but will this AD interfere with the other AD in another site?
2003 all by itself is correct. It will connect the local Active Directory but will this AD interfere with the other AD in another site?
Not if kept on a different subnet.
WOuldn't it be easier all around if you just bought an Archiving solution such as KVS? If that's all you're looking to do I would suggest going that route.
ASKER
Because it needs exchange. I have EMC Legato EmailXtender. I've researched and tested all the big brands. KVS is the same. It all needs exchange to journal and journalling uses alot of processing. Hence, I am installing a new Exchange.
Sounds good! I wish you luck.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I appreciate all your help in this. Every view matters.
I intend to send mail to the Exchange 2003 box by simply creating a mailbox on the server and then forward a message from Exchange 5.5 to Exchange 2003.
The Exchange 2003 box will be journaling these messages.
As you both know from the conversation, I don't want to use the ADC. The reason for this is because I don't need any of the data from the other exchange (5.5). All I want is to use the domain name. That is it.
Is it possible guys?
I intend to send mail to the Exchange 2003 box by simply creating a mailbox on the server and then forward a message from Exchange 5.5 to Exchange 2003.
The Exchange 2003 box will be journaling these messages.
As you both know from the conversation, I don't want to use the ADC. The reason for this is because I don't need any of the data from the other exchange (5.5). All I want is to use the domain name. That is it.
Is it possible guys?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks.
ASKER
I will pretty much will create my report on the three options: integrated with 5.5; independent entity (subdomain) with 2003; or half into an upgrade with 5.5 and 2003 by using the methods outlined in the Microsoft documentation.
Time for another meeting. Thanks guys.
Time for another meeting. Thanks guys.