Dear Forum,
In the last couple of weeks I have been installing, configuring and migrating SCCM from Windows Server 2008 R2 to Windows Server 2012 R2. Since we have quite an complex environment we use quite a lot of the SCCM features, though it seems that one of the core functions of SCCM struggles once the feature Pull Distribution was enabled. Let me explain this in a bit more depth.
As everyone who has implemented or used SCCM knows, every package, application, boot image etc. needs to be distributed to either one or more distribution point, be it remote or local. If data is not available on the distribution points your clients won't receive the content, be it pull or push, and installations nor updates will occur. So being able to update and distribute content to the distribution point is essential. In our environment this works just fine on both the original 2008 R2 installation and the newly (migrated) 2012 R2. Since the SCCM on Windows Server 2012 R2 will be our new SCCM once it goes into production, this is the one I will focus on for this post. This SCCM has been updated to the latest version (1606) and up to date with Windows Updates (including other Microsoft Products).
Now once the Pull Distribution Point function is enabled this process of distributing contect to the distribution point comes to a halt during the "In Progress" fase. The SCCM Console concludes the following: "Distribution Manager Instructed Package Transfer manager to send package xxxxx to distribution point..." As far as the eye can see there arn't any errors in the logs, but I might be looking in the wrong ones.
Does anyone know what I might be doing wrong, what I should reconfigure or how I am able to troubleshoot this problem. I am able to share logs when required, but I have not found any error that could cause such a problem in the following logs: distmgr.log, SMSProv.log and PkgXferMgr.log. Obviously I could be overlooking something so don't be afraid to ask about these logs if you think I should be able to find my answer or a lead to a solution there.
With kind regards,
Henk