Tefty Posted April 18, 2016 Report post Posted April 18, 2016 I was doing some SCEP work this morning and noticed a few of my machines were running the 4.9.219.0 Antimalware Client Version while others were running 4.7.214.0. Having then dug through my ADR definition deployment rules I can see that the packages being created and deployed have the newer version so was a little confused as to why some had not updated which I have still yet to get to the bottom of. In the meantime I noticed that the client directory in the SMS_Site directory has an updated with the latest CCMSetup.exe from my 1602 upgrade which is great but the SCEPinstall.exe is showing the old 4.7.214.0 version. I know the 2 are differently managed however the site server itself is running the 4.9.219.0 and as far as I was aware when the site server updates it was supposed to update the SCEPInstall.exe in the client directory so the latest SCEPInstall gets installed by default with the SCCM client. I've dug through the updates and found the latest SCEPInstall.exe package so will replace manually but has anyone else seen this or have any advice on how to proceed with this? Thanks, Andy Quote Share this post Link to post Share on other sites More sharing options...
ex3me Posted April 20, 2016 Report post Posted April 20, 2016 It is very interesting, because I, too, watch it and do not know why there was a downgrade product version scep to 4.7.214.0 in sccm1602, although according to https://support.microsoft.com/en-us/kb/3153224should be anti-malware client version to 4.9.0219.0. Also on a clean server installation sccm 1602 we have source distribution version anti-malware client 4.7.214.0. Quote Share this post Link to post Share on other sites More sharing options...
Tefty Posted April 21, 2016 Report post Posted April 21, 2016 It is very interesting, because I, too, watch it and do not know why there was a downgrade product version scep to 4.7.214.0 in sccm1602, although according to https://support.microsoft.com/en-us/kb/3153224should be anti-malware client version to 4.9.0219.0. Also on a clean server installation sccm 1602 we have source distribution version anti-malware client 4.7.214.0. So its not just me that has this issue then, thought I was going completely mad for a minute... So this could be an inherit issue with SCCM 1602 ? Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted April 24, 2016 Report post Posted April 24, 2016 If you replace manually then it will NOT work, as you will get hash mismatch (hashes are stored in inf, inside signed .cab) Been there, tried that, does not work Seb Quote Share this post Link to post Share on other sites More sharing options...
Tefty Posted April 25, 2016 Report post Posted April 25, 2016 Aye worked that one out as well 10 minutes after posting... Between this and the new "Error 1406. Could not write value LastMsgSerialNum to key \SOFTWARE\Microsoft\CCM\StateSystem. System error . Verify that you have sufficient access to that key, or contact your support personnel." my current new builds are doing fantastically well ! Quote Share this post Link to post Share on other sites More sharing options...
dmaggioni Posted July 6, 2016 Report post Posted July 6, 2016 Same situation for me. How can I upgrade scep from 4.7.214.0 to 4.9.0219.0 in sccm 1602? When I deploy the client it installs older version and did not upgrade to 4.9.0219.0. Thank you for your reply! Davide Quote Share this post Link to post Share on other sites More sharing options...
