MR4 is showing up on my File Connect as well.

Probably won't install until next week so I am certain there are no major issues with it.

So, if MR3 was released this past October, and MR4 was just released (only 2 months later), does that mean that MR3 is buggy and I should skip over MR3 and go directly to MR4? We are currently at MR2 MP1. Just seems wierd that there were no MP patches and MR4 came out so soon after MR3.

Thanks!

I would skip MR3.  We had numerous issues with it that we did not have with MR2--we have been waiting for MR4 to hopefully address those problems.

Hmmmm - will have to check this!

Be certain to look through the readme.txt in the CD1 zip.  There's some useful information about upgrading from various previous versions that may affect MR4 deployments.

MANY thanks for the heads-up on that!

Will do - last thing we need is more issues caused by not reading! LOL

4 releases in one year !

I think this software should be re-released at least for the management part.

Less ambitious but more bugs-free

Hope this time can solve all the problem.....and really worry about any error durning upgrade...

I've installed MR4 (upgrade from MR3 rather than clean install - after taking a swift VMware snapshot of course). The upgrade was pretty seamless and have pushed the client out to a few test machines without issue.

Well I did a test upgrade on my test domain and everything seems to work well. First 100% seemless upgrade that I have had. Server upgraded fine MR3 to MR4 without a reboot, clients upgraded seemlessly from MR3 to MR4 without a reboot. Virus definitions are updating fine. No errors at all.

I'm using a SQL2005 Entrprise, 2 VMWare servers running SEM (with SEP for the OS protection)

I was a bit worried when I saw it was restructuring the database while I upgraded the first server, thought, oh crap! There's another server in this system, what will happen!

Well, nothing, really. I did shut down the secondary server, upgraded the first, then turned on the second server, upgraded it - it saw the database was already changed, uneventful. I could see some differences in the management console, but nothing earth-shattering so far. Like no button to save the column order, etc.

Will try client upgrades now that the management is done and seems fine.

Good to hear from you all! Whew, your messages made me feel easier.

Thats good to hear, the save button has been removed since we save the view all the time now anyway, it was one of those things that was a bit "halfway house" which we enhanced with MR4.

For me, it didn't save when I used that button anyway. I could leave that view, return, or close the manager, then return, and it would go back to factory default.

Thanks much for helping out, Paul. It's appreciated.

If you know a Marise Gwinn in Dublin, say hi to her for me.......

Hmm still showing up as MR3 on FileConnect. Any ideas?

Depends on the Language you need, it appears:

Product  Full Version  Language  Platform  Symantec Multi-Tier Protection 11.0 - International English  11.0.4000 MR4   International English  Microsoft SQL Server 2005/RedHat Enterprise Linux 4.0/Windows 2000 Advanced Server/Windows Storage Server 2003/XP Professional w/SP1/XPSP2/Windows Vista/Windows 2000 w/SP4/XP/Windows 2000 SP3/SUSE Enterprise Linux 10/RedHat Enterprise Linux 3.0/Microsoft SQL Server 2000/SUSE Enterprise Linux 9/RedHat Enterprise Linux 5.0/Windows Server 2003/Win XP 64

Seems that the non-English versions are still MR3

It can take a few days for the entire license database to be updated.

MR3 took a few days for me to get.

Well, The SEPM upgrade Process worked fine, with no problems.

After That, i assigned the new package to upgrade with it some groups. i noticed, that MR3 clients upgraded with no problems. WOW! For the firs time i saw how this procees is due

But MR2 to MR4 don't.

after 2 days of waiting, MR2 and MR2 MP2 Clients won't upgrade at all. no one of them.  

i had this problem allways, from the first Realease that came to us, with CD. this auto upgrade proces never has runned for me. so i alway was updating the client manually. now i have more than 100+ clients.. and i don't want  to update it again manually . 

why my MR2 client won't update to MR4? pls help someone (or i need to open a case?)

(sorry if i'm writing in the wrong forum threat)

I have upgraded my server from MR3 to MR4 and now only a handful of clients are talking to the server. I have about 2000 clients and running SQL on a seperate server where the database is located. :( If I have to run the same tool I ran when going from MR2 to MR3 on 2000 machines it isn't going to be pretty. :(

Any suggestions?

I'm downloading the MR4 CD's now. I'm going from 11.0.780 and will just do a fresh install. One management server, five other servers and about 90 clients with about 20 of those offsite in remote offices. I guess I'll have to create new packages and push them down to worksations.