Windows 10: SCCM Co-management

Hi,


We have recently started to move all our devices to a co-managed state to leverage the additional functionality that Intune will be able to provide our organisation in terms of managing our Windows 10 devices. The move has been quite easy with very little issues, however I have a couple of devices that just won't receive the 2004 feature upgrade since becoming co-managed. These devices receive both quality and driver updates via Intune without any issue, but just won't display the feature update. All of them are running 1909 and have the latest CU, SSU's installed


There isn't any blockers present on these devices as I have ran the 2004 media to ensure that there was no issues with any drives, disk space etc and they all passed. I have repaired the SCCM client and reinstalled it to no avail, I really don't want to rebuild these devices, but at the moment it seems like the only option that I have left. Has anyone else experienced a similar issue?


Thanks


Billy

:)

 

Execute a command from SCCM Task sequence step "Run a Command line"

Hi,

Thanks for your suggestion.

That will work indeed, however I need to run it from the SCCM Task Sequence's Run Command Line Step and I am not able to figure out how to do that.

Can we change line while executing command from SCCM Task Sequence's Run Command Line Step?

Regards

 

How to activate SCCM server license

The SCCM server is already installed. And I am to activate the license but I never had experience.

Could you please provide step by step procedure to activate SCCM server license?

 

SCCM Local Policy - BITS

Managing BITS policy for clients can be done several ways - just a few listed here:

1. Group Policy template
2. Local Policy template
3. registry
4. and more...

SCCM client settings for BITS uses local policy to enforce the BITS agent settings.

Consider the following scenario:

SCCM client settings contains BITS settings for max throttle, start and stop times, etc...

SCCM Client settings also have the "Limit the maximum network bandwidth for BITS backgrounds transfers" set to "NO" so, effectively no settings that are configured are actually being enforced.

This is working fine. Here's the issue:

If I fun the following command:

GPResult /scope computer /h file.htm

... the output file will show that this local setting is "enabled" and appears it is enforced.

The setting is not enforced but the reporting mechanism thinks it is. I'm considering this a bug. This burned a customer and cost them several hours of troubleshooting where this setting was coming from because they swore that SCCM was not setting it.