Endpoint Protection

When I am checking on one of the PC's, I see this message, "The client has decided to reject the upgrade package"

1. I have not designated ANY upgrade pacakge for this site or client

2. This PC is ALREADY at the LATEST version, so I am not sure exactly what it is rejecting

3. There have been no manual or remote pushes to this client.

4. Why would a client reject an upgrade package anyway?

5. Copy and paste STILL DO NOT work in IE in these forums.

Thanks everyone.

See Elisha Comments

There are several important items to remember when updating the client feature set from SEPM:

1. Make sure you uncheck the "Maintain existing client features when updating". If you don't uncheck this then the clients will not do anything.

2. Make sure you uncheck the "Upgrade Schedule" checkbox. This way the clients chose to update their feature set immediately.

3. Make sure that the package you assign to the group is the same build number as the SEP clients in the group. If you assign an older build for this then the clients will ignore the settings.

4. Make sure you assign the correct bit rate (32bit vs. 64bit). Clients will only look at packages with their bit rate. If you assign a 64bit package, for example, and you have only 32bit clients then they will ignore the settings.

5. In most cases once the client has added or removed features you will need to reboot the client for the changes to be complete.

https://www-secure.symantec.com/connect/forums/problem-upgrade-clients-sep121#comment-6126291

BOND, JAMES BOND!!! Thank you, but there is nothing out there, no pacakages were assigned to this PC or to her group.

How many SEP client showing same error ?

If one or two system may be it's old log try to delete sep client in SEPM console after some time SEP client reappare again.

This is interesting, all of them in my Chicago location are showing this, but there is no assignment of an upgrade package to this location. Outside of this location everyhing is copasetic.

On the Clients page, there is no package assigned under the Install Packages tab?

Delete the client from the SEPM and let it check back in

You can enable sylink logging as well to see the communication between client/SEPM.

I don't suppose any of these machines have an updated SEP_INST.log file in the C:\Windows\Temp directory do they?

The timestamp may help you pin down what's going on.  Also, I think the below string appears if it's upgrading from the SEPM:

IDCDEPLOYMENT=AutoUpgrade

Also, depending on how far you want to investigate, the sylink logs can tell you more about what the client thinks it should be installing

Excellent idea.

Looks like that did not work, I am trying once more just to be certain.

Deleted it, re added it automatically, and same old same old. hmmmmmmm

The log is from July of 2013

That string is in fact present

Verify you applied the correct package architecture (32/64bit).

I continue to be told that all clients are 64-bit but I come to find out some are actually 32-but which explains why they get rejected. Once I add the 32-bit package, life is good.