Client installs but doesn't set site code

[ATeamM]

I get my client to install but it's not setting a site code. The client has installed ok on most servers and on one client machine out of 200.

Boundries are configured, schema is extended, and I have permissions set in AD for the SCCM server. All these clients were apart of a different sitecode with a different server. That server had corrupt OS files the Microsoft couldn't fix and told me to reinstall the server with a new server name, sitecode, and IP.

On my machine I have run the ccmsetup /uninstall and pushed the client from the server. It doesn't show the server and has no site code. On machines that I didn't manually do an uninstall still show the old server and sitecode in Configuration Manager.

I seem to be having permissions issue even though for the testing I am using a domain admin account.

 

 

On my client the ClientLocation.log just says.

Current AD forest name is sweco.corp, domain name is sweco.corp    ClientLocation    10/5/2017 8:41:44 AM    13496 (0x34B8)
Domain joined client is in Intranet    ClientLocation    10/5/2017 8:41:44 AM    13496 (0x34B8)
Getting Assigned Site    ClientLocation    10/5/2017 10:10:50 AM    13368 (0x3438)
 

 

 

CCM.log for the same client shows

======>Begin Processing request: "2097152272", machine name: "SWECO715WIN10"    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:38:59 AM    12096 (0x2F40)
Execute query exec [sp_IsMPAvailable] N'SWE'    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:38:59 AM    12096 (0x2F40)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:38:59 AM    12096 (0x2F40)

---> Attempting to connect to administrative share '\\SWECO715WIN10.sweco.corp\admin$' using account 'sweco.corp\administrator'    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:38:59 AM    12096 (0x2F40)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account sweco.corp\administrator (00000035)    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:38:59 AM    1344 (0x0540)
---> Connected to administrative share on machine SWECO715WIN10.sweco.corp using account 'sweco.corp\administrator'    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:00 AM    12096 (0x2F40)
---> Attempting to make IPC connection to share <\\SWECO715WIN10.sweco.corp\IPC$>    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:00 AM    12096 (0x2F40)
---> Searching for SMSClientInstall.* under '\\SWECO715WIN10.sweco.corp\admin$\'    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:00 AM    12096 (0x2F40)
---> System OS version string "10.0.10586" converted to 10.00    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:00 AM    12096 (0x2F40)
---> Unable to connect to WMI (root\ccm) on remote machine "SWECO715WIN10.sweco.corp", error = 0x8004100e.    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:00 AM    12096 (0x2F40)
---> Creating \ VerifyingCopying existence of destination directory \\SWECO715WIN10.sweco.corp\admin$\ccmsetup.    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:00 AM    12096 (0x2F40)
---> Copying client files to \\SWECO715WIN10.sweco.corp\admin$\ccmsetup.    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:01 AM    12096 (0x2F40)
---> Copying file "D:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf"    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:01 AM    12096 (0x2F40)
---> Copying file "D:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe"    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:01 AM    12096 (0x2F40)
---> ForceReinstall flag is set to true    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
---> Created service "ccmsetup" on machine "SWECO715WIN10.sweco.corp".    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
---> Started service "ccmsetup" on machine "SWECO715WIN10.sweco.corp".    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
---> Deleting SMS Client Install Lock File '\\SWECO715WIN10.sweco.corp\admin$\SMSClientInstall.SWE'    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
Execute query exec [sp_CP_SetLastErrorCode] 2097152272, 0    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
---> Completed request "2097152272", machine name "SWECO715WIN10".    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
Deleted request "2097152272", machine name "SWECO715WIN10"    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152272, 4    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
Execute query exec [sp_CP_SetLatest] 2097152272, N'10/05/2017 12:39:02', 18    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
<======End request: "2097152272", machine name: "SWECO715WIN10".    SMS_CLIENT_CONFIG_MANAGER    10/5/2017 7:39:02 AM    12096 (0x2F40)
 

[gavin1973]

I went through the same scenario in my environment when we upgraded SCCM and in doing so we changed the site code.  In order to manage those machines we used a script to change the hardcoded site code to auto which then allows the machine reassign to the new site server.

 A snippet of the important part of the script:

''''Set Site Discovery to Auto
                    Set objWMIService2 = GetObject("winmgmts://" & strComputer & "/root/ccm") 
                    Set objSMSClient = objWMIService2.ExecQuery ("Select * from SMS_Client") 
                    For Each objClient in objSMSClient 
                        objClient.EnableAutoAssignment = 1 
                        objClient.Put_ 0 
                    Next
The key to was the 'EnableAutoAssignment'

On a side note in the configuration manager client are you able to manually connect to your new site code? It may also be worth you checking the location log on the client machine to make sure there are no errors springing up in there.