I have different rules for XP and Win7. One is like this select * from win32_systemenclosure where chassistype=9 and others like select * from win32_Operatingsystem where version like "6.%" None work, is there something else I need to enable? I have tried so many times.

I have this same issue and haven't found a solution. I have a software package that I want installed but only on our HP machines. I've triple checked my query and it is correct yet it keeps installing on the Dells as well. If you find a fix please update this post.

if you integrate MDT, and make a toolkit package, like this http://blog.coretech.dk/mip/creating-and-using-toolkit-package/ . then you can run a use toolkit step, and a gather step, and use chassie type like this http://blog.coretech.dk/mip/easy-way-to-install-depending-on-chassis-type-laptop-desktop-or-server/ You can also use MAKE in the same way to get only HP machines! To get most of the MDT variables available you can run ZTIGather.wsf from the scripts folder on your local machine, and look in C:\MININT\SMSOSD\OSDLOGS\ZTIGather.log Michael Petersen http://blog.coretech.dk/mip/

That would work if I wanted to install the package on all HP's. I want the option to be able to do so in the OSD Setup Wizard but only on HP's. As far as I can tell from the documentation what I have should work. On the package in question I have a WMI Delivery Rule. The namespace is root\cimv2 and the query is SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE "%Hewlett-Packard%"

I feel like someone must know the answer to this. Is there anyone out there that does have the WMI Rules working?

This does not work for me either, just to clarify the part of the Task Sequence I am running is for rebuilds and is in WIndows 7 64bit or 32bit and not in WinPE. I have been looking all over the web for a couple of days now as to why. http://andysal.wordpress.com/2010/08/04/udi-getting-started-with-user-driven-installation-in-mdt-2010-update-1-application-configuration/ About half way down there is an explanation of how this works. I have used the following different namespace \.\root\cimv2 : \root\cimv2 : \cimv2 : cimv2 None of which work, the query is correct, I even used SELECT * FROM Win32_ComputerSystem WHERE NAME LIKE 'W%', all workstations here start with W. Which did not work. Anyone got any ideas as to why this is not working? Here are other links to complaints.... http://social.technet.microsoft.com/Forums/en-US/mdt/thread/2b597d2e-e71a-4c2c-9a13-1df1bad1a152/ Here is a screen shot of the part I am talking about Here is a script to test the query works '-------------------------------------------------------- Call Test Wscript.Quit Function Test Set objWMIService = GetObject("winmgmts:\\.\root\cimv2") Set colItems = objWMIService.ExecQuery("select * from Win32_ComputerSystem where Name LIKE 'W%'") For Each objItem in colItems Wscript.Echo objItem.Name Next End Function '--------------------------------------------------------

I have managed to work this out myself and resolve my issue, I thought it best to post the resolution since there is 2000 odd views and people are problably interested. The Mapping & Delivery Rules in the UDI Wizard do not work unless you run Application Discovery at the start of the build in the preflight section. Add this path to your UDI Wizard settings and group. Then add the following step to Preflight, with the followoing command. Sorry about thr resolution of the screenshot. And since I can only psot 2 images per message Ill create another and mark this as a propose as asnwer.

Just like to add as well, that they act as a filter, actually removing the sofwtare from the list if it does not meet the WMI query, so I locked all my software, selected by default and used the WMI filters to remove ones.