Re: Recipient update service

as it's a migration then the admin model follows the old MX 5.5 site
boundary ie one MX 5.5 site - 1 Admin Group.
"Simon Walsh" <simon.walsh@xxxxxxxxx> wrote in message
news:OYdSRCjHHHA.420@xxxxxxxxxxxxxxxxxxxxxxx
You need 1 Enterprise RUS and 1 RUS for each domain that has Exchange
recipients.

Just a thought. Do you really need 20 Admin Groups? It sounds like quite a
lot for an organization of your size.
Remember that an AG is an administrative boundary and not a messgae
routing boundary.

/Simon
"Jim" <j_snowdon@xxxxxxxxxxx> wrote in message
news:uhO0u6hHHHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
We are currently migrating from MX 5.5 to 2003, 42 MX 5.5 sites/3500
users, will eventually replace 42 MX 5.5 sites with 20 MX 2003 admin
groups.

Question is about the RUS, do you need to set up more than the default
domain/enterprise one's?





.

Relevant Pages

  • Re: More ADMT errprs during SID migration
    ... I've created new user on Target Domain added him to Domain Admin group - ... I'm trying to migrate just one user - if that's how the rest of my migration ... > I've added Target domain admin group to local admin group on Source domain ...
    (microsoft.public.windows.server.migration)
  • ADSI Error
    ... issue..!but during the migration of computers I'm receing follwoing errors ... The ADSI property cannot be found in the property cache. ... ERR3:7075 Failed to change domain affiliation, ... admin group of that XP computer, all the service are started and firewall is ...
    (microsoft.public.windows.server.migration)
Loading