Hi all,

I have a small problem with one sccm site. I've configured the site for enable automatic site-wide client push installation.

Manually works fine. So from the site configuration I've ebenbale this function, it's enable for workstation, I have proper accounts setup.

I've made a test and with a new windows 7, the system was discovered in 10  minutes , I can see hem in sccm without client. in ccm.log nothing about this computer. What I've missed ?

The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Default MP: xxx.domain SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Certificate Store: SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Checking configuration information for server:  xxx.domain . SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Checking configuration information for server:  xxx.domain . SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Fallback Status Point:  xxx.domain SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Install on DC: False SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Option for installing using IP address: 0 SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 20/04/2015 11:50:33 4712 (0x1268)
Execute query exec [sp_CP_CheckNewAssignedMachine] N'PW1',0

SMS_CLIENT_CONFIG_MANAGER 20/04/2015 12:00:13 4856 (0x12F8)
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 20/04/2015 12:00:14 4856 (0x12F8)

Hi,

Do the clients fall in a boundary and boundary group? In the console does it show the site for these clients?

https://technet.microsoft.com/en-gb/library/gg712298.aspx?f=255&MSPPError=-2147217396

You could fire off a client installation on a collection using the client push installation wizard.

• Edited by Richard.Knight 20 hours 21 minutes ago

Hi Richard,

All the clients are in a network covered by an boundary group by network address and also are in AD site covered by same boundary group.

I made all settings like in TechNet docs. Manually I can push the client using wizard on any computers.

The infrastructure it's very simple. Only one primary site, only one MP + all usual roles and a second DP in another network. Every process works normally, site status and component status are all green.

You mentioned boundary groups. . .is one set up for site assignment? Without a site assignment boundary group client push will not work.  You can override that by specifying a site when you do it manually - are you specifying a site when you do the manual push of the client?

Jeff

adsysdis.log

domainp,DC=local' SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:45:03 1840 (0x0730)
INFO: Property (operatingSystem) for (w7-sccmtest1) was not set SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:45:03 1840 (0x0730)
INFO: Property (operatingSystemVersion) for (w7-sccmtest1) was not set SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:45:03 1840 (0x0730)
INFO: Property (dNSHostName) for (w7-sccmtest1) was not set SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:45:03 1840 (0x0730)
ERROR: System w7-sccmtest1 is a unsupported operating system, unsupported version, or malformed AD entry. Reported system type is:  (). SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:45:03 1840 (0x0730)
WARN:  Failed to get following optional attributes, operatingSystemServicePack,operatingSystemVersion, SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:45:03 1840 (0x0730)
INFO: successfully completed directory search SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:45:03 1840 (0x0730)

domainp,DC=local' SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:50:02 2520 (0x09D8)
INFO: Property (operatingSystem) for (w7-sccmtest1) was not set SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:50:02 2520 (0x09D8)
WARN:  Failed to get following optional attributes, operatingSystemServicePack, SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:50:02 2520 (0x09D8)
INFO: DDR was written for system 'W7-SCCMTEST1' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adsawr5y.DDR at 4/20/2015 10:50:1. SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:50:02 2520 (0x09D8)
INFO: successfully completed directory search SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:50:02 2520 (0x09D8)
INFO: Start to recursively process into group objects SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:50:02 2520 (0x09D8)

domainp,DC=local' SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:55:02 2856 (0x0B28)
INFO: Property (operatingSystem) for (w7-sccmtest1) was not set SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:55:02 2856 (0x0B28)
WARN:  Failed to get following optional attributes, operatingSystemServicePack, SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:55:02 2856 (0x0B28)
INFO: DDR was written for system 'W7-SCCMTEST1' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\ads16vi8.DDR at 4/20/2015 10:55:1. SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 10:55:02 2856 (0x0B28)

I know that w7 without sp 1 it's fine. From logs fails to query sp. In mean time I start to apply sp1 on this w7 to see if are any issues with missing sp1.

https://technet.microsoft.com/en-us/library/gg682077.aspx?f=255&MSPPError=-2147217396#BKMK_SupConfigClientOS

after service pack applied I have only this entry

INFO: discovered object with ADsPath = 'LDAP://domain/CN=w7-sccmtest1,OU=SCCM Test OU2,OU=WorkStations,DC=domain,DC=local' SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 15:10:03 936 (0x03A8)
INFO: Property (operatingSystem) for (w7-sccmtest1) was not set SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 15:10:03 936 (0x03A8)
INFO: DDR was written for system 'W7-SCCMTEST1' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adszb1b3.DDR at 4/20/2015 15:10:2. SMS_AD_SYSTEM_DISCOVERY_AGENT 20/04/2015 15:10:03 936 (0x03A8)

