xc3ss1v3 Posted September 25, 2014 Report post Posted September 25, 2014 Hello all.. I've started configuring distribution points to be placed in out-lying offices so that the local clients do not always have to come across the WAN to get deployments (obviously). Everything has gone swimmingly setting up the DP's, distributing content to them, etc.., until I tried actually putting one to good use. The first DP got deliver to the outer office this morning and after attaching to the network and defining the boundary it's assigned to, it seems that clients are no longer able to download and install anything. For instance, on a machine I'm using to test, two different packages are sitting at "downloading information" and have not moved. These two packages both install normally in other offices that aren't assigned to that boundary and DP. If I pull the DP out of loop (remove the boundary assignment), everything works fine. So, I'm guessing there is some kind of configuration setting that I'm missing. As of now, it's distribution point role is set up nearly identical as my Primary Site Server's distribution point role with the exception of PXE boot, multicast, prestaged content, etc... For troubleshooting outside of what's already been said, on the client machine, I've tried connecting to the folder share via the web and I could connect to the Primary Site Server's share, but not the distribution point's share. Going into the ContentTransfer log I don't see any errors, just messages stating that it's trying to connect to the both the DP and the PSS. Any help would be greatly appreciated. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted September 26, 2014 Report post Posted September 26, 2014 Do I understand it correctly that you can't connect to the DP, from the client, since the move? If so, is the client resolving the DP to the right IP? Quote Share this post Link to post Share on other sites More sharing options...
xc3ss1v3 Posted September 26, 2014 Report post Posted September 26, 2014 Do I understand it correctly that you can't connect to the DP, from the client, since the move? If so, is the client resolving the DP to the right IP? Yes I can connect to the client from anywhere. Whether it be while remotely or locally. It's just that it appears the SCCM clients can't connect to the DP as installations just hang and the downloading steps. I did fail to mention that the DPs are all Windows 7 x64 boxes. I did verify that IIS is installed (evidenced by inetpub existing), however I do not see the IIS Manager in Control Panel > Administrative tools. Could this be indicative of a problem with IIS? *Edit -- In looking at Windows Features, IIS is not checked. ): Quote Share this post Link to post Share on other sites More sharing options...
xc3ss1v3 Posted September 26, 2014 Report post Posted September 26, 2014 Yes I can connect to the client from anywhere. Whether it be while remotely or locally. It's just that it appears the SCCM clients can't connect to the DP as installations just hang and the downloading steps. I did fail to mention that the DPs are all Windows 7 x64 boxes. I did verify that IIS is installed (evidenced by inetpub existing), however I do not see the IIS Manager in Control Panel > Administrative tools. Could this be indicative of a problem with IIS? *Edit -- In looking at Windows Features, IIS is not checked. ): After manually configuring IIS on that DP and also allowing web traffic through the firewall, applications have begun to install. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted September 26, 2014 Report post Posted September 26, 2014 Makes sense, as IIS is a core component of a DP. Quote Share this post Link to post Share on other sites More sharing options...
