MEMCM 2203 Client does not install

Duchemin, Dominique 2,006 Reputation points
2022-06-18T19:17:54.767+00:00

Hello,

MEMCM 2203 + KB14480034
Installation by right client > Install Client from the Primary Server

I can't install the MEMCM Client on client on a new domain...

  • Certificate installed and valid
  • Boundaries exists and assigned to a group

Site Server:

  • Administration > Site Configuration > Site > Settings > Client Installation Settings > Client Push Installation

212731-memcm-test-client-push-settings-01.png

  • Installation Properties
    SMSSITECODE=UCT DNSSUFFIX=adtest. SMSMP=VITSCCMCB.adtest CCMHOSTNAME=SCCMTinternet.adtest FSP=VITSCCMCB.adtest

Client:

Firewall Off

212705-memcm-test-client-push-settings-02.png

The account is Local Administrators

212713-memcm-test-client-push-settings-03.png

212667-2022-06-17-19-59-44-memcm-mits-server-service-acco.png

===========================================================================

Ccm.log:

======>Begin Processing request: "2097152030", machine name: "VITINTUNE01" SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
Execute query exec [sp_IsMPAvailable] N'UCT' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01.adtest\admin$' using account 'ADTEST\svcconfigmgrdts' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> NetUseAdd failed: 1909: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account ADTEST\svcconfigmgrdts (00000775) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01.adtest\admin$' using account 'ADTEST\svcconfigmgrsrv' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> NetUseAdd failed: 1909: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account ADTEST\svcconfigmgrsrv (00000775) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01.adtest\admin$' using account 'ADTEST\svcconfigsrvna' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> NetUseAdd failed: 1909: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account ADTEST\svcconfigsrvna (00000775) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01.adtest\admin$' using account 'AD\svcconfigmgrdts' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> NetUseAdd failed: 1326: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:16 PM 5052 (0x13BC)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svcconfigmgrdts (00000005) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01.adtest\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> Failed to connect to \VITINTUNE01.adtest\admin$ using machine account (5) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> ERROR: Failed to connect to the \VITINTUNE01.adtest\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01\admin$' using account 'ADTEST\svcconfigmgrdts' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> NetUseAdd failed: 1909: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account ADTEST\svcconfigmgrdts (00000775) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01\admin$' using account 'ADTEST\svcconfigmgrsrv' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> NetUseAdd failed: 1909: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account ADTEST\svcconfigmgrsrv (00000775) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01\admin$' using account 'ADTEST\svcconfigsrvna' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> NetUseAdd failed: 1909: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account ADTEST\svcconfigsrvna (00000775) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01\admin$' using account 'AD\svcconfigmgrdts' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> NetUseAdd failed: 1326: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svcconfigmgrdts (00000005) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> Attempting to connect to administrative share '\VITINTUNE01\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> Failed to connect to \VITINTUNE01\admin$ using machine account (5) SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> ERROR: Failed to connect to the \VITINTUNE01\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
---> ERROR: Unable to access target machine for request: "2097152030", machine name: "VITINTUNE01", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
Execute query exec [sp_CP_SetLastErrorCode] 2097152030, 5 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
Stored request "2097152030", machine name "VITINTUNE01", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152030, 2 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
Execute query exec [sp_CP_SetLatest] 2097152030, N'06/18/2022 02:53:17', 40 SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)
<======End request: "2097152030", machine name: "VITINTUNE01". SMS_CLIENT_CONFIG_MANAGER 6/17/2022 7:53:17 PM 5052 (0x13BC)

---------------------------------------------------------------------------------------------------------------------------------

Which other logs could give some clue on this?

The folder C:\Windows\ccmsetup is even not created on the client. Which logs on the Site Server will give me information about the issue?

I tried the Run
from the site server

  • \Client\C$
  • \Client\Admin$

from the client
\Site Server\C$
\Site Server\c$\Program Files\Microsoft Configuration Manager\Client

