Video Screencast Help

OSX 10.8.4 + SED 10.3.0 MP1 & MP2

Created: 04 Jun 2013 | 15 comments
sven_frank's picture

Hi All,

Apple just released OSX 10.8.4(some hours ago) for the masses. 

We have been running QA Tests already with the Beta Versions and have seen no negative impact with it. 

The Final Version of 10.8.4 seems to create no supprises so far and we had so far also no Customer Report with an Issue on that Version. 

10.8.4 seems to be "ok" for the time being but isn't fully tested yet.

So 10.3.0 MP2 is very close to release but came basicly to late for testing it against the final build of OSX. The Version will be tested now and might get certified for 10.8.4 (stay tuned hope to have some postive news here). 

If something comes up etc. we will publush KB Article's and post them here when they corelate with 10.8.4 & SED 10.3.0

Operating Systems:

Comments 15 CommentsJump to latest comment

PGP_Ben's picture

We have done some smoke tests with upgrades on a few 2012 Retina MacBook Pro's and 1 2012 MacBook Air. So far the results have been good.

I know that QA has been testing with OSX 10.8.4 builds on 10.3.0 and 10.3.1 (10.3.1 is not released till later this year).  So far the results have seemed to be fine.

I will update this thread if the status changes. Meanwhile, in regards to the thunderbolt firmware update issue we saw prior. No customers have reported the issue that we can confirm solidly. So far it seems it was an issue isolated to one machine in Support who had the issue upon upgrade.

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

Ahrenstein's picture

I'm interested in upgrading from 10.8.3 to 10.8.4 and I'm running PGP WDE 10.3.0 MP1 Build 9060. What steps are recommended for making this work? (I also have Windows 7 Ultimate 64-bit SP1) in Bootcamp running the same Symantec software.

Thanks

sven_frank's picture

Hi Ahrenstein, 

1. Do a Backup 

2. Within OSX it seems to be safe to install 10.8.4 just the normal way (so far we have 0 reports of Issues) 

==> When the version matches on both sides you don't need to do any further steps:

As soon MP2 comes out (should be in some days) you should upgrade osx first and then do the same on windows. 

But please be aware 10.8.4 is not officially QA'ed yet also when it has been tested with. 

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

jimsky7's picture

I have an  install of PGP 10.3.0 MP1 on top of OSX 10.8.4 and it fails to proxy email connections. Am working to understand why. PGP attempts to connect to remote email server and negotiates SSL, but the connection times out after about 10 seconds. Can't get mail in or out.

I previously had PGP 10.2 installed, and it also started failing to proxy around the time OSX was upgraded.

I also have PGP 10.2 installed on another OSX 10.8.4 system (iMac vs Macbook) and it works there! So it sounds like this is an interaction between the new PGP and the 10.8.4 upgrade.

Can give lots more details, but wonder if anyone else has had connection/proxy problems with this combination?

sven_frank's picture

HI jimsky7,

PGP Desktop 10.3.0 MP2 should be shipping tonight and should have availibity later the day on fileconnect. 

I haven't seen this particular Issue in this combination yet but it should be looked at. 

Since it is only little work wait until MP2 comes out and check the diffrence. 

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

jimsky7's picture

I have a trouble ticket in with Symantec on this particular PGP issue.

I have narrowed it down to an issue related to one PGP-secured email account slipping out of SSL/TLS mode and into an unencrypted mode, which then causes the PGP proxy on port 25 to fail -- to time out instead of completing its connection. Because this may not be related to OSX versioning, I will not comment in this thread again unless it ends up being relevant to the topic.

sven_frank's picture

Hi Jimsky7,

cool thanks for the update that it seems to be not 10.8.4 related since we had no reports in this area. 

Thanks

Sven 

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

sven_frank's picture

Just as FYI:

10.3.0 MP2 has been released yesterday.

And I'm posting this from a fully encrypted 10.8.4 MBP with MP2 on it 

 

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

Tom Mc's picture

Fileconnect is available at https://fileconnect.symantec.com/

When you consider your issue resolved, please click Mark As Solution on the most helpful response.

Search the Knowledge Base &

jimsky7's picture

But as is typical, Fileconnect has only the MP1, not the MP2 version.

Ahrenstein's picture

FIleconnect says my serial number is invalid. SymAccount also said that. Why is a $220 license not valid in your system two weeks after purchase?

PGP_Ben's picture

@ Ahrenstein - make sure you are using the Serial Number provided to you by licensing. I'm sorry but Technical staff on the forums does not have access to your licensing information.

 

Be sure that you are using the serial number and not a product license key used to license the Symantec Encryption (powered by PGP technology) product.   It should start with something like a TMP or M something in the front of it. If all else fails, you can call our customer care who should be able to verify entitlement to the update and provide you with a temporary serial number. Just contact customer care.

Telephone:
800.721.3934 or 541.335.7023
 
Found here:
 
http://www.symantec.com/support/assistance_care.jsp
 

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

Hackajar2's picture

OS X 10.8.4 + MP2 still "bricks" about 1 in every 5 machines we upgrade. (MacBookPro 6,2)

Is there any way to recover from the doomed "gray circle cross" screen when this occurs?  

With all the notes of bricked machines on the forum, it would be nice to see a recovery tool for when this happens.