11.0.5 client / 11.0.4 SEPM issue
I'm doing some testing and I upgraded a client to 11.0.5. SEPM is still on 11.0.4.
I was under the impression this client could still be managed even though it's on a newer version
Anyways, I installed 11.0.5 unmanaged and made it managed after the install was complete.
Now I see the client in SEPM however it is still showing old info, (mainly the defs)
My client is showing the green dot and the latest defs (Monday, November 16, 2009 r2 for AV, Nov 16th, 2009 17 for PTP, and Thurs, Nov 12, 2009 r1 for NTP) however this is not reflected in SEPM as it is showing the defs from 2 days ago.
Just curious to know if the server is actually managing this client or just appears to be and if being on a 11.0.5 client but SEPM still being on 11.0.4 is an issue
SEPM cannot be upgraded at this time so if I have to go back to 11.0.4 on the client, I have no problem with that.
Any help would be appreciated
Comments
Best practices is to keep everyone at the same version
While I'm not aware of any issues per se of having an "old" SEPM and a newer client, we have seen issues in the past with mismatches like this in SEP. They ended up being mostly annoyances...the clients were still updating and were still protected, but they failed, say, upload logs correctly (or, to be more precise, the SEPM couldn't understand the "old" logs, as values had moved around in the database schema update).
If it's not a big deal, I'd recommend going back to MR 4 until you can update the SEPM to RU 5.
Works for me. It does appear
Works for me. It does appear to be getting updates from SEPM but I need to be able to manage it without issue.
Thanks for the info
Endpoint Knowledge Base
Security Best Practices
Always make the version of
Always make the version of the SEPM's equal to or greater than the clients they are managing.
That has been the rule since NAV/SAV first appeared...if you don't you are basically on your ownas far as support is concerned
Z
Would you like to reply?
Login or Register to post your comment.