Port 135 & 445 are opened.

Everything works...

Thanks,
Dom

Microsoft Configuration Manager
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Simon Ren-MSFT 30,496 Reputation points Microsoft Vendor
    2022-06-20T11:24:39.84+00:00

    Hi,

    Thanks for posting in Microsoft MEM Q&A forum.

    1,Can we manually install the client agent? 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:
    Troubleshooting SCCM ..Part I (Client Push Installation )

    2,Does the problematic machine reside in another forest? If yes, please refer to the cross-forest support:
    Cross Forest Support in ConfigMgr 2012 Part 1: Simple Management

    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.

    1 person found this answer helpful.
    0 comments No comments

  2. Simon Ren-MSFT 30,496 Reputation points Microsoft Vendor
    2022-06-23T10:12:42.497+00:00

    Hi,

    Thanks for your information.

    As the manual installation works, I assume something is blocked between the server and client. Please check below options:

    1,Add the File and Printer Sharing and Windows Management Instrumentation (WMI) as exceptions to the Windows Firewall.
    2,Make sure that there are no DNS issues
    3,Firewall is not blocking the SMB traffic
    4,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.

    Hope it helps. Thanks for your effort and 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.

    1 person found this answer helpful.

  3. Simon Ren-MSFT 30,496 Reputation points Microsoft Vendor
    2022-07-05T17:05:39.313+00:00

    Hi,

    Thanks very much for your feedback. We're glad that the question is fixed now. It's appreciated that you could click "Accept Answer" to the helpful reply, this will help other users to search for useful information more quickly. Here's a short summary for the problem.

    Problem/Symptom:
    Client push installation fails in MEMCM version 2203 while manual installation works.

    Solution/Workaround:
    Change the NTFS and sharing permissions of the %ConfigMgr InstallDir%\EasysetupPayload folder which contains the latest client installation files.

    Reference Links:
    Understand and troubleshoot Updates and Servicing in Configuration Manager
    Troubleshooting SCCM ..Part I (Client Push Installation )

    Thanks again for your time! Have a nice day!

    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.

    1 person found this answer helpful.
    0 comments No comments

  4. Duchemin, Dominique 2,006 Reputation points
    2022-06-20T17:43:30.927+00:00

    Hello,

    1. I could try to install the Client manually & locally
    2. No the Configuration Manager server and the Clients are in the same Forest & same domain ADTEST.

    Thanks,
    Dom


  5. Duchemin, Dominique 2,006 Reputation points
    2022-06-23T01:41:31.9+00:00

    Hi,

    1. The manual installation works:

    <![LOG[Deleted file C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi.download]LOG]!><time="18:37:32.615+420" date="06-22-2022" component="ccmsetup" context="" type="1" thread="4868" file="ccmsetup.cpp:10688">
    <![LOG[Deleted file C:\Windows\ccmsetup\client.msi.download]LOG]!><time="18:37:32.616+420" date="06-22-2022" component="ccmsetup" context="" type="1" thread="4868" file="ccmsetup.cpp:10688">
    <![LOG[Task 'Configuration Manager Client Upgrade Task' does not exist]LOG]!><time="18:37:32.617+420" date="06-22-2022" component="ccmsetup" context="" type="0" thread="4868" file="wintask.cpp:564">
    <![LOG[Could not retrieve value for MDM_ConfigSetting . Error 0x80041013]LOG]!><time="18:37:32.641+420" date="06-22-2022" component="ccmsetup" context="" type="2" thread="4868" file="ccmcomgmt.cpp:952">
    <![LOG[CcmSetup is exiting with return code 0]LOG]!><time="18:37:32.642+420" date="06-22-2022" component="ccmsetup" context="" type="1" thread="4868" file="ccmsetup.cpp:11819">

    And reports to the console...

    214113-2022-06-22-20-33-16-vitintune01-installation.png

    Thanks,
    Dom

    0 comments No comments