“Client deployment cannot be fulfilled since use of metered network is not allowed”

If your ccmsetup install of the SCCM Client fails and your ccmsetup.log file includes this error message, read on.

Failure when running ccmsetup.exe; ccmsetup service stopping immediately

Recently I was tasked with troubleshooting why an installation of the SCCM client was failing on a workstation at a remote location. The client push initiated from the Configuration Manager Console was not successful.

I connected to the workstation remotely using PowerShell. I confirmed C:\Windows\ccmsetup existed, and that the Windows service for ccmsetup was present but was currently stopped.

I deleted C:\Windows\ccmsetup\logs\ccmsetup.log and started the service again. It immediately stopped. I reviewed the newly created ccmsetup.log file and saw the following error message:

Client deployment cannot be fulfilled since use of metered network is not allowed

Check Metered Connection setting from Windows PowerShell

The workstation had a wired Ethernet connection on a company LAN; no computer should have a connection set as a metered network. I didn’t have access to the desktop UI at the time, so I ran the following from my Windows PowerShell remote session:

C:\>[void][Windows.Networking.Connectivity.NetworkInformation, Windows, ContentType = WindowsRuntime]
C:\>[Windows.Networking.Connectivity.NetworkInformation]::GetInternetConnectionProfile().GetConnectionCost()

ApproachingDataLimit : False
NetworkCostType : Fixed
OverDataLimit : False
Roaming : False
BackgroundDataUsageRestricted : False

The value of NetworkCostType was set to Fixed, which is equivalent to having Metered Connection enabled. The value should be Unrestricted when Metered Connection is disabled.

Disable Metered Connection from Windows Desktop UI

I couldn’t find a sure fire way to change the NetworkCostType setting from the command line (found some guidance indicating this could be done with netsh, but it required the Windows service Wired AutoConfig to be running, which it was not for this workstation.)

I ultimately ended up remoting into the desktop and checked the Network status:

This confirmed what we found in the ccmsetup.log and remotely in our Windows PowerShell session. To disable, I clicked Properties and toggled Set as metered connection from On to Off.

After disabling the metered connection, I started the Windows service ccmsetup again. This time the installation completed successfully.