I’m currently involved in a project that requires me to build a ConfigMgr 2012 R2 infrastructure from scratch (these are the best ones to be honest).
In this project, the customer requires to have different collections for desktops and laptops for various reasons. All client devices have Windows 8.1 Enterprise installed.
As many ConfigMgr admins, specialists and consultants know, a lot of different ways are possible to populate collections with the right objects. In this scenario, I decided to use the Chassis Types.
I used this website as a reference:
I encountered some funny behavior with the collection for desktops (with the very obvious name All Desktops).
The collection had the following query rule:
After a while I decided to verify if the objects returned are the ones I expected. This wasn’t the case unfortunately. The collection also contained computer objects which were virtual machines running Windows Server 2012. I concluded that a Hyper-V virtual machine also received that Chassis Type (I prefer not to use Chassis Types 1 and 2). The only reason I can come up with is using this chassis type for VDI purposes.
NOTE: I used the script available at http://technet.microsoft.com/en-us/library/ee156537.aspx on a virtual machine running on a ESXi platform to investigate what Chassis Type the script returns. On that platform I received Chassis Type 1 (= other).
Fortunately, a small modification of the Query Statement provided me Desktops only. Since I know that all desktops are equipped with Windows 8.1 I added a rule that checks if a Workstation OS is installed:
After the next update cycle the virtual machines running Windows Server 2012 were no longer a member of this collection.
Hope this helps…