Thursday, October 20, 2011

How to create or change new Windows collections in ConfigMgr

By default there are 17 collections in ConfigMgr. Most of them will never be used, so they can be moved as subcollection for overview reasons. How to do that is described here: Move default collections in ConfigMgr 2007. That way collections for Windows 2000, Mobiles devices and Windows XP (for example) will be out of sight in collections overview.

Collections that can be moved (in my case) are:


Most of times I create a "_Unused Microsoft Collections" collection to move old/not used collections too. That way the Collection ID and used query will retained. Now it's time to create new collections or change existing collection queries. This for new Operating Systems like Windows Vista, Windows 7, Windows Server 2008 and Windows Server 2008 R2 (for example). The steps needed for that I will describe here.


First create a new collection in ConfigMgr and choose Membership rules based on direct membership. Click the [blue computer icon] and choose the query explained below. In this case I'm using a Resource class based on System Resource and a Attribute name based on "Operating System Name and Version". Choose "Dynamically add new resources" when using ConfigMgr R3 to automatically add new devices.


Furthermore don't use Collection limiting and select resources needed when displayed. Otherwise the query will not be saved. Then choose Finish, Next (3x) and Finish to save the new collection with query created. To change an existing collection query, choose collection properties, go to Membership Rules, edit the query, choose "Edit Query statement" and Criteria. Then choose edit to change the existing query.

For new Windows releases use the following queries:
  • Windows Vista: Value = %Workstation 6.0%
  • Windows 7: Value = %Workstation 6.1%
  • Windows 8: Value = %Workstation 6.2%
  • Windows Server 2008: Value = %Server 6.0%
  • Windows Server 2008 R2: Value = %Server 6.1%
  • Windows Server 8: Value = %Server 6.2%

That way it's possible to create new collections with support on new Operating Systems. I will add support for new Operating Systems later when available.

2 comments:

  1. There is an easier way of doing this.
    Create a new Collection (e.g. Unused Collections) where you want to place these unused collections in. Select this new unused collection and then create a new subcollection, but use the "Link to Collection" option. Select as a source the old collection in the root. Do this for all the collections that you don't need in you're root. Afterwards, simply delete the collections in the Root. All the "linked" collections in the collection "Unused Collection" will still exists. This method is allot quicker because you don't have to create new queries :)

    ReplyDelete
  2. Hi, that's exactly what I describe in my other blog about "Moving default collections in ConfigMgr 2007" Is that right? http://henkhoogendoorn.blogspot.com/2011/03/move-default-collections-in-configmgr.html

    ReplyDelete