This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 15%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFZ%3C/text%3E%3C/svg%3E)
I've been trying to solve this error for days, but without success. I configured my firewall
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 57.99999999999999%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELA%3C/text%3E%3C/svg%3E)
there is no problem from your side mate!
i found the culprit after weeks of mess at work
Cummulative Updates!
From June 2022 Cummulative Update onwards to July and now August it is still present!
Reverting to May 2022 Cummulative Update fixes the issue!
But this is a workaround of course not a solution!
Cheers
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 44%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Hey, Lala , Is that true??
it was but eventually i found the real culprit the sccm server didn't have the latest cummulative update installed so there was a discrepancy between authentication levels client-server. after patching the windows server os to the latest cummulative update everything was fixed. cheers
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 6%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECZ%3C/text%3E%3C/svg%3E)
update system patch
should file and printer sharing and WMI be configured in the AD GPO?
Hi,
1, Can we manually install the client agent? It's firstly recommended to add at least one client push installation account under Administration > Site Configuration > Site > Settings > Client Installation Settings > Client Push Installation to have a try. This account must be a member of the local Administrators group on the target client computers. You can specify more than one client push installation account. Configuration Manager tries each one in turn until one succeeds.
Refer to: Client push installation account
2, As we can't see Started service "ccmsetup" in ccm.log, then that means that the client installation requirements are not met. Please refer to the points below for the Client Push installation pre-requisites:
a, Add the File and Printer Sharing and Windows Management Instrumentation (WMI) as exceptions to the Windows Firewall.
b, Make sure that there are no DNS issues
c, Firewall is not blocking the SMB traffic
d, Make sure the RPC port 135 and the Dynamic port range is opened in any firewall between the client and the server including the windows firewall.
Refer to: Troubleshooting SCCM ..Part I (Client Push Installation )
Hope it helps. Thanks for your time.
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi,
Thanks for your reply.
1,==>should file and printer sharing and WMI be configured in the AD GPO?
It's depended on your environment. In fact, we at last need to ensure the firewall exceptions on the clients.
2, How about adding the client push installation account? Does it work?
3,Does manual client installation work? If yes, here is a similar thread for your reference. The solution is to change the NTFS and sharing permissions of the %ConfigMgr InstallDir%\EasysetupPayload folder which contains the latest client installation files.
MEMCM 2203 Client does not install
Hope it helps. Thanks for your time.
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi,
Just checking in to see if there is any update. We haven't heard from you for a few days and would like to know the current status of the problem. Is the problem solved? Do you need any further assistance? Look forward to hearing from you.
Thanks for your time.
Best regards,
Simon
Sorry for the delay, I was on vacation. the problem has not yet been resolved. I'm having the same problem.
I verified that I had DNS records for the same IP, but it removes a record but the problem remains
Hi,
Thanks for your reply.
Can we manually install SCCM client agent on the machine "LAPTO-01"? If yes, please help check if the pre-requisites are met.
Thanks for your time. Have a nice day!
Best regards,
Simon
Good Morning,
I already install the Agent Manually on the Machine, what's the next step to follow
Hi,
Thanks for your reply. As the manual installation works, it means some pre-requisites are not meet. Please firstly check the firewall and port configurations to make sure they are not blocked. And also configure the client push installation account to have a try.
Thanks and regards,
Simon