Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Upgrading to MR3

Updated: 21 May 2010 | 8 comments
Hedy's picture
0 0 Votes
Login to vote

I am planning on upgrading to MR3 from MR2 MP2, here we go again. For those of you who have gone through this migration were the MR2 clients able to communicate with the new MR3 SEPM console?

 

I will be gradually pushing out MR3 client to my servers and want to ensure that communication b/t client and manager will not be intrerupted until I am able to push out MR3 client to all serves and PC's.

 

Thanks!

Comments

bains1000's picture
22
Oct
2008
0 Votes 0
Login to vote

We have carried this migration out 4 times and each time we have experienced problems.  We have been on the phone to Symantec support for over 5 hours today trying to fix an upgrade from MR2 to MR3.

 

The situation has been left with the engineer telling me i may have to manually uninstall over 100 clients to upgrade them to MR3.

 

I have NO confidence in Endpoint, we have experienced too many issues and we continue to experience these on a daily basis!

Hedy's picture
22
Oct
2008
0 Votes 0
Login to vote

Thanks for your response. I started with MR1 which in my opinion was really a beta version. I certainly do not not need anymore headaches at this point since I have done numerous installations as well. Makes me wonder if I should go ahead with MR3. Manually installing the client is not an option for us. I have a call into support I can let you know what they say. Last week I had to use their D.R. process to move our database on our SQL server because they said that the database was corrupt. Amazingly it worked...they highly recommend that any installs be done from the console, using RDP according to them is just asking for trouble.

kornholio's picture
22
Oct
2008
0 Votes 0
Login to vote

I can only answer from personal experience...stick with MR2 if not having problems with that version.  I wish we had.  I'm seriously considering rebuilding both of our MR3 servers with MR2.

Hedy's picture
22
Oct
2008
0 Votes 0
Login to vote

Thank you for the reply. I am getting the request to upgrade to MR3 since if fixes some issues, see below. Figured the upgrade was inevitable. So far only negative responses which is not a good sign.

 

"There there are a number of fixes for issues we are having with MR2. Most recently SEP prevented users from saving Word documents to network shares.  We were able to get around this issue by disabling some features in the client."

kornholio's picture
22
Oct
2008
0 Votes 0
Login to vote

So far (fingers crossed) we have not seen any problems from the client side with MR3 , only from the server (but have only upgraded approx 30 of 1500 clients).  If it resolves your client issues, I guess it's better to have a handful of administrators with headaches rather than all of your users.  Good luck.

Hedy's picture
22
Oct
2008
0 Votes 0
Login to vote

Would you mind briefly describing the server issues you ran into.

kornholio's picture
22
Oct
2008
0 Votes 0
Login to vote

We have seen the issues mentioned in the posts below.  Some have been easy to fix, others "Symantec is investigating the cause of this issue", thus no solution yet.  All (except possibly the Domain ID issue) began with MR3.

 

https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=18763

 

https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=18686

 

https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=17165

 

https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=18079

 

Also, regarding the report server, we have trouble viewing the logs from remote consoles--we get prompted to login to the report server and it fails regardless of credentials used.  I haven't tested enough to say this happens EVERY time, but it has happened multiple times.  I can't remember this happening when accessing locally from the SEPM.

 

Our environment has 2 SEPM servers, not connected in anyway, each with their own clients.  We have seen all of these issues on one of the servers, some of these issues on both.  

 

Please note that I don't mean to try and convince you not to upgrade to MR3--I'm simply trying to convey the problems we've had.  It seems that some folks have been able to upgrade with little or no issues, while others have had multiple problems.  I've been through a number of rebuilds since SEP's initial release and I have had to rebuild at least one (sometimes both) of our SEPM servers during each MR upgrade--yet we have not had many of the problems other users have reported on in the forums.  When we have rebuilt a SEPM server, it may have been fixable.  But for us, it has been easier starting with a fresh install than trying to fix a crippled one.

Message Edited by kornholio on 10-22-2008 10:21 AM
toasale's picture
22
Oct
2008
0 Votes 0
Login to vote

I don't understand why so many have problems installing SEP and any of its maintenance releases. Could it be that I use this on a non-networked laptop installed by myself? The unit is a 5 year old Dell (1.66ghz CoreDuo with 1.5gb 533mhz ram) D620 that uses two HD's separately: XP Pro SP3 and Vista Ultimate SP1. I have not had any problems in the areas I read about, other than user brain loss. Not bragging, but I do not have any certifications other than breaking and fixing 3.10, 3.11, 95, 98, 98SE, 2000 Pro SP4, XP Pro and Vista units continously for 13 years.

 

I'm familiar with networking, but not servers, so what am I doing right?:smileywink: