Thursday, June 9, 2011

Signature verification failed for PolicyAssignmentID

I will say the sometimes in Native mode I have seen this problem and it was due to a problem with the certificate on the MP but this article assumes you have tested your site system and found no such problem

Problem:


1. Run Advergtised Programs is blank or partially populated

2. PolicyAgent log : Signature verification failed for PolicyAssignmentID


Solution:


Locate all the Programs from Packages that have bad OS Requirements. This means if you have a program set to run "All x86 XP workstations as well as x86 XP SP1, x86 SP2. Because you cannot have both All systems as well as the individual versions of the OS. The policy cannot be compiled due to this conflict.


When you check the client it appears to be working fine. It can update hardware but otherwise it looks fine.



Signature verification failed for PolicyAssignmentID {6dc2328f-1dd7-4cc3-95a9-3ca5aa34ec8a}.




The problem is that how do find the offending Program? Well there are many ways but I will just give you the one I used and I am sure I will find a faster way and repost. First connect to machine via Wbemtest (ROOT\ccm\Policy\Machine\requestedConfig). Enum Classes and select Recursive to list everything.






Next find the CCM_Policy_Assignment2 and click on it








Click on the Instances and you should see something similar to this below. Now find the line with your policy. You could create a query to find it but this is a manual approach.








When you find your line click and select "Show MOF" You sould see something like this

instance of CCM_Policy_Assignment2
{
AssignmentCondition = "{BA0997BC-AA74-498E-8D8E-B0A691F46F6F}";
AssignmentCookie = "2011-06-07 16:53:17.550";
AssignmentID = "{ef6d2778-3b08-4fdf-a989-cc48458c1bd6}";
AssignmentPolicy = "CCM_Policy_Policy4.PolicyID=\"C0220033-C020009D-7D1B5B9B\",PolicyVersion=\"4.00\",PolicySource=\"SMS:P03\"";
AssignmentSource = "SMS:P03";
AssignmentVersion = "4.00";
};




SELECT TOP 1000 [PolicyID]
,[PADBID]
,[PolicyAssignmentID]
,[OfferID]
,[PkgID]
,[ProgramName]
,[OfferCRC]
,[PkgCRC]
,[ProgramCRC]
,[ProviderVersion]
,[ParentPolicyID]
,[DepSourceID]
FROM [dbo].[SoftwarePolicy]
where PolicyID like '%C0220033%'

Advertisment - PackageID -xxxxxxx






This query will help you find the offending program and now you can find the offending program

Wednesday, May 18, 2011

SCCM 2007 Performance Considerations

Many times in the forum you will see administrators ask how to setup their hard disk arrays for best performance with SCCM. While this is not approached directly in the ConfigMgr documenation it is understood that you should always install the Configuration Manager application on a different drive than your OS. With that in mind, Microsoft has a document that will help with performance considerations for sites between 10,000 and 200,000 machines. If you are running a site less than 1,000 machines you could easily install everything on one drive and not see performance degredation but I would not consider is a best practice.

What is great about this document is the detailed information on Volumes, Raid type and number of disks.

10k clients (Single machine) Configuration
Site Server / management point:
* 2x2 Xeon @ 3 GHz
* 4GB RAM
* SAS write back / read ahead cache (with battery backup) options for all volumes

VolumePurposeRAID Type# of Disks
1Operating System/SQL Server Temp DatabaseRAID 12
2Configuration Manager 2007 installation files and SQL Server site databaseRAID 12

This document and other valuable White papers can be found here:
http://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-white-papers.aspx



Exact white paper:
Configuration Manager 2007: Sample Configurations and Common Performance Questions

Please note that the document was created in July 2008 but still contains valuabe information that can be used today! Microsoft cannot keep up with every change in Disk and CPU technology so please adjust as necessary. For this reason Microsoft cannot recommend how to setup every different enviroment because there is no way of knowing the performance of your hardware.


Tuesday, March 29, 2011

Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1 as supported platforms for Configuration Manager 2007 Service Pack 2

Looks like Microsoft is set approve the use of Sp1 for 2008 R2 and Win7. There is a hotfix that needs to be installed.

http://support.microsoft.com/kb/2489044/en-us?sd=rss&spid=12769

Hopefully no one jumped the gun and installed Sp1 in their enviroment before it was certified by the ConfigMgr group. As a general rule when something new comes out you should look to MS for their 45 to 90 day rule of testing. Once they says it works then you can install/upgrade. This goes for SQL versions.

Running this hotfix on your site systems will add the capabilities you desire. There were problems with this site earlier in the day so keep trying if you have a problem. Many people are dowloading it I bet