Ccmsetup is *not* the client agent installer so that's not indicative of anything. Ccmsetup is simply a bootstrapper that initiates the download and installation of pre-reqs and the client itself (which is done by client.msi).
See Todd's answer for updating the clients to CU3 (from SP1). J From: [email protected] [mailto:[email protected]] On Behalf Of Todd Hemsell Sent: Monday, September 23, 2013 4:28 PM To: [email protected] Subject: Re: [mssms] SP1 CU3 / Client Upgrades when I push the ccmsetup.exe is version.4000 but it still installs client version .1000 You can import the CU as an update into SCUP or deploy as a package On Mon, Sep 23, 2013 at 5:52 AM, Stuart Watret <[email protected]<mailto:[email protected]>> wrote: I was late getting to SP1, did it this Friday and noticed here that CU3 was out also; so applied that Saturday. So the notes on the CU update process clearly state that when clients get re-installed the CU update wll need to be re-applied. Which is fine I suppose; but prior to running CU3 I checked the version of ccmsetup.exe in the "Client" folder on the server. Post CU3 this version had been incremented which led me to hope that client upgrades push or auto would get CU3 straight away. Been using the auto update method since Saturday and the clients are only getting the SP1 update, I'm having to push separately CU3. Is this normal? Stuart Watret Offshore - IT Ltd
