Thanks. I will have to deploy my clients with a GPO it seems. If I turn on automatic client push installation on the secondary site, then the secondary site will push clients to machines in the primary site across the WAN.

If I turn on automatic client push installation on the secondary site, then the secondary site will push clients to machines in the primary site across the WAN. Not at all. Just like the primary site not pushing to the secondary site systems because they are not in its boundary, secondary sites won't push to clients in the primary's boundaries. Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

With manual client push installation, you cannot push from the secondary site. With automatic client push installation, it can be configured to push from the secondary site: http://myitforum.com/cs2/blogs/jgilbert/archive/2007/02/22/sms-2003-client-push-installation-method-explained.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I have a primary site and a secondary site. These are both in the same AD forest, spread across a WAN with two distinct AD sites. The primary management point boundaries are set to one AD site, and secondary proxy MP is set to the other AD site. I am doing testing, using a desktop on the secondary AD site. It was discovered from the secondary MP site using AD system discovery. It shows up in the collection as being assigned properly to the secondary site code. When I do a client push install, if I leave the box "include only clients in this site's boundaries" checked, nothing happens and nothing is written to either servers ccm.log file. If I uncheck this box, it tries to push from the primary site. How can I configure this so that systems within the boundaries of the secondary site have the client pushed from the secondary management point? Thanks!