push wizard :

======>Begin Processing request: "2097153353", machine name: "W7-SCCMTEST1" SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:54 2924 (0x0B6C)
Execute query exec [sp_IsMPAvailable] N'PW1' SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:54 2924 (0x0B6C)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:54 2924 (0x0B6C)
---> Attempting to connect to administrative share '\\W7-SCCMTEST1\admin$' using account 'domain\account1' SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:54 2924 (0x0B6C)
---> Connected to administrative share on machine W7-SCCMTEST1 using account 'domain\account1'   SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:54 2924 (0x0B6C)
---> Attempting to make IPC connection to share <\\W7-SCCMTEST1\IPC$> SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:54 2924 (0x0B6C)
---> Searching for SMSClientInstall.* under '\\W7-SCCMTEST1\admin$\' SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:54 2924 (0x0B6C)
---> System OS version string "6.1.7601" converted to 6.10 SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)
---> Unable to connect to WMI (root\ccm) on remote machine "W7-SCCMTEST1", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)
---> Creating \ VerifyingCopying exsistance of destination directory \\W7-SCCMTEST1\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)
---> Copying client files to \\W7-SCCMTEST1\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)
---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)
---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)
---> Created service "ccmsetup" on machine "W7-SCCMTEST1". SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)
---> Started service "ccmsetup" on machine "W7-SCCMTEST1". SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)
---> Deleting SMS Client Install Lock File '\\W7-SCCMTEST1\admin$\SMSClientInstall.PW1' SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)

Hi,

Do the clients fall in a boundary and boundary group? In the console does it show the site for these clients?

https://technet.microsoft.com/en-gb/library/gg712298.aspx?f=255&MSPPError=-2147217396

You could fire off a client installation on a collection using the client push installation wizard.

• Edited by Richard.Knight Monday, April 20, 2015 11:27 AM

---> Started service "ccmsetup" on machine "W7-SCCMTEST1". SMS_CLIENT_CONFIG_MANAGER 20/04/2015 16:03:55 2924 (0x0B6C)

No errors in there. Next: examine ccmsetup.log on the client.

@Torsten Meringer

Sorry my fault, manual push wizard was successfully. I believe that was obviously ;)

Have you checked site assignment in your boundary group like I mentioned previously? Manual push can override site assignment and work as a result.  Automatic client push needs site assignment configured by a boundary group.

Jeff

Yes I have.

• Edited by Cristian.Ceobanu 17 hours 27 minutes ago

What happens if you delete a single client that doesn't have the ConfigMgr client installed then run discovery. Does it automatically send out the client to the newly discovered client device?

• Edited by Richard.Knight 16 hours 44 minutes ago

Yes,

discover log:

INFO: discovered object with ADsPath = 'LDAP://domain.LOCAL/CN=PWWKS-W7SCCM,OU=SCCM Test OU2,OU=WorkStations,DC=domain,DC=local' SMS_AD_SYSTEM_DISCOVERY_AGENT 21/04/2015 16:12:49 6312 (0x18A8)
INFO: Property (operatingSystem) for (PWWKS-W7SCCM) was not set SMS_AD_SYSTEM_DISCOVERY_AGENT 21/04/2015 16:12:49 6312 (0x18A8)
INFO: DDR was written for system 'PWWKS-W7SCCM' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adsfl2o3.DDR at 4/21/2015 16:12:30. SMS_AD_SYSTEM_DISCOVERY_AGENT 21/04/2015 16:12:49 6312 (0x18A8)

ccm.log

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 21/04/2015 16:09:37 2256 (0x08D0)
Waking up for site control file directory change notification SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
The Site Control File has changed, parameters will be reread. SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Default MP: server.domain.local SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Certificate Store: SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Checking configuration information for server: server.domain.LOCAL. SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Checking configuration information for server: server.domain.LOCAL. SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Fallback Status Point: CORPRKSCCM01.corp.local SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Install on DC: False SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Option for installing using IP address: 0 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Retrieving properties from the site control file. SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Advanced Client Command Line: SMSSITECODE=PW1 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
  Ignoring unrecognized property "Advanced Client Command Line Default" SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Security Mode Option - CCR buffering enabled. SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Default Client Type: -1 SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)
Sleeping for 656 seconds... SMS_CLIENT_CONFIG_MANAGER 21/04/2015 16:12:27 6056 (0x17A8)

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

So the computer was discovered, it's visible in sccm, but nothing in ccm.log. In what log can I check what sccm decided to do with the new client discover, decision, errors, etc.

• Edited by Cristian.Ceobanu 16 hours 8 minutes ago