Has anyone found root cause or a solution to this issue? We're seeing this with SCCM 1902 when re-imaging existing workstations with Windows 10 1809. Two workarounds: delete the existing SCCM computer object BEFORE re-imaging or repair/reinstall the SCCM client after the imaging process.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.