anyone already installed RU3 ?

[ace1]

did anyone already dare to install RU3 from MP1?
Is the RU3 upgrade install more polished than RU2 (that was riddle with certificate/database defects/misc)?

thanks

[Aleksandar Devecerski]

Yup, two days ago.

Deployed to one server and selected group of workstations (W7/W10, laptop/desktop combo). No problems, everything went well.

The only issue I've seen is in SEPM, Install Packages -> RU2 (4615.2000) WIN64BIT package got deleted. The rest of RU2 packages seem intact. I tried (re)adding WIN64 install package afterwards, after I've noticed this. Just in case. Package appeared in the SEPM alright, but was deleted again after a while?! But, as I'm most likely going to move all the rest of the client groups to RU3 in a couple of days anyway, I'm not bothered (much) with this.

Besides that, nothing negative to report.

[ace1]

thanks for the feedback.

[DAVID MATTHEWSON]

Well, I tried to u/g our 14RU2 to 14RU3 - and it failed. The console u/g went fine then the dBase got to 100% and then 'error occurred' (see pics)

This is a VM which had a clean install of 14RU2 last year because ... the u/g failed and support could not help.. I like the product when it works but really feel it's time to look for a replacement for our sites.  Sigh..

Thank goodness for VM & snapshots - easy to get back to stability!!

[David Hicklin]

The RU2 (4615.2000) package gets deleted by the RU2 Patch 1 ,  do you have package 4637.2000 ?

[LUK JASON]

upgrade fail from 14.3 RU2 to RU3

[Aleksandar Devecerski]

>do you have package 4637.2000?

In my case, no. Haven't even seen that build.
We went from RU2 (4615.2000) to RU3 (5413.3000) and only WIN64BIT RU2 package got deleted.

[ace1]

Went to from MP1 to RU3 without, so far, problems.
The RU3 installers now does some prechecks before messing things up (ie digital certificate expiration).

In my case cert was expired (but MP1 was working just fine) so I had to switch all the SEPM<->SEP connection to unauthenticated http (to avoid losing the connection), renewed the certificate, then installed RU3.

[msnslag]

No problems during upgrade from SEP 14.3 RU2 to SEP 14.3 RU3.

However, after the upgrade under "Clients" there is a mix-up of Computer names and User names, which we hope will be fixed soon
as it makes the "Clients"-part more or less unusable.

[mcsldr]

We are also seeing the computer names and user names mixed up after upgrading to SEP 14.3 RU3

[John Owens]

For user names and computer names being mixed up after the upgrade please open a case.

------------------------------
John Owens
Strategic Support Engineer | Symantec Endpoint Security Division (SES)
Broadcom Software
------------------------------

[mcsldr]

Hey, after getting response from another user, that this is a feature, I investigated a little.

It appears in the client page when you right click on a client "Switch to user mode" and "switch to computer mode" menu options will reverse this.

It has to done for each client that is incorrect - which in my case was >5.

Regards,
MCSLdr

[JoWo]

Upgraded two of our four SEPM from RU1 MP1 to RU3 without issues so far.