If other mailboxes on the old BE are working fine via OWA, then
check the new BE config.. Mahmoud From:
exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On
Behalf Of Mitul Zaveri Yes I am using a FE/BE topology. This issue is
occurring after I have moved one test user to the newly added backend exchange
server. OWA only resides on the FE server. However I am able to login while
accessing the backend server directly. Thanks & Regards From:
exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On
Behalf Of Mahmoud Amin Ismail Check this: http://support.microsoft.com/kb/823159
are you having a FE/BE topology..? or you are accessing owa on
each of the two server..? Mahmoud Amin From:
exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On
Behalf Of Mitul Zaveri Hi All: We have added a new Exchange backend server in the current
setup and tried moving a test user mailbox using ESM. The process was completed
successfully. However when we are trying to check the same using OWA it is
giving “HTTP/1.1 503 Service Unavailable”. Please help me on this. Thanks & Regards From:
exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On
Behalf Of Jason Sherry 1.
Make the new server Exchange
2007 ·
Read: http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part1.html
or similar articles that cover migrating to E2k7 and retiring your E2k7 servers ·
Recommend going with a
CCR cluster, which requires at least 3 E2k7 server (CCR node 1, CCR node 2, HUB
& CAS server) o
If you call all-in-one
then HUB, CAS, & MBX roles can be on one system ·
If you don’t go CCR
then at least setup LCR ·
If you do goto E2k7,
you will need to replace your FE with a E2k7 CAS server before you move
mailboxes to E2k7 2.
Recommend adding at least one
addition DC. Jason Sherry - Technology
Strategist, MCSE: M, Microsoft MVP From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Kamuni,
Prabhakar Since there is only 1000 Mailboxes in the Organization, new Back
end server should be a well versed solution. I will recommend you to distribute the mailboxes, so everything
should go ok.
From:
exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On
Behalf Of James Chong No cons really; this is the correct step. The only con is probably
to considering migrating to 07 which will give you a that significant IO
reduction via incremental memory. James
Chong Sr.
Systems Engineer Simplexity,
LLC. 11130
Sunrise Valley Drive, Suite 300 Reston,
VA 20191 O
(703) 657-4612 C
(703) 863-1483 From: exchangelist-bounce@xxxxxxxxxxxxx
[exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Mitul Zaveri [mitul@xxxxxxxxxxxxxxxxxxxxx] Hi All: The Current Exchange Setup is as follows: # Frontend – Backend Setup # 1 Frontend Server (with RPC over HTTPs proxy) + 1
Backend Server (1000 mailboxes) + 1 Domain Controller # Windows 2003 Enterprise Server (SP2) + Exchange 2003
Enterprise Server (SP2). We are planning to add an additional backend server with
higher disk and I/O capacity and move the mailboxes on the new server. The steps are broadly outlined as below: 1. Additional Server joining the Existing windows domain Can somebody please guide me through the pros/cons of this
setup or pre-defined checklist that one needs to take care of in this kind of
migration. Thanks & Regards Mitul
Confidentiality
& Disclaimer Note:
This e-mail and any attachments thereto contain protected and confidential
information intended for the sole use of the addressee individual or
organization. If you are not the addressee or an authorized agent for him/it,
or if you have received this message by error please notify the sender
immediately by returning the message, and delete this copy from your system
without any illegal use. The
Dar Group shall not be liable for the improper or incomplete transmission of
the information contained in this communication nor for any delay in its
receipt or damage to your system.
|