Endpoint Protection

At several sites (fortunately small), I had SEP/M 11.5002.333 installed, and upgraded to 11.0.6.  When I performed the Upgrade Groups with Package command, the XP clients all politely updated to the MR6 clients, but I had to upgrade the W7 clients manually.  What am I doing wrong here that the W7 clients aren't upgrading automatically?  Thanks for any pointers.

Are your Windows clients 32 or 64 bit? If 64 bit, you will need to create a 64 bit package and add as well.

I have both 32- and 64-bit clients.  So are you saying I need to export a new 64-bit client install package before doing the group update?  (I don't need to do that if upgrading XP PCs or Server 2003/2008, both 32 & 64 bit).

If you are having both 64 bit and 32 bit clients in a group,you have to add both packages to that group.
Are you try by disabling UAC?
Also do the following things
Disable the File Sharing Wizard.

Enable network discovery by using the Network and Sharing Center.

I have 32- and 64-bit clients in different groups - I do not mix them. 

I have not tried disabling UAC - why would that make a difference?  UAC is enabled on my W2K8 x64 server, but that upgraded just fine.  Also, how does the File Sharing Wizard affect this?

Network discovery was already enabled on all the W7 PCs.

i asked you to do so is just for testing.can you try and give us a feed back?

I found that UAC really interferes with things on W7 far more than VISTA or other OSs.

I've got a few in each group that won't upgrade, no rhyme nor reason, in the server group, 8 of 10 did, 2 did not, yet I can push the install to them just fine.
So for some reason, with this release, some clients don't do the upgrade, while most do.
With the W7 machines, only those with UAC shut down upgrade successfully.

I  tested mine and they upgraded fine.  We needed to reboot some clients to get the install to happen but needed to do that in Vista too,.
 

I've noted as well that when a client or server is rebooted, sometimes the install goes. Why is that?
Why doesn't it go with no reboot?
But it doesn't always take care of it.......... sometimes I've still had to push.
The good thing, though, is that those are a very small percentage. I mean, if you get over 90% success at ANY install or upgrade, IMO, you are doing well! And I'm pretty close to that.

Now that I think about it: on the last upgrade, 1 of the 4 W7 PCs did have UAC disabled (was x64), and it did not upgrade automatically.

I will try the rebooting method and see if that helps at all.

If you perform a Windows update, add/remove software, etc, and it requires a reboot, the installation won't go through.  This isn't a limitation of the software, the Windows installer with VIsta and Windows 7 is actually rolling the installation back because it does a check to see if a reboot is required before proceeding with the installation.  This event is usually logged in the application log.  In instances where a reboot doesn't fix the issue, the cause is usually some software that uninstalled or installed, set the flag for reboot required, and then didn't remove the entry from the registry after the uninstall.  In those instances you have to manually remove the pending reboot entry in the registry.  The other thing with Windows 7 / Vista is that you should deploy to those machines using silent installations.  This is covered in the readme. 

Well, I did another upgrade on another server.  This time I exported all my client install packages before updating groups with the packages.  And the results: 3 for 3 with the W7 updates.  All are x32, UAC on.  Odd.  Maybe doing the export beforehand does matter?  Either way - I'll take it.