Hi John,
I would say it does matter. I have the same situation here in my environmnet.
When the machine is discovered in one site, it can contact its local DP and download the package. However, when it is discovered in other region, the machine is in roaming state. IN such case as per the BOOK we can say that it will reach out to the local
DP of that site. But practically it doesnt. IN our case it fallsback directly to the Primary DP. Thus, the client keeps toggling between the local site DP which is assigned to it as per the policy and the primary DP where it tends to fallback to get
the package when on a roaming site.
I can clearly see this toggling between the site in the CAS and Location Service logs, where i see 2 DP listed instead of just one LOCAL DP.
And in turn its throwing out an error of SQL JOb error, trust me there are no other errors listed in any of the logs.