Video Screencast Help

SEPM 12.1 upgrade

Created: 02 Jan 2013 | 12 comments

Hello all,

Happy Newyear to all of you.

I have a question about automatically upgrading clients to the latest version of SEP from the SEPM.
I recently upgrade to the latest version of SEPM 12.1 RU2, and im attaching the new clients to some of my groups to test the functionalty of the new SEP clients 12.1.2015.2015.

Strange thing is some of the clients upgrade to the newest client and some don't even after a few weeks they still didnt upgrade to the client i attachted to this group.
Does anyone know why this behaviour is happening?



Discussion Filed Under:

Comments 12 CommentsJump to latest comment

Mithun Sanghavi's picture


In the Enterprise version, you can use Upgrade Clients with Package to upgrade existing clients: 

However, the following cautions apply:

  • If you upgrade from 11.x and use Application and Device Control, you must disable the Application Control rule "Protect client files and registry keys." After the clients receive the new policy, you may upgrade using AutoUpgrade.

  • Due to possible bandwidth concerns, it is best to schedule AutoUpgrade for after hours. You can also stage and select a package on a web server when you run Upgrade Clients with Package, or you can use an alternate method to deploy the upgrade package.

This Issue may also occur due to either - 

- Upgrade schedule badly configured


- DNS issues.

I would request you to perform the steps provided below:

- Access the install packages tab and remove the upgrade packages that has been added;

- Add the packages again;

- Set new period of time time for SEPM to provide the upgrade packages to the clients.

If the DNS error is shown in SylinkMonitor, try to add the SEPM's IP address and name into hosts file as workaround but also verify if the DNS server registries are correctly configured.

Reference Article:

Auto upgrade does not work when migrating from SEP 11.x to 12.1

Also, Check these Articles:

Best practices for upgrading to Symantec Endpoint Protection 12.1.2

Steps to prepare computers to install Symantec Endpoint Protection 12.1 client

Hope that helps!!

Mithun Sanghavi
Associate Security Architect


Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

pete_4u2002's picture

i hope you are using the autoupgrade feature

have you scheduled the upgrade?
are the clients which have not been upgraded are they communicating with SEPM?

levd's picture

Im attaching the new client package to the group i want to upgrade.
The clients are all communicating normally to the SEPM.

ᗺrian's picture

Do they have the correct policy for the group they're in?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

pete_4u2002's picture

can you check the sylink log ? it should throw some light on the request for the package,

are the packages 64 bit as well 32 bit assigned to them?

levd's picture

Yes im attaching both 32 and 64 bits client packages. Can you tell location of sylink log file?

pete_4u2002's picture

firstly you need to enable it
How to enable Sylink Debugging for Symantec Endpoint Protection in the registry- SEP 12.1

ᗺrian's picture

Will be located in C:\

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

GeoGeo's picture

Have you upgraded from a SEPM 11 to SEPM12 RU2?

If so were you using Application and Device control to protect clients and registry keys? Disbale that rule set in the policy as SEP 12 has moved registry protection to a different area and this policy will prevent the SEP 11 clients with this policy from upgrading to 12 RU2.

Hope this helps :)

Please review ideas and vote there could be something useful :)

levd's picture

no not using application and device control, also some clients are upgraded normally..

RickJDS's picture

View the SEP_INST.LOG file located in C:\Windows\Temp.  Scroll to the bottom and work your way up to see if there's any errors why it didn't install.  Use a program called SMS TRACE from Microsoft to make viewing the log a lot easier.

levd's picture

Ok thanks i will look into things.