Endpoint Protection

I have recently upgraded my SEP Manager  "Cluster" from 12.1.671.4971 to 12.1.2015.2015. 
It seem that the WIN64 Package is corrupted because in it's properties it has only 60MB of size.
When i export the package and try to install i get an Error about a missing file.

How can i reimport the Package into SEPM?

The packages should be on your install media, you can just import them following the below KB article:

How to manually import client packages into Endpoint Protection Manager (SEPM)

Hello,

I would suggest you to Run the upgrade wizard located in:

'C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\upgrade.bat'

which would repair the client package and make sure it is updated.

Hope that helps!!

Hi,

Check this thread

http://www.symantec.com/connect/forums/export-package-sepm-121-not-working#comment-6712961

The Corrupted Package is a imported executable package that was done before we upgraded to the new version. This import is one Month away, so no chance to go back and restore...

Adding is not possibile because the package already exists and the SEP Manager got no option to overwrite it.

We Upgraded the installation today, so the upgrade wizard has already been run, but it also said that the package already exists....

I'M also unable to delete it. Message here is "...is the lates pacakage. You cannot delete it"

hi,

if you have try all of possibility you can raise support ticket.

How to create a new case in MySupport

http://www.symantec.com/business/support/index?page=content&id=TECH58873

Phone numbers to contact Tech Support:-

Regional Support Telephone Numbers:

• United States: https://support.broadcom.com (407-357-7600 from outside the United States)
• Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)
• United Kingdom: +44 (0) 870 606 6000

Thank you all. I have opened a MySupport case now.

If I understood correctly you had the install package for SEP 12.1 RU2 imported to SEPM RTM - so before the upgrade to RU2, right? Well that unfortunately is not recommended action - the newest imported install package on the SEPM should not be newer than the SEPM itself - otherwise SEPM may not be able to properly process it and thus the corruption. Not sure if you get around that without SEPM repair/reinstall - but let the support have a look, maybe they come with something up.

Hi,

Did you ever find a solution to this? I am in the same situation.

My Solution was to wait for the next release and install it normally.

Now, everything is ok.

Ok, that's what I was afraid of. Who knows when the next release will be.

Did Symantec Support give you any alternative solutions?