We discovered the issue. This scenario is part of a rapid deployment of domain and lots of other components. While we had the network boundaries configured in SCCM properly, because the domain was a base "Default-First-Name-Site" only, part of our configuration did not include configuring the same subnets in AD for the site. Once the AD subnets were created, MECM deployed the client as expected.
Automatic site-wide client push doesn't execute
MECM 2303. Looking for help to understand why Automatic Site-Wide client push installation is not executing. After the site is created all boundaries, discovery methods, etc. are configured along with automatic client push configured. The computers are discovered and show in Devices. Selecting a device and choosing to install the client using the Client Wizard works with no issue. CCM log never indicates that the computers get queued for installation. The message shows: CCR count in queue "Incoming" is 0. Am I missing a prerequisite? Does the automatic installation only evaluate at a particular time? Any help is appreciated.
2 answers
Sort by: Most helpful
-
-
AllenLiu-MSFT 45,531 Reputation points Microsoft Vendor
2023-11-15T02:57:41+00:00 Hi, @ChadP
Thank you for posting in Microsoft Q&A forum.
Have we checked the option "Allow connection fallback to NTLM"? If not, try to check it to see if it helps:
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".