What's new
Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING New SCCM Install Client Push error

  • Thread starter Thread starter desolation
  • Start date Start date
  • Replies Replies 6
  • Views Views 4K
desolation

desolation

Member
Messages
6
Solutions
1
Reaction score
0
Points
1
Greetings all,

I'm trying to wrap my head around how to fix this issue, and it's driving me CRAZY. I'm in a new environment, and our old SCCM server took a massive L, so I completely rebuilt SCCM on a new VM. We have also have 4 domains with 566 computers

When I push the client out to devices, all but 3 machines received it, it's the same error over and over and over. My Client Push account is administrators on machines, it has the correct username/passwords too. As it did work perfectly fine on 3 machines. Below are the errors I get constantly anytime I try push the client.

I am at a complete loss here, I've been tearing into this for 4 days now and I am so stuck and lost I don't know what else to do. Please help me if possible

Execute query exec [sp_IsMPAvailable] N'KWJ' SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x3) SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> Attempting to connect to administrative share '\\LCP06KW00036.kwajalein.local\admin$' using account 'KWAJALEIN\SCCM-ClientPush' SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> NetUseAdd failed: 53: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account KWAJALEIN\SCCM-ClientPush (00000035) SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> The device LCP06KW00036.kwajalein.local does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x3) SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> Attempting to connect to administrative share '\\LCP06KW00036\admin$' using account 'KWAJALEIN\SCCM-ClientPush' SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4660 (0x1234)
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4660 (0x1234)
Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4660 (0x1234)
---> NetUseAdd failed: 53: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account KWAJALEIN\SCCM-ClientPush (00000035) SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
---> The device LCP06KW00036 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
---> ERROR: Unable to access target machine for request: "2097152051", machine name: "LCP06KW00036", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
Execute query exec [sp_CP_SetLastErrorCode] 2097152051, 53 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
Stored request "2097152051", machine name "LCP06KW00036", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152051, 2 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
Execute query exec [sp_CP_SetLatest] 2097152051, N'12/17/2022 01:40:45', 2 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
<======End request: "2097152051", machine name: "LCP06KW00036". SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
 
Solution
desolation
Garth said:
Error 64 (hex) = Cannot create another system semaphore.
Error 64 (dec) = The specified network name is no longer available.
Click to expand...
Figured out the issue. Old SCCM site code was still lingering on machines, pushed a package out to update the site code to new site code. and now it's working
Sort by date Sort by votes
Garth said:
Check DNS has the right IP or the name.
Click to expand...
Funny enough, it does look like a DNS problem. I'm facing major DNS issues across the entire environment. We have 4 domains, and one domain seems to have a DNS issue, but for the others I don't see anything wrong with DNS, so i'm still not sure why I get the errors
 
Upvote 0 Downvote
desolation said:
Greetings all,

I'm trying to wrap my head around how to fix this issue, and it's driving me CRAZY. I'm in a new environment, and our old SCCM server took a massive L, so I completely rebuilt SCCM on a new VM. We have also have 4 domains with 566 computers

When I push the client out to devices, all but 3 machines received it, it's the same error over and over and over. My Client Push account is administrators on machines, it has the correct username/passwords too. As it did work perfectly fine on 3 machines. Below are the errors I get constantly anytime I try push the client.

I am at a complete loss here, I've been tearing into this for 4 days now and I am so stuck and lost I don't know what else to do. Please help me if possible

Execute query exec [sp_IsMPAvailable] N'KWJ' SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x3) SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> Attempting to connect to administrative share '\\LCP06KW00036.kwajalein.local\admin$' using account 'KWAJALEIN\SCCM-ClientPush' SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> NetUseAdd failed: 53: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account KWAJALEIN\SCCM-ClientPush (00000035) SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> The device LCP06KW00036.kwajalein.local does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x3) SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> Attempting to connect to administrative share '\\LCP06KW00036\admin$' using account 'KWAJALEIN\SCCM-ClientPush' SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:43 PM 4004 (0x0FA4)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4660 (0x1234)
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4660 (0x1234)
Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4660 (0x1234)
---> NetUseAdd failed: 53: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account KWAJALEIN\SCCM-ClientPush (00000035) SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
---> The device LCP06KW00036 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
---> ERROR: Unable to access target machine for request: "2097152051", machine name: "LCP06KW00036", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
Execute query exec [sp_CP_SetLastErrorCode] 2097152051, 53 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
Stored request "2097152051", machine name "LCP06KW00036", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152051, 2 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
Execute query exec [sp_CP_SetLatest] 2097152051, N'12/17/2022 01:40:45', 2 SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
<======End request: "2097152051", machine name: "LCP06KW00036". SMS_CLIENT_CONFIG_MANAGER 12/17/2022 1:40:45 PM 4004 (0x0FA4)
Click to expand...
Alternatively, may be worth trying GPO start-up script to install client:
eskonr.com

SCCM Configmgr How to implement Jason Sandys Client Startup Script to achieve good client success rate

Recently ,I worked on on a SCCM project and as initial step ,it was mandatory to bring all the desktops and servers (where ever it was missing) into SCCM with Client installed. Though ,there are di…
eskonr.com eskonr.com
 
Upvote 0 Downvote
Error 64 (hex) = Cannot create another system semaphore.
Error 64 (dec) = The specified network name is no longer available.
 
Upvote 0 Downvote
Garth said:
Error 64 (hex) = Cannot create another system semaphore.
Error 64 (dec) = The specified network name is no longer available.
Click to expand...
Figured out the issue. Old SCCM site code was still lingering on machines, pushed a package out to update the site code to new site code. and now it's working
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

Similar threads

  • PENDING CcmSetup failed with error code 0x80004005
  • PENDING SCCM 2503 – Network Boot Sometimes Fails to Get IP Address (PXE issue)
  • PENDING SCCM Upgrade 2503 Issue - Stucked
  • SOLVED Application hanging during SCCM task sequences with OS deployments 24H2 or 25H2
  • SOLVED SQL Server 2025 support for SCCM

    • Forum statistics

    Threads
    7,150
    Messages
    27,919
    Members
    18,221
    Latest member
    pconleynms

    Latest posts

    Trending content
    Back
    Top