A quick heads-up for SCCM admins. I came across this nasty issue and together with a colleague we quickly resolved this issue before matters got worse.
Since the answer cannot be found on the Microsoft Support site at the time of writing, you can find it here.