RE: Recipient Update Service Redundancy

2001-09-18 Thread Mark Harford
I was referring to a second RU Service, not a second RU Policy. Have you tried that? -Original Message- From: Jean-Francois Bourdeau [mailto:[EMAIL PROTECTED]] Sent: 17 September 2001 17:52 To: Exchange Discussions Subject: RE: Recipient Update Service Redundancy We tried to create

RE: Recipient Update Service Redundancy

2001-09-18 Thread Jean-Francois Bourdeau
:24 To: Exchange Discussions Subject: RE: Recipient Update Service Redundancy I was referring to a second RU Service, not a second RU Policy. Have you tried that? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm

RE: Recipient Update Service Redundancy

2001-09-17 Thread Jean-Francois Bourdeau
I forgot to tell you I also made the 2nd DC a Global Catalog Server. JF -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jean-Francois Bourdeau Sent: 17 septembre, 2001 11:31 To: Exchange Discussions Subject: Recipient Update Service Redundancy Hi

RE: Recipient Update Service Redundancy

2001-09-17 Thread Mark Harford
- From: Jean-Francois Bourdeau [mailto:[EMAIL PROTECTED]] Sent: 17 September 2001 17:10 To: Exchange Discussions Subject: RE: Recipient Update Service Redundancy I forgot to tell you I also made the 2nd DC a Global Catalog Server. JF -Original Message- From: [EMAIL PROTECTED] [mailto

RE: Recipient Update Service Redundancy

2001-09-17 Thread Jean-Francois Bourdeau
Of Mark Harford Sent: 17 septembre, 2001 12:45 To: Exchange Discussions Subject: RE: Recipient Update Service Redundancy It seems to be possible to create a second RUS on the same exchange server pointing to a different DC. If you set them to have update schedules that do not conflict this may