Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Force Client Deployment on metered network

We have several users who are ALWAYS on metered networks and will never get client updates.

The client deployment currently does not honour the option "Client Setting - Specify how clients communicate on metered network connections".

We need an option to override it for manual client deployment / update as well. (Force install checkbox doesn't work)

Setting the connection to "not metered" in Windows 8.1/10 doesn't work when a 3rd party connection software is used and doesn't work at all for TCT Mobile LTE sticks so this is not a solution.

43 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christoph von Wittich shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    10 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        We are experiencing the same behaviour, In Windows 10 1709, a user can set the Ethernet connection to a Metered connection. There is no GPO to prevent this. Once set the SCCM Client cannot install, As soon as it is removed, which you can only do from the OS the client installs without a error.

        This seems to be a major issue, as there is no way for a admin to control the users from doing this, and once set a admin needs to do a RDP session to remove.

      • Dennis Abbott commented  ·   ·  Flag as inappropriate

        This WMI setting is marked as Read-Write but it does not work, the provider comes back and says it is not-writeable.
        set-wmiinstance -class ccm_NetworkSettings -namespace root\ccm\clientsdk -Argument @{MeteredNetworkUsage=0}
        set-wmiinstance : Provider is not capable of the attempted operation
        + CategoryInfo : InvalidOperation: (:) [Set-WmiInstance], ManagementException
        + FullyQualifiedErrorId : SetWMIManagementException,Microsoft.PowerShell.Commands.SetWmiInstance

        Even checking the property with get-cimclass confirms that the ReadOnly flag is not there, this is not working as expected. Fixing this would make an easy solution.

        $a = get-cimclass -class ccm_NetworkSettings -namespace root\ccm\clientsdk
        $a.CimclassProperties['MeteredNetworkUsage']

        Name : MeteredNetworkUsage
        Value :
        CimType : UInt32
        Flags : Property, NullValue
        Qualifiers : {}
        ReferenceClassName :

      • Phil Chatham commented  ·   ·  Flag as inappropriate

        we still can't update the latest client to our mobile laptop estate!
        we really need a way to allow our client to be upgraded!

      • Bea commented  ·   ·  Flag as inappropriate

        For workaround you need to change locally the value of CCM_NetworkSettings locally on client to allow metered connection to be assigned and get the client settings policy

      • Chris Allison commented  ·   ·  Flag as inappropriate

        We have exactly the same issue, our devices are permanently on a metered connection and will never receive the upgraded client - please help!!

      • Phil Chatham commented  ·   ·  Flag as inappropriate

        This would be so Usefull!!

        We have so many mobile only devices...

        We can allow deployments via the Client settings - but we can never get the client upgraded or repaired even when specifying a local /source

      • Phil Chatham commented  ·   ·  Flag as inappropriate

        This would be so Usefull!!

        We have so many mobile only devices...

        We can allow deployments via the Client settings - but we can never get the client upgraded or repaired even when specifying a local /source

      • Nishan Gonsalkorale commented  ·   ·  Flag as inappropriate

        I know this was nearly a year ago, but did you ever figure this out?
        My problem is maybe the other way around, but the behaviour i'm seeing doesn't really make sense!
        I have machines that are sometimes on a metered connection. All deployments are 'required'. According to what I've read (and since tested) when I set the client settings to 'Limit' it allows all deployments when they've reached their deadline! Well, that's all of ours, so what's the point in the tick box in deployments that states that it allows deployment on metered connection when deadline is reached...it always would!?
        I'm struggling to get metered connection clients to receive SCEP definitions and occasional patches through Direct Access and yet deny all the rest unless they're connected locally to the LAN...

      Feedback and Knowledge Base