Hi there,

We're building a new SCCM server and are having some issues now that we've updated it to R2 SP1 CU1 (ver 5.00.8239.1203). New clients being pushed out (or a remove/reinstall) are installing client version 5.00.8239.1000, which only give 2 of about 11 options in the "Actions" tab and isn't working in general. We had auto-updating on for a while which then updated them to version 1203 but took forever (overnight in most cases). I know that already-installed clients will need updating separately, but shouldn't the client on the server have been updated when CU1 was installed so that any new clients pushed out are already updated? I see I see four update packages as a result of the CU1 upgrade (console, server, x64 client and x86 client). Do we need to deploy one of those to the server? The tech who installed CU1 says he chose "Automatically Apply" when doing the upgrade, which I think should have done the trick.

I'm sure there's something that we missed or don't understand here.

I see from this post:
https://social.technet.microsoft.com/Forums/en-US/0a846098-7c92-4f4d-9d74-800e747f2030/sccm-2012-sp1-cu1-versions-of-files-not-incrementing-after-the-update?forum=configmanagerdeployment

that I may need to add a patch property to the installation properties in my console to fix this. Is this really what needs to be done every time we update so client push works quickly and properly? There's gotta be a way that the client pushed by the server is updated when we update the server, console, etc.

The most recent client should be installed / pushed with R2SP1CU1: http://blogs.technet.com/b/configmgrteam/archive/2015/08/04/automatically-updating-the-configuration-manager-client.aspx

Well, I've managed to get the 1203 client out consistently now, but we're still having issues where there are only two Actions on the tab and the Client Certificate line on the General tab says "none". It's happening to most systems (probably 80%) but not all for some reason.

For each client that fails to install properly, the ccmsetup.log file has:

"Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent."

And in the server-side log (ccm.log) we're seeing alot of:

"Execute query exec [sp_CP_SetLastErrorCode] <request#>, 0"

One off error message offer no help and in this case the first is not fatal -- not all error messages are -- and the second isn't even an error. Simply searching for red in the log files via cmtrace is a start, but is in no way definitive or authoritative.

Also, ccmsetup show setup activity; if you have the control panel applet, then setup is done and you need to move onto operational logs like clientlocation.log, locationservices.log, and clientidstartupmanager.log.

Sorry it took so long to reply. This issue got bumped up to our Network Services team and they seem to have fixed the issue. I'm currently trying to get the tech involved to post on here with what he found / did to fix it.