Last year @MMS Kent showed our automated RBA solution and I just discovered that this does not work in ConfigMgr 2012 R2 CU1 environment. It seems like they have changed the process behind the UI and in ConfigMgr 2012 R2 CU1 environment they are using different IDs to identify the Object. Before they used FolderTypeID value but now they are using SecuredTypeID values. You will need these values, if you are working with SMS_SecuredCategoryMemberShip WMI class and AddMemberShips/RemoveMemberships mehtods
FolderTypeID | FolderTypeName | SecuredTypeID |
2 | SMS_Package | 2 |
7 | SMS_Query | 7 |
9 | SMS_MeteredProductRule | 9 |
11 | SMS_ConfigurationItem | 11 |
14 | SMS_OperatingSystemInstallPackage | 14 |
16 | SMS_VhdPackage | 16 |
17 | SMS_StateMigration | 17 |
18 | SMS_ImagePackage | 18 |
19 | SMS_BootImagePackage | 19 |
20 | SMS_TaskSequencePackage | 20 |
23 | SMS_DriverPackage | 23 |
25 | SMS_Driver | 25 |
1011 | SMS_SoftwareUpdate | 37 |
2011 | SMS_ConfigurationBaselineInfo | 11 |
3011 | SMS_GlobalCondition | 32 |
5000 | SMS_Collection_Device | 1 |
5001 | SMS_Collection_User | 1 |
6000 | SMS_ApplicationLatest | 31 |
6001 | SMS_ConfigurationItemLatest | 11 |
Best,
Kaido
[…] blogs about Working with Security Scopes in Configuration Manager with PowerShell and recent changes under the hood in Configuration Manager 2012 R2 […]