SEPM is backwards compatible with all older versions...

No there will not be any problem....

Only thing you will miss is new features which are available in RU5 clients...

Few features which are not present in older version will not work on clients even if you configure it on server...

Check the release notes.. ftp://ftp.symantec.com/public/english_us_canada/pr...

There should not be aany concerns or issue.

Supported platforms
Symantec Endpoint Protection 11.0.5002.333 (RU5) can migrate seamlessly over the following:

• Symantec Endpoint Protection 11.0.780.1109 (RTM), 11.0.1000.1375 (MR1), 11.0.1006 (MR1 MP1), 11.0.2000.1567 (MR2), 11.0.2010.25 (MR2 MP1), 11.0.2020.56 (MR2 MP2), 11.0.3001.2224 (MR3), 11.0.4000.2295 (MR4), 11.0.4010.19 (MR4 MP1), 11.0.4014.26 (MR4 MP1a) and 11.0.4202.75 (MR4 MP2).

http://service1.symantec.com/SUPPORT/ent-security....

 There wont be any problems except Multiple GUPs policy wont work.

There is no issue in SEPM is managing SEP MR4MP2 cleints.

As Vikram has already said , there may be issue while configuring  multiple gups as in RU5   a new table called GUP_LIST has been added to the database schema to hold information of the GUPs.

As i have already mentioned there wont be any issue... 

for example... 

Think that you have replaced army troop commander with highly trained person but all the solders are old and not trained... Troop is still useful and can go for BATTLE but it can never WIN unless you replace your soldiers with trained ones....
In the same way Newer version of SEPM and older version of Client wont give any trouble but u cant get the full FUNCTIONALITY and RESULT of newer version.

As has been pointed out, there shouldn't really be errors, but in the past we've seen issues.  Nothing critical (clients still updated definitions and were protected), just nagging errors that spammed up the logs until resolved.

Here's an example of something we've seen in the past:

Title: 'Symantec Endpoint Protection Manager (SEPM) is logging the error: "Invalid log record: Too few fields." in the Admin > Servers > Status Panel'
Document ID: 2008092311461848
> Web URL: http://service1.symantec.com/SUPPORT/ent-security....

There's also been reports of seeing this where an RU 5 client is reporting up to an MR4 MP2 SEPM...but that was only one parting comment from another technician.

You really should update your SEPM first, then roll out to your clients very soon after.  While we should work, we've seen in the past that it isn't always elegant, and may not fully function in future releases (like, say, RU 6 reporting to RU 5 or something).

What are the extra benifits I will get if I upgrade my clients too.

Can I get better scan speed as mr4mp2 scans for hours.

Client side features:

The size of the exported client installation package has been reduced

The GroupUpdateProvider includes new functionality

You can configure the following features for the Group Update Provider:

■ Limit the amount of bandwidth that the Group Update Provider can use when the Group Update Provider downloads content from the
management server.

■ You can define a Group Update Provider by using rules and conditions, such as an IP address or host name. You can configure a single Group Update Provider in a single LiveUpdate Policy that applies across multiple groups for multiple clients.

■ Define clients to connect to a Group Update Provider within the same site to improve performance.

■ Identify which clients act as Group Update Providers.
REF:https://www-secure.symantec.com/connect/articles/types-group-update-providers-ru5-release-symantec-endpoint-protection-110

The client now includes a Download Support Tool command on the Help and Support menu

ftp://ftp.symantec.com/public/english_us_canada/pr...
 

I m new to symantec... These kind of disscussion are helping me a lot.....

Hi Bijai,

I dont have anything new to say, It should handle it perfectly fine :)

if you check the release notes , they have not changed anything which relates to SEPM communication with clinets and client is not uploading any additional logs to the DB
the schema are the same.
it should work fine.

https://www-secure.symantec.com/connect/forums/can-sepm-mr4-mp2-server-manage-sep-ru5-client#comment-3126101

I would just like to add this that there has been modfication to the database schema in RU5 a  new table called GUP_LIST  has been added.
BUT ADDITION OF THIS TABLE HAS NOTHING TO DO WITH CLIENT COMMUINCATION

STILL Leagacy SEP clients will commuincate with SEPM that is on RU5

OK
I have upgraded the sepm. but exported client package size is more then previous version.

in sep 11mr4mp2  size was arround 72 mb but now it of 98 mb.

has any one noticed this.

yes  ,we have seen that in RU5 the package size has increased.

Then why symantec has mentioned in the documentaion  that package size has decreased in ru5 so that upgrade will be faster.

Hi Raghav,

As Prachand said the package size will be less only when you do upgrade using SEPM.
You are going to get a big package size when you export. this is because increase in the updation file size.

Ok i just performed the update of SEPM from Sep11mr4mp2 to RU5.

After that i performed the autoinstall with the newest package. I monitored with the task manager the traffic on my lan interface (no other programs running) and it only shows about 10 MB traffic. That is a great size for a symantec update. The update itself lasts about 5 minutes on my Core 2 Duo  T9400 with 2,54 Ghz and 4 GB RAM (windows xp sp3).

What i miss is an completion notice. But it's ok.

But i have a question. I created a group for the update and assigned both packages 32bit and 64 bit. Does Symantec decide what to install ?

Greets
Stephan