Hi,
Last week I updated our SEP Manager from 14 to 14 MP1. I have a group called HOME in which I have several machines for testing. Within HOME I have a group called INSTALL which inherits its policies from HOME. The INSTALL group has the install packages for 14 MP1. HOME has no install packages assigned. I moved a few of the test machines into the INSTALL group and they updated from 14 to 14 MP1 without incident. I felt all was well after testing.
Our production machines belong to a group called WORK. Within WORK is a group called INSTALL. INSTALL has the install packages for MP1. It is an identical setup to HOME other than the WORK group is server controlled and offers few options to the clients. I decided to upgrade 1 client from 14 to 14 MP1 by moving it to the INSTALL group. Nothing happened. I rebooted the client (Win 7 machine) twice and that made no difference. I tried moving other machines with no positive results. The INSTALL group within the WORK group worked fine with 14. I finally discovered that when I moved clients to the INSTALL group the clients were not recognizing the move. The SEP manager showed them in the proper group. When I opened Troubleshooting on the clients that had been moved, they all still showed they were in the WORK group. I tried copying the policy settings from WORK to a new group and the problem moved to the new group as well. I finally created a brand new group and built the policies from scratch. A tedious procedure lol. The brand new group worked fine and I was able to update my test machine.
Can anyone offer a reason why the WORK group has this problem? All clients use the Pull mode and check in with the manager every few minutes. I also discovered that if I moved a client to the HOME group and them moved the client back to the INSTALL group within the WORK group the update process would begin within the clients. My only guess on this is some sort of corruption occurred on the WORK group during the upgrade.
Thanks,
CQ