Re: New User Not in GAL, Recipient Policy Not Applied

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Robert Li [MSFT] wrote:

Since the older RUS Recipient Update Service (Domain) is deleted and
the new created RUS work fine, you can take it easy. Also, since
that's deleted, we are unable to find which attributes are corrupted.
Thanks for your understanding.

No, the older in-built Enterprise RUS is still there (it can't be
deleted), and now I have a new Domain RUS - this is the one that works.
What I was asking was how to fix the in-built Enterprise RUS (which is
what caused these issues in the first place), so that I can then delete
the new Domain RUS.

--
Regards,
Steve.
.

Relevant Pages

  • Re: RUS
    ... Just looking for best practice really. ... So is all I really need is one Enterprise RUS and one domain RUS (with ... Am I right in stating that the RUS runs on the Exchange server and this ... Should I configure a domain RUS for each AD site that I have? ...
    (microsoft.public.exchange.admin)
  • Re: RUS and Domain Controllers
    ... When an object under scope of a Recipient Policy changes, RUS should update ... MCSE, MCT ... >>> What that really means is that if you create a new domain RUS, ...
    (microsoft.public.exchange.admin)