Hello, We have multiple domains in a cross forest trust operating off one primary site. DNS suffixes have been setup to ensure name resolution. All clients have been pushed using a login script that defined the site, MP etc since they can't rely on AD. Boundaries were already defined all sites are assigned to primary. We are now debating if we should use protected DPs or secondary sites. We have 4 offices. The main office with the primary has about 200-300 pcs the remote offices have around 100 each. The offices are connected with fully meshed highspeed links two 10mbps, one 30mbps and the primary has a 50mbs. I find the site layout cleaner with protected DPs but some of my co-workers seems to be leaning for secondaries. Since the boundaries were already defined and the clients installed etc if we setup a secondary after the fact and we re-assign the boundaries to the secondaries would the clients even pickup up on that. Keep in mind that AD is not used for discovery etc, would we have push the client again? If the client was to be pushed again would we still assign the primary (I understand that they still get assigned to the primary but they associate to the secondary for MP etc? Any opinions? Thanks.

Hi, I would go for the secondary sites as well. Clients will still remain assigned to the primary site but will start to use the local site systems offered by the local secondary site server. Make sure you have the boundaries added to the secondary site and removed from the primary site (only for the remote sites). Clients will automatically pick up the changes.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Thank you for your reply. During the install the MP, SLP and site are all defined and pointed at the primary. Would this stay the same and just let the boundaries take over? Many of the clients roam between sites many of the offices local networks are unable to communicate with other offices local networks however all offices can communicate with the office of the primary. If a client roams to a site with a another secondary with different boundaries won't the client still try to communicate with his secondary? Keep in mind that they are not on the same domain so they should essentially be considered workgroup computers.

Check out this article on client roaming, it also contains some other scenarios - http://technet.microsoft.com/en-us/library/bb632476.aspxKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund