Home

SCCM showing outdated version of endpoint protection clients

%3CLINGO-SUB%20id%3D%22lingo-sub-733598%22%20slang%3D%22en-US%22%3ESCCM%20showing%20outdated%20version%20of%20endpoint%20protection%20clients%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-733598%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20SCCM%20version%201610%20and%20was%20having%20an%20issue%20with%20some%20of%20the%20clients.%20SCCM%20showing%20the%20outdated%20SCEP%20version%20and%20engine%20version%20whereas%20the%20client%20itself%20is%20updated%20as%20per%20the%20attached%20screenshot.%20The%20issue%20is%20resolved%20and%20reported%20back%20correctly%20after%20reinstalled%20of%20SCEP%20clients.%20But%20it%20is%20somehow%20it%20is%20showing%20outdated%20again%20after%20a%20few%20months.%20Any%20idea%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-733598%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EEndpoint%20Protection%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-734636%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%20showing%20outdated%20version%20of%20endpoint%20protection%20clients%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-734636%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F369698%22%20target%3D%22_blank%22%3E%40zarchi%3C%2FA%3E%26nbsp%3BThe%20first%20step%20here%20is%20upgrading%20to%20a%20supported%20version%20of%20ConfigMgr%20as%201610%20hasn't%20been%20supported%20in%20almost%202%20years%20now.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENext%2C%20how%20are%20you%20deploying%20the%20SCEP%20updates%3F%20Using%20an%20ADR%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-738927%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%20showing%20outdated%20version%20of%20endpoint%20protection%20clients%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-738927%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F117994%22%20target%3D%22_blank%22%3E%40Jason%20Sandys%3C%2FA%3E%26nbsp%3B%20Thanks%20for%20the%20replying.%20We%20will%20not%20upgrade%20the%20version%20at%20the%20moment.%20We%20are%20deploying%20the%20updates%20via%20task%20scheduler%20every%2030%20mins.%20It%20is%20just%20weird%20that%20it%20happened%20to%20some%20of%20the%20machines%20out%20of%20hundreds%20of%20machines.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-740368%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%20showing%20outdated%20version%20of%20endpoint%20protection%20clients%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-740368%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F369698%22%20target%3D%22_blank%22%3E%40zarchi%3C%2FA%3E%26nbsp%3BThen%20nothing%20you%20do%20is%20supported%20or%20should%20even%20have%20any%20expectation%20of%20success%20necessarily.%20It%20is%20very%20important%20to%20keep%20up%20with%20ConfigMgr%20releases%20--%20choosing%20not%20to%20is%20simply%20asking%20for%20fixed%20bugs%20to%20affect%20you%20or%20for%20additional%20non-supported%20scenarios%20to%20affect%20the%20management%20of%20your%20estate.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26nbsp%3BWe%20are%20deploying%20the%20updates%20via%20task%20scheduler%20every%2030%20mins.%3C%2FP%3E%0A%3CP%3EI%20don't%20understand%20what%20this%20means%20in%20the%20context%20of%20ConfigMgr%2C%20why%20you%20would%20use%20the%20task%20scheduler%2C%26nbsp%3B%20why%20you%20would%20do%20this%20every%2030%20minutes%2C%20or%2C%20(i%20guess%20to%20reiterate)%20how%20ConfigMgr%20has%20anything%20to%20do%20with%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-742265%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%20showing%20outdated%20version%20of%20endpoint%20protection%20clients%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-742265%22%20slang%3D%22en-US%22%3EThanks%20for%20your%20reply%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E
zarchi
New Contributor

We have SCCM version 1610 and was having an issue with some of the clients. SCCM showing the outdated SCEP version and engine version whereas the client itself is updated as per the attached screenshot. The issue is resolved and reported back correctly after reinstalled of SCEP clients. But it is somehow it is showing outdated again after a few months. Any idea?

4 Replies
Highlighted

@zarchi The first step here is upgrading to a supported version of ConfigMgr as 1610 hasn't been supported in almost 2 years now.

 

Next, how are you deploying the SCEP updates? Using an ADR?

@Jason Sandys  Thanks for the replying. We will not upgrade the version at the moment. We are deploying the updates via task scheduler every 30 mins. It is just weird that it happened to some of the machines out of hundreds of machines.

@zarchi Then nothing you do is supported or should even have any expectation of success necessarily. It is very important to keep up with ConfigMgr releases -- choosing not to is simply asking for fixed bugs to affect you or for additional non-supported scenarios to affect the management of your estate.

 

> We are deploying the updates via task scheduler every 30 mins.

I don't understand what this means in the context of ConfigMgr, why you would use the task scheduler,  why you would do this every 30 minutes, or, (i guess to reiterate) how ConfigMgr has anything to do with this.

Thanks for your reply :)
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
22 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
cntvertex in Discussions on
13 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies