Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SEPM reporting Mac clients as version 12.5.0001.8888

Created: 05 Oct 2010 • Updated: 05 Oct 2010 | 5 comments

Some of my SEP Clients for Mac are showing in the SEPM console as version 12.5.0001.8888 instead of the version 11.0 that is actually installed and running on them .  Has anybody else seen this problem?  Any fix?

Thanks,

-Craig

Discussion Filed Under:

Comments 5 CommentsJump to latest comment

sandra.g's picture

Funny you should ask.  I just learned that this is resolved with RU6 MP1.  If you have not updated your client to 11.0.6100.645, please do so.

sandra

Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!

Cozy Wintermute's picture

I also see 12.5.0001.8888 on MacOS-X.  And I could not find any infomation on the RU6 MP1 release note in Japanese.

Why RU6a in US and RU6 in Japan are same version? Please synchronize the version and its name globally.  In Japan, we get a not enough information earlyer, so must search English document. I would not conflict during solving problem at all.

Thanks.

sandra.g's picture

For SEP for Macintosh, there is no RU6a (11.0.6005).  It's either 11.0.6000 (162) (RU6) or 11.0.6100 (0179) (RU6 MP1).  Or do you mean something else?

As I understand it, the fix that is noted for RU6 MP1 (below) had the side-effect of resolving this build number issue as well.

Managed clients fail to display management information after a period of time
Fix ID: 2075100
Symptom: Managed Symantec Endpoint Protection for Macintosh clients stop displaying management information after event rewrites the SymantecRegistry.xml file to zero-byte size.
Solution: Added functionality to remediate the SymantecRegistry.xml when the file is corrupt or missing.

sandra

Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!

MattBarber's picture

So what's the prefferred way to upgrade, just to push the upgrade package out to all of the problem clients?

Will the SEPM ever allow assigning an install package (if it's so easy to upgrade the clients, why can't the SEPM do it)

Matt Barber
Application Specialist

TN User Group Marketing Director

sandra.g's picture

You will have to export a new package after migrating the SEPM, then overinstall the SEP Mac client.

I hear there's more OS version parity coming.  I don't honestly know if assigning a package (to auto upgrade) is among those things, since I don't know the technical detais by which the clients are upgraded on the Windows side, under the hood.

sandra

Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!