I’m currently investigating some potential boundary issues related to the use of AD sites. Therefore I was looking for some more details on how content download is behaving considering slow and fast links in the environment.
This is some of the tests I did and the results thereof:
Action: Deploying software-package as available to a client which is within a slow boundary.
Result: Policy is received and entry in Software Center visible. Launching the installation gives following entry in the execmgr.log:
Action: Change the deployment options to Download content from distribution point and run locally when the client is within a slow or unreliable boundary. Refresh machine policy, and run the installation from Software Center again.
Result: This time execmgr.log immediately respondend with a successful content request.
And while digging further into LocationServices.log, do notice following entries:
Locality=’REMOTE’, which identifies the client as being in a slow and unreliable boundary, which in this case is very true, but the software deployment is still running because of the change of options on the deployment.
When a client is within a fast and reliable boundary of the site, the entry would look like this, as in the locality of the client is local.
Client logs to consider when troubleshooting boundaries and content download: