Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Provide an option to automatically upgrade Client versions on PullDP

We found some strange behavior's when having a Pull DP deployed and will deploy a SCCM Agent later. This occurs only when the newest Client version has not been upgraded to production.
According to https://technet.microsoft.com/en-us/library/gg712321.aspx> the versions must be the same.
---
On a computer that is configured as a pull-distribution point and that runs a Configuration Manager client, the version of the Configuration Manager client must be the same as the Configuration Manager site that installs the pull-distribution point. This is a requirement for the pull-distribution point to use the CCMFramework that is common to both the pull-distribution point and the Configuration Manager client.
---

Ask: can't we make sure that all agents in the infrastructure run the latest client version.

Workaround for now is to add all PullDP servers to the Pilot collection to ensure they are upgraded in a timly manner.

38 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Marco Cibis (MS) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • Anil Abraham commented  ·   ·  Flag as inappropriate

    Rather than an option to upgrade all the clients automatically, I think we should upgrade the Pull DP clients by default and have a dashboard item that shows the client versions on Pull DPs. But there should be a solution when the requirement is very clear about the client versions on Pull DP.

Feedback and Knowledge Base