The ConfigMgr Advanced Client received policy that could not be verified
Dear all,I have seen similar posts but none of them brought me to the sollution of my problem.We have X64 machines that start to have problems since few days.They are fresh installed but soon after the task sequence have finished and the machine is started up the following errors is shown in status messages.The ConfigMgr Advanced Client received policy that could not be verified. For more information see PolicyAgent.log on the client machine. Message ID: 10821I can see in the locationservices.log that the machine is refreshing the siteserversigning certificate and says successfully stored new site signing certificate.I have changed my webserver and signing certificate but without solution.Anybody a clue?
June 3rd, 2009 6:16pm

Now I try to reinstall these 64 Bit desktops without software patches, I believe this error might be somehow related to the latest patches. No other workstations have this issue then the 64 bit ones.
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2009 10:35am

Just curious ... did the PolicyAgent log on the client detail any more information about the reason for rejection of policy?
June 4th, 2009 12:43pm

signature verification failed for policyassignmentIDI tried to remove the security reg key and let it repair itself... same error after a while.All 32 bit systems run without any issue. I start to think about downgrading the site back to mixed mode.We need to get this working soon.. we have users that need the new machines for a customer.similar as this thread http://www.myitforum.com/forums/m_190207/mpage_1/key_Client%252CVerification/tm.htm#190207
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2009 1:14pm

I now tried an install not using images but the install operating system package and excluding updates.So far it is installing the first packages and the error message have not showed up.I have read other post about os deployment and the key that get stuck in the registry perhaps this is my issue as well.I can try to make a new image, install using without images. Anybody a suggestion or article that might help out?I have to mention as well that I have no software updates installed yet, they are running now so I hope to find that they are not causing the cert error.
June 4th, 2009 2:59pm

I found that when I install the X64 machines from operating system install package not using images and install mandatory patches i get the error. 58 patches where installed on the X64 Vista SP1 machine so that will become quit hard to find where the error started. There are a few approaches that I can take to solve the issue. 1. Do a DVD based OSD deployment and assign all patches except the patches of the last 2 months. See if that install keeps working and then do the install again with the patches of april see if it keeps working and continue until the error is shown. This will take some time so I thought .... 2. Do a DVD based OSD deployment with Vista SP2 (no I will not try to make an image I know that is not supported yet) and install without software updates. This will make sure that al lot of patches dont need to install. Then I will let the rest of the patches come after OSD is finished. If that keeps working I can get the users working for now and start finding what patches make this certificate error.
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2009 10:18am

Yes sorry I have done this, again sorry.Any help is very very welcome I have the idea that I tried all possible.
June 5th, 2009 11:38am

Torsten,Can it be that a certain advertisement causes this error?As soon as I added it to a group that is uses in a query collection to assign software packages this error came.Can I check the policy has with a advertisement or program/package somehow?Arjan
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2009 1:54pm

I removed the advertisements that where assigned to the collection that where updated based on the group membership. I recreated them and the error showed up. Then I removed the advertisements one by one. I found one advertisement causing the error. I have removed the package and recreated all advertisements. Now it is running again. I agree With LA1976. We recently moved to Native Mode. I had a collection that would not get software updates, advertisements etc. There was a bad advertisement that I deleted which made things work.
February 19th, 2010 7:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics