I just added a Windows 10 Enterprise client to our domain and have waited for over 3 hours and Client Push has not installed it. It is discovered in SCCM with AD System Discovery. I've been watching ccm.log and every hour it retries a handful of systems but not the new one I just added.

I can manually push the client out from the console and that is successful. Could there be some issue with Windows 10 and client

What version of ConfigMgr are you running? To be supported, you need to be at 2012 SP2 or 2012 R2 SP1.

We're running SCCM 2012 R2 SP1 CU1.

Another question, now that I have your ear, I wonder if your ConfigMgrStartup Script works on Windows 10 clients?

My client installation script works on all OSes.

For the issue above, is the resource assigned to your site (before it gets the agent)?

Thanks for the script answers.

Yes, the record in SCCM showed that it was assigned to my site. It was in a good boundary as well. Every hour SCCM tried to reinstall to the same systems but mine was not among them. Maybe it was a fluke. I'll try another system and see if I'm getting the same result.

What does the resource record in ConfigMgr tell? Client = yes, so was an existing client just reinstalled?

The resource record shows Client is null, empty. Last night I deleted the system from AD and SCCM and reimaged a machine fresh. This morning it's still sitting uninstalled. Ccm.log doesn't show any activity towards installing (unless I manually force it from the SCCM console). The ip range is in a border as well. I had read that I should check out smsprov.log for more clues. Is that a good strategy?

On the site server, what sort of errors are you seeing in CCM.log for this resource?

That's the odd thing. I see no record of the resource in ccm.log. CCR.box is empty and ccrretry.box has about 10 records however they're over a week old.

That is odd, records should be automatically deleted after a week from there. They retry every hour for a week and are supposed to then go away. Very curious. Have you tried deleting this record from the console, and then running AD system discovery again? It may also be worth deleting the contents of ccrretry.box if they are all older than a week

I have deleted the record from the console. Several times. AD system discovery finds them again and they sit dutifully waiting for a client. I've emptied ccrretry.box as well.

I've fallen back on Jason Sandys ConfigMgrStartup script that is doing a nice backup job for Client Push. Don't know what I'd do without it.

When I have some time, I'll open a support ticket with MS and see what they can find.

What OS is listed in the resource after AD System Discovery picks it up?

It is detected as Windows 10 Enterprise 10.0

When the client is installed it changes to Microsoft Windows NT Workstation 10.0 (Tablet Edition)