mr3 client reporting to MR5 sepm
Created: 13 Oct 2010 | 4 comments
Hi Everyone,
Any problems reporting of an MR3 client reporting to a MR5 SEPM. I need to move a number of clients across to a new SEPM that is on RU5.
Thanks for your help.
Discussion Filed Under:
Comments
Hi
No problem, it can manage it for few months, good to migrate at the earliest.
check this link
https://www-secure.symantec.com/connect/forums/can-sepm-mr4-mp2-server-manage-sep-ru5-client
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Once they are communicating
Once they are communicating to the proper server, in this case the MR5 server, just need to assign the package to the group and the "auto-update" will upgrade your clients to the proper client package/build.
Have you already moved your clients over? Chaged the SYLINK.XML file using the SYLINKDROP tool?
SEPM and SEP clients are
SEPM and SEP clients are reverse Compatible. MR3 can report to SEPM MR5 however there will be some minor errors that you might find in the logs but nothing major.
However I would suggest to upgrade your Setup to atleast RU6a as there are many issues in MR3.
VMWARE-- SEP 12.1 vs McAfee vs Trend Micro
Official Article
Hi Por,
The SEPM and SEP clients should be able to communicate without any trouble. Here is the official article on the subject:
Does Symantec Endpoint Protection Manager function with different versions of SEP client? (http://www.symantec.com/docs/TECH131718)
My personal recommendation would be to upgrade both SEPM and SEP clients, though. MR3, in particular, is quite old. Migrating to RU6 MP1 will ensure that you are taking advantage of literally thousands of available fixes, enhancements and improvements.
Thanks and best regards,
Mick
With thanks and best regards,
Mick
Would you like to reply?
Login or Register to post your comment.