Windows Servers not reporting to SCCM console with client installed. (Network Steve Forum)

Windows Servers not reporting to SCCM console with client installed.

I don't see that error and the task scheduler is set to auto on all the servers.

They all have the same result:

File C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation succeeded. ccmsetup 8/17/2015 4:19:08 PM 4276 (0x10B4)
Successfully deleted the ccmsetup service ccmsetup 8/17/2015 4:19:13 PM 4276 (0x10B4)
A Fallback Status Point has not been specified. Message with STATEID='400' will not be sent. ccmsetup 8/17/2015 4:19:13 PM 4276 (0x10B4)
Deleted file C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 8/17/2015 4:19:13 PM 3944 (0x0F68)
Task 'Configuration Manager Client Upgrade Task' does not exist ccmsetup 8/17/2015 4:19:13 PM 3944 (0x0F68)
CcmSetup is exiting with return code 0 ccmsetup 8/17/2015 4:19:13 PM 3944 (0x0F68)

The strange thing is I run the install from the console to the machine it starts immediately with the installation. if you go into the properties it show some data:

I go to the machine and it points to the correct site.

Edited by Eiram Rulz Tuesday, August 18, 2015 5:33 PM

August 18th, 2015 5:32pm

Ok so looking in that log: (just a few lines but common errror - Server rejected registration request: 3

[RegTask] - Server rejected registration request: 3 ClientIDManagerStartup 8/18/2015 2:21:20 PM 5940 (0x1734)
Sleeping for 33 seconds before refreshing location services. ClientIDManagerStartup 8/18/2015 2:25:46 PM 5940 (0x1734)
GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE ClientIDManagerStartup 8/18/2015 2:26:20 PM 5940 (0x1734)
Computed HardwareID=2:A751D6E114B4AA096507B4D1FA2A1B80D6EC6610
Win32_SystemEnclosure.SerialNumber=<empty>
Win32_SystemEnclosure.SMBIOSAssetTag=<empty>
Win32_BaseBoard.SerialNumber=None
Win32_BIOS.SerialNumber=VMware-42 0f 70 e8 af 3d 27 fa-be 44 16 d0 a8 10 22 cb
Win32_NetworkAdapterConfiguration.MACAddress=00:50:56:8F:14:CC ClientIDManagerStartup 8/18/2015 2:26:20 PM 5940 (0x1734)
[RegTask] - Client is not registered. Sending registration request for GUID:6F4AE14E-5B79-471A-BD95-FD70B7616061 ... ClientIDManagerStartup 8/18/2015 2:26:20 PM 5940 (0x1734)
[RegTask] - Server rejected registration request: 3 ClientIDManagerStartup 8/18/2015 2:26:20 PM 5940 (0x1734)

What is even more strange I go on the server we have SCEP deployed as well and it settings are stating it is getting policy from the server!?!?!

Edited by Eiram Rulz Tuesday, August 18, 2015 6:34 PM

Free Windows Admin Tool Kit Click here and download it now

August 18th, 2015 6:28pm

I have just a handful of servers that are not reporting to the console.

SCCM is installed and is pointing to the management site. I uninstalled numerous times and still they will not response to the respond to the console. I've checked logs and FW settings but nothing. Any ideals why they are not reporting acitivity? Even thought the installations is pointing to the correct location?

August 19th, 2015 10:31am

Have you checked the ccmsetup.logs on the servers to ensure the client has actually installed on them?

Free Windows Admin Tool Kit Click here and download it now

August 19th, 2015 10:44am

verify you have the service "task scheduler" enabled or automatic on your servers. The SCCM client used task scheduler during install and ensures functionality of the client to site communication. We had a issue in a test environment where machines could be discovered but the client would never fully install therefore not talk back to the server to report installed and active.

In the ccmsetup.log if you are getting generic 1603 errors this would be something to look into.

August 19th, 2015 10:50am

I don't see that error and the task scheduler is set to auto on all the servers.

They all have the same result:

The strange thing is I run the install from the console to the machine it starts immediately with the installation. if you go into the properties it show some data:

I go to the machine and it points to the correct site.

Edited by Eiram Rulz 14 hours 17 minutes ago

Free Windows Admin Tool Kit Click here and download it now

August 19th, 2015 1:20pm

Is Heartbeat discovery enabled on your site ?

On the client also check the ClientIDManagerStartup.log

The data you are seeing when you double click your client is discovery data from SMS_AD_SYSTEM_DISCOVERY, nothing to do with the agent installation.

August 19th, 2015 1:46pm

Ok so looking in that log: (just a few lines but common errror - Server rejected registration request: 3

What is even more strange I go on the server we have SCEP deployed as well and it settings are stating it is getting policy from the server!?!?!

Edited by Eiram Rulz 13 hours 17 minutes ago

Free Windows Admin Tool Kit Click here and download it now

August 19th, 2015 2:16pm

Oh and yes heartbeat discovery is set 1 week

August 19th, 2015 2:41pm

Are the servers domain members or workgroup machines?

Free Windows Admin Tool Kit Click here and download it now

August 19th, 2015 2:43pm

Domain memebers

August 19th, 2015 2:50pm

Ok I think I found part of the issue. I removed all components deleted the folder and started install and watched the logs when running the installer from the server itself....and it still looking for the old sccm site first it finds the new site server, it installs reporting to the new SCCM but it is still not showing up in the console.

Is there some where it stores old config data from the previous site server?

Free Windows Admin Tool Kit Click here and download it now

August 19th, 2015 3:14pm

Any clues?

August 19th, 2015 4:27pm

So you had another SCCM server before this one ? 2012 ?

Has it been uninstalled ? How ?

What are your client installation properties ?

Free Windows Admin Tool Kit Click here and download it now

August 20th, 2015 9:45am

This topic is archived. No further replies will be accepted.