PENDING Windows 10 Clients installation issue on SCCM (1902)

[seraphicus]

Hey all,

Does anybody know this problem with windows 10 clients with sccm 1902?

The clients pc show up in the monitoring tool with no configuration management client installed, even it is. I did it manualy. after the manual installation it show up for about 30min Client Active. Then it losts the status to unknown (Client not instsalled).

Sometimes the client PC show up again as available, but with wrong currently logged user, and its listed twice, as connected client and unknown client, without client installed. This drives me crazy... you know something similar, or can give a hint to solve this ?

The sccm works fine with dozens of windows 7 clients.

1000 thanks for every hint.

Kind regards,

Harald

 

[Youssef Saad]

Hi Harald,

Did you have installed the latest Hotfix Rollup for 1902?
What is the version of your Windows 10 clients? (open the CMD and type winver)
Do you have the same issue with all Win10 clients?
On one of these, check the LocationServices.log to ensure that your client have already the correct information about your Management Point, SUP... (%WINDIR%\CCM\Logs)

 

[seraphicus]

Hello Youssef,

I've realise that we've got a lot of problems with the 1803 release of WIN10. The 1903 works perfect. So i roll out for new maschines the 1903.

Now, i'm not able to deploy to this Ghost machines (1803 wich has a client installed but in sccm the are visible as with no client installed) with the 1903 release. Strange: even the 1803 get the Patches from our sccm and install them, but they dont get the 1903 feature update. I created a simple deploment under 'All Windows 10 Updats/Feature update .....' It worked for some older win10 version, but not with the machines with 1803.

how can i force this 1803 to upgrade to the working 1903 release ?

thanks for your help,

Harald

 

[Youssef Saad]

You can use an in-place upgrade to Windows 10 1903.

Refer to this: https://www.prajwaldesai.com/in-place-upgrade-to-windows-10-enterprise-with-sccm/

 

[Edy]

@seraphicus have a look at this https://2pintsoftware.com/download/configmgr-ci-local-policy-corruption/

to confirm, logon to one of the machines and check if Registry.pol is today's date. if its not then the pol is broken.

sometimes, the policy gets corrupted and needs to be re-created.