SEP client version newer than SEPM version
Updated: 06 Feb 2012 | 11 comments
Hi,
I would like to know if there will be any problems by using the version 11.0.6300.803 on the SEPM and a newer/the newest version 11.0.7000.975 on the client side. The background for this configuration is that I will stay at 11 RU6 MP3 because of the direct upgrade path to version 12.1. The newest client version was shown up some times ago on the console and therewith I will push that version to all my clients.
Regards
Stefan
Discussion Filed Under:
Comments
Nothing to worry about
You can do a direct upgrade to SEP12.1RU1 even if you were to upgrade your SEPM to RU7
Hi, thanks for your answer
Hi,
thanks for your answer but is it also possible to manage newer 11.x client versions that are newer than the SEPM? Can this cause any errors or problems?
SEPM with version 12.1 can
SEPM with version 12.1 can manage 11.x clients. First you can upgrade your server to 12.1 and slowly you can upgrade your clients to 12.1
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
Errrr, I'd be careful here...
In theory, I suspect the answer is a cautious "Yes" but this is unlikely to be supported by Symantec if you encountered any problems.
though it is not recommended,
though it is not recommended, the SEPM lower version can handle higher SEP client version.
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
Hello Sbay , I agree with
Hello Sbay ,
I agree with Pete and SmlatCST , be caustious . Sep 11 are legacy for 12.1 hence migrating sepm ie server to 12.1 first would be good idea .
However make sure to back up all the db / policies/server private key folders before doing this change .
Swapnil
SOC Team .
Please don't forget to mark your thread solved with whatever answer helped you.
2c
I have a few 12.1 clients managed by an 11.0.6300 (RU6 MP3) server.
Although there are barely any policies in place. The conflict would most likely appear if you have PTP and NTP policies in place. The othe components may not be directly managed by 11.x.xxxx. like Inslight and SONAR.
I'd recommend that you wait until the server is at version 12 before migrating the rest of the clients.
“Your most unhappy customers are your greatest source of learning.”
Hi,Upgrade Manager and SEP
Hi,
Upgrade Manager and SEP clients to the same version.
Latest release is SEP 12.1 RU1.
You can upgrade directly to SEP 12.1 RU1 irrespective of SEPM/SEP client version.
Thanks and Regards,
Chetan Savade
Technical Support Analyst,
End Point Security, Enterprise Technical Support
I agree
Hello,
I agree with SMLatCST above statements.
Until and unless you have same Base versions, you have nothing to worry about.
In your case, SEPM and SEP clients are of version 11. However, it is always recommended for you to make sure that your SEPM and SEP clients are on the Latest Version. It is important to maintain consitency in the SEP 11 - check article below:
About Maintaining Consistency of Software Versions throughout a SEP 11 Organization
http://www.symantec.com/docs/TECH131660
Migrating to Symantec Endpoint Protection 11.0.7101 (RU7 MP1)
http://www.symantec.com/docs/TECH171552
Hope that helps!!
Mithun Sanghavi
Symantec Technical Support Engineer, SEP
MIM | MCSA | SCTS | ITIL v3
Follow me on Twitter: @mithun_sanghavi
Don't forget to mark your thread as 'SOLVED' with the answer that best helped yo
Although not recommended, we
Although not recommended, we had RU7 clients on an RU6 MP3 SEPM without issue, and are currently on a RU7 SEPM with several thousand RU7 MP1 clients in the environment. They are managed and report into the server without issue, and our environment has a fairly complex structure making extensive use of location awareness. However I would be unwilling to add 12.1 clients to our environment until the SEPMs have been upgraded as it is significantly different from the 11.x client.
If you have the version of
If you have the version of SEPM 11.07, then go to upgrade directly SEPM 12.1 RU1.
Would you like to reply?
Login or Register to post your comment.