RUS
Exchange Server Forum Index Exchange Server
Discussion forums for Microsoft Exchange Server users.
Microsoft Outlook
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web ExchangeServerHelp.com
RUS

 
Post new topic   Reply to topic    Exchange Server Forum Index -> Design
Author Message
admin
Guest





Posted: Tue Dec 14, 2004 1:37 pm    Post subject: RUS Reply with quote

In my company, there will be 4 unit of exchange server 2003 with SP1 in 3
separate AD domains. Domain A, B and C. Out of 4 exchange servers, 2 will be
located in domain C but in 2 separate physical locations namely site X and
site Y. The 2 sites are interconnected via a 512k WAN connection. Assuming
that I associate the RUS with 2 DCs in Site X and with another 2 DCs in Site
Y, here are my questions (note that all RUS association is done from an
exchange server in Site X only):
1. How the RUS publish the GAL when there are many DCs associated with the
component? will RUS component publish the GAL to all the associated DCs at
the same time? basically, how does this RUS works in publishing GAL to GCs?
2. If the exchange server which I associated the RUS with goes down for few
days, will GAL can still be generated maybe by the exchange server in Site
Y?

I really hope that some experts can help me answering the questions. We are
in the middle of designing RUS component placement.

thanks in advanced.

Back to top
Al Mulnick
Guest





Posted: Wed Dec 15, 2004 9:33 am    Post subject: Re: RUS Reply with quote

I think I know what you're asking...
How does RUS work? Take a look at the docs that fully explain this at
http://www.microsoft.com/exchange/library but basically you'll need a RUS
defined for each domain where user accounts will be mailbox-enabled. That
can be on one server or many, it's your choice.

If the server with the RUS functionality is off-line for several days, then
you won't get RUS functionality. Therefore, do your best to have a plan in
place for that eventuality. Maybe create a new one? Or maybe don't make
changes until it comes back online? Whatever works best for you. Oh, and
remember you may not want the OAB on the same server as the RUS if this is a
concern. Or maybe you do ;)

Al


"admin" <admin@test.com> wrote in message
news:uZoqG$a4EHA.2676@TK2MSFTNGP12.phx.gbl...
Quote:
In my company, there will be 4 unit of exchange server 2003 with SP1 in 3
separate AD domains. Domain A, B and C. Out of 4 exchange servers, 2 will
be located in domain C but in 2 separate physical locations namely site X
and site Y. The 2 sites are interconnected via a 512k WAN connection.
Assuming that I associate the RUS with 2 DCs in Site X and with another 2
DCs in Site Y, here are my questions (note that all RUS association is
done from an exchange server in Site X only):
1. How the RUS publish the GAL when there are many DCs associated with the
component? will RUS component publish the GAL to all the associated DCs at
the same time? basically, how does this RUS works in publishing GAL to
GCs?
2. If the exchange server which I associated the RUS with goes down for
few days, will GAL can still be generated maybe by the exchange server in
Site Y?

I really hope that some experts can help me answering the questions. We
are in the middle of designing RUS component placement.

thanks in advanced.






Back to top
admin
Guest





Posted: Wed Dec 15, 2004 1:30 pm    Post subject: Re: RUS Reply with quote

Al,

thanks for your response...

Can i understand your answer as the following? Under domain C, I should
create RUS functionality at both exchange servers (Site X and Site Y) in
domain C and associate each RUS server with more than 1 local DC. For
example, RUS server in China will associate itself with DCs in China and the
RUS server in Singapore will associate with DCs in Singapore. if one of the
exchange server goes offline in domain C for serveral days, RUS
functionality will still be around to create/update or maintain address
lists. am I correct?

thanks


"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:OCnAHbl4EHA.2572@tk2msftngp13.phx.gbl...
Quote:
I think I know what you're asking...
How does RUS work? Take a look at the docs that fully explain this at
http://www.microsoft.com/exchange/library but basically you'll need a RUS
defined for each domain where user accounts will be mailbox-enabled. That
can be on one server or many, it's your choice.

If the server with the RUS functionality is off-line for several days,
then you won't get RUS functionality. Therefore, do your best to have a
plan in place for that eventuality. Maybe create a new one? Or maybe
don't make changes until it comes back online? Whatever works best for
you. Oh, and remember you may not want the OAB on the same server as the
RUS if this is a concern. Or maybe you do ;)

Al


"admin" <admin@test.com> wrote in message
news:uZoqG$a4EHA.2676@TK2MSFTNGP12.phx.gbl...
In my company, there will be 4 unit of exchange server 2003 with SP1 in 3
separate AD domains. Domain A, B and C. Out of 4 exchange servers, 2 will
be located in domain C but in 2 separate physical locations namely site X
and site Y. The 2 sites are interconnected via a 512k WAN connection.
Assuming that I associate the RUS with 2 DCs in Site X and with another 2
DCs in Site Y, here are my questions (note that all RUS association is
done from an exchange server in Site X only):
1. How the RUS publish the GAL when there are many DCs associated with
the component? will RUS component publish the GAL to all the associated
DCs at the same time? basically, how does this RUS works in publishing
GAL to GCs?
2. If the exchange server which I associated the RUS with goes down for
few days, will GAL can still be generated maybe by the exchange server in
Site Y?

I really hope that some experts can help me answering the questions. We
are in the middle of designing RUS component placement.

thanks in advanced.










Back to top
Al Mulnick
Guest





Posted: Thu Dec 16, 2004 9:03 am    Post subject: Re: RUS Reply with quote

I suppose you could do it that way. There are guidelines for using multiple
RUS services in the same domain however. You may need to contact your local
Microsoft support for that information. I would point you to docs for it,
but I haven't seen any floating around.
I have seen organizations that use a similar setup however. Not for
redundancy so much but for performance reasons.
Basically, you just need at least one RUS running per domain. It can be
running on the same server in one domain for all of them or separated out,
but an instance needs to be defined for each domain. At least one instance
in this case.

Al



"admin" <admin@test.com> wrote in message
news:O9H9Cgn4EHA.3120@TK2MSFTNGP12.phx.gbl...
Quote:
Al,

thanks for your response...

Can i understand your answer as the following? Under domain C, I should
create RUS functionality at both exchange servers (Site X and Site Y) in
domain C and associate each RUS server with more than 1 local DC. For
example, RUS server in China will associate itself with DCs in China and
the RUS server in Singapore will associate with DCs in Singapore. if one
of the exchange server goes offline in domain C for serveral days, RUS
functionality will still be around to create/update or maintain address
lists. am I correct?

thanks


"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:OCnAHbl4EHA.2572@tk2msftngp13.phx.gbl...
I think I know what you're asking...
How does RUS work? Take a look at the docs that fully explain this at
http://www.microsoft.com/exchange/library but basically you'll need a RUS
defined for each domain where user accounts will be mailbox-enabled.
That can be on one server or many, it's your choice.

If the server with the RUS functionality is off-line for several days,
then you won't get RUS functionality. Therefore, do your best to have a
plan in place for that eventuality. Maybe create a new one? Or maybe
don't make changes until it comes back online? Whatever works best for
you. Oh, and remember you may not want the OAB on the same server as the
RUS if this is a concern. Or maybe you do ;)

Al


"admin" <admin@test.com> wrote in message
news:uZoqG$a4EHA.2676@TK2MSFTNGP12.phx.gbl...
In my company, there will be 4 unit of exchange server 2003 with SP1 in
3 separate AD domains. Domain A, B and C. Out of 4 exchange servers, 2
will be located in domain C but in 2 separate physical locations namely
site X and site Y. The 2 sites are interconnected via a 512k WAN
connection. Assuming that I associate the RUS with 2 DCs in Site X and
with another 2 DCs in Site Y, here are my questions (note that all RUS
association is done from an exchange server in Site X only):
1. How the RUS publish the GAL when there are many DCs associated with
the component? will RUS component publish the GAL to all the associated
DCs at the same time? basically, how does this RUS works in publishing
GAL to GCs?
2. If the exchange server which I associated the RUS with goes down for
few days, will GAL can still be generated maybe by the exchange server
in Site Y?

I really hope that some experts can help me answering the questions. We
are in the middle of designing RUS component placement.

thanks in advanced.










Back to top
 
Post new topic   Reply to topic    Exchange Server Forum Index -> Design All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




Windows Server Dedicated Servers
New Topics Powered by phpBB