Per the log above, the client is not reachable on the network so nothing has changed here. To perform a valid test, as noted, the client must be reachable on the network.
Client Push installation uses only one account in 2103?
Have a SCCM 2103 installation that we use for managing clients from different domains. Have now discovered that a lot of systems have no SCCM client. Troubleshooting reveals that SCCM 2103 uses only the first account that is specified in the client installation properties. I remember from previos SCCM versions, that SCCM was trying all acounts that are configured in the push installation properties.
Has anyone an advice? Thank you in advance.
Franz
-
Jason Sandys 31,186 Reputation points Microsoft Employee
2021-09-08T13:51:57.653+00:00
2 additional answers
Sort by: Most helpful
-
Jason Sandys 31,186 Reputation points Microsoft Employee
2021-09-07T16:08:48.217+00:00 Two quick observations here based on your log:
- The log shows two different devices.
- Both devices fail because they are not reachable on the network so trying with an alternate account has zero value here.
To properly validate this, you need to push to a single device (so that multiple devices aren't intermingled in the logs since auto client push is threaded and is active on up to 10 different clients simultaneously) and the device needs to be reachable on the network.
-
Franz Schenk 336 Reputation points
2021-09-08T07:30:59.86+00:00 Hello Jason
Thank you for your feedback.
- Have changed the order of the client access accounts, and have seen in ccm.log that SCCM has processed this change.
- Have verified that a system with missing SCCM client is online, and tried the push installation.
The problem is the same: Even if there is a line in the logfile where SCCM says it will try each account, SCCM tries only the client installation account that is on top of the list, then gives up.