Advanced clients are not connecting to the Local Distribution Point.

[skclark]

I have read the previous post:

http://www.tek-tips.com/viewthread.cfm?qid=1144499&page=2

(among others)

In the locationServices.log the clients are coming across the wan to the Site Server instead of using the local distribution point configured on a file server in that location.

I have configured IIS with BITS on the remote file server and configured it as a Distribution Point under site systems on the Primary Site Server. I configured the roaming boundaries as local for the distribution point and also set the Distribution point as protected and selected the applicable AD site. There are no other roles configured for the remote distribution point and I am able to update the distribution points and the packages push.

Can anybody think of anything to try?

 

[tbrennans]

Are those boundaries also in the primary site DP range?

 

[skclark]

I'm not sure, where would I check? If I have the site properties open under site boundaries I have all the sites listed, remote and the primary sites. Under Roaming Boundaries all the sites are listed as well. I had them all set to "remote roaming boundary" and changed them to local roaming boundary for troubleshooting purposes. I also set them to protected DPs and added ONLY the AD site that was local to the DP.

I can push a package to the DP without error and I checked the permissions on the sms package share to confirm there wasn't a permissions issue. (SMSPKGC$). In the locations log file it reports the DP as remote for some reason. I am sure I have misconfigured something somewhere but I can't seem to find any documentation on deploying a remote DP.

 

[tbrennans]

In the SMS console primary, site settings | site systems | select your primary site server and look at the DP tab down in the configure boundaries and make sure they dont overlap with your new DP.

 

[skclark]

I have confirmed that the DPs are not overlapping.

I am just curious, do I have to have the remote files servers that I have configured as Remote DPs also configured as MPs?

I can create a package and the package is copied to the remote DP without issue. However, if I create a package and choose that remote DP that is local to the SMS advanced client in that AD site it fails to copy. The actuall error in execmgr.log is OnContentAvailable program (package name)NOT available, 0x80091007?

 

[mib147]

From what I understand, it seems to be working like it should. When a client goes to install a package, it asks AD where are my DPs. If there are multiple DPs for its assigned SMS site, it will just randomly pick one. The only thing you accomplish by protecting the DP is other clients that do not fall under those boundaries cannot access that DP. It does not force the clients that fall under those boundaries to use that DP. The only way to accomplish to do what you are trying to do is to make the remote DP a secondary site. It costs nothing as far as licenses go.

If I am wrong I am sure tbrennans will let me know

 

[skclark]

Thank you for taking the time to respond. I have opened a support call with Microsoft and it turns out it isn't a DP problem. Some of the steps taken to troubleshoot the issue where to provide the SYSTEM account rights to the smspkg$ share, create an account for software distribution, and a whole lot of package testing. For some reason I couldn't download to the client cache but if I let it install from the DP it works without issue. I have been able to get it to work after doing an install from the DP so it's a mystery as to why it works now. Thanks again for providing suggestions that have helped in troubleshooting the issue.