I would suggest that if the RUS is the same then you probably don't need to do that. You can try to see if it creates a performance improvement, but if the maintenance and address portions are exactly the same I'm not sure what the repercussions might be. In our case we have different policy needs for different admin groups so we have a RUS for each admin group which typically in our case means different DC/GC/Exchange servers.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mailing List Sent: Monday, March 22, 2004 1:48 PM To: Exchange Discussions Subject: RE: Exchange 2003 RUS (REcipient Update Service Delay) BTW We have 2 DC/GC in the main site and one DC/GC in another site (Remote site) Must we add a RUS (Recipient Update Service) in ESM for every DC/GC ??? Would this make our creation of user to have the proxy address generated faster ? JF -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Reasoner, Bob (PHES) Sent: Monday, March 22, 2004 11:30 AM To: Exchange Discussions Subject: RE: Exchange 2003 RUS (REcipient Update Service Delay) If you are part of a forest with more than one "Site" there isn't much you can do as it is based on AD replication schedule and inter-site replication pretty much averages 15 minutes. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mailing List Sent: Monday, March 22, 2004 10:16 AM To: Exchange Discussions Subject: Exchange 2003 RUS (REcipient Update Service Delay) When we create a user in our domain (AD) it takes up to 15 minutes to add the proxy address (SMTP address) to the user We have to manually in exchange manager do an update manually How can we setup the DC/GC and exchange for the proxy address generation to happen faster ?? JF _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
