Here’s a new Knowledge Base article we published today. This one explains why in System Center Configuration Manager, when you set the Site Code of a Software Metering rule to a secondary site, that rule will not be applicable to any clients:
=====
Summary
In System Center Configuration Manager, when you set the Site Code of a Software Metering rule to a secondary site, that rule will not be applicable to any clients.
This is expected behavior.
More Information
SMS 2003 Advanced Clients and Configuration Manager clients within a secondary site boundary also obtain policy from the primary site’s site database. If the Site Code of a Software Metering rule is set to a secondary site, no policy will be generated for that rule, so that no clients will receive that rule. You must set the “Site Code” of a rule to a primary site’s site code to make it assigned to clients.
=====
For the most current version of this article please see the following:
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/