Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

SEP 11 ru6 MP3 SEPM manage an MR3 Client?

Updated: 19 Apr 2011 | 5 comments
por997's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi Everyone,

 

Can SEP 11 ru6 MP3 SEPM manage a SEP 11 MR3 Client?

Cheers.

Comments

Prachand's picture
19
Apr
2011
0 Votes 0
Login to vote

Yes , it can manage.

Yes , it can manage.

A SEPM on RU6Mp3 can manage an MR3 Client.

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

Mithun Sanghavi's picture
19
Apr
2011
0 Votes 0
Login to vote

Yes.

Hello,

Yes, It can manage.

I would also recommend you to make sure you upgrade the SEP MR3 Clients to the Latest version via Autoupgrade Feature, once managed.

 

Upgrading clients by using AutoUpgrade
 
 

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

por997's picture
19
Apr
2011
0 Votes 0
Login to vote

We have over 100k clients,

We have over 100k clients, not sure how the bandwidth will cope with this.

Prachand's picture
19
Apr
2011
0 Votes 0
Login to vote

Since the you are on RU6Mp3

Since the you are on RU6Mp3 and the clients are on MR3  you first need to Upgrade to RU6 and then to RU6MP3
If bandwidth is a concern then you can create a pacakge and share it locally to the user and then they can run

.But in Autoupgrade we can push the pacakge whenever we want depending on the free bandwidth.

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

Ryan_Dasso's picture
19
Apr
2011
0 Votes 0
Login to vote

Ignore the errors about parsing...

It's worth noting you'll get a few errors in the SEPM when managing out-of-date clients. These are expected. they occur because the information included in the logs is different between versions... basically the MR3 clients report fewer things than the RU6 clients, so the SEPM returns an error indicating what it sees as a truncated log.