Friday, September 07, 2012 6:50 PM
This might be a silly question but I'm still new to this whole MDT business. I have some webcam software that I want to install a few of our machines when they are imaged. Only 3 out of 10 models that we own have a webcam. In my task sequence I have a separate group for laptop installs. Right now the only programs in the group are the vpn client we use and the webcam software. The gropu fires if the "IsLaptop" variable equals TRUE. My question is, what is the best way to deploy this webcam app to only 3 models? I've tried the following...
Single WMI Condition
Select * from Win32_ComputerSystem where Model like 'MODEL A%' OR Model like 'MODEL B%' OR Model like 'MODEL C%' (I'm still learning the syntax...)
Multiple WMI Conditions
Select * from Win32_ComputerSystem where Model like 'MODEL A%'
Select * from Win32_ComputerSystem where Model like 'MODEL B%'
Select * from Win32_ComputerSystem where Model like 'MODEL C%' (This only seems to process the first query and then moves on...)
I believe the best answer would be to simply create three separate Install Application tasks and move on but I thought I'd ask.
Saturday, September 08, 2012 4:57 AM
You can also create selection profile for each model.In each profile select the respective model and their drivers.
Monday, September 10, 2012 2:26 PM
Either of your queries will work. There is no "best" option. Whatever works is good. Creating a Task Sequence step and restricting it to those 3 models is a great way to tackle this issue.
Monday, September 10, 2012 6:08 PM
Thank you both for your input. The first option, the query with the multiple OR operators fails. It results in a unsuccessful deployment, 12 errors, unable to resolve WMI query. The second option, using three separate wmi queries, works for only the first listed query, Model A in my example above.
As Andrew stated above, there is no "best" option. I went with my original plan, three separate application istall tasks. It has worked flawless since the change.
- Marked As Answer by TK Deployment Monday, September 10, 2012 6:08 PM
Tuesday, September 11, 2012 6:19 PM
I was looking at using this
But I get it to install the application for the driver than it doesn't return back to the task sequence. The cscript process never returns. The logging indicates that ZTIApplication completed successfully and goes back to ZTIInstallDriverExePackage but ZTIInstallDriverExePackage never returns and the task sequence never completes.
Tuesday, September 11, 2012 7:47 PM
I've got some tips on how to cheat at WMI queries on my blog here: http://scriptimus.wordpress.com/2011/06/22/mdt-2010-using-wmi-queries-with-task-sequence-step-conditions/
Might help you merge them back into 1 step as you had hoped.
Wednesday, September 12, 2012 5:38 PM
Your article is what inspired my work around. I was just hoping to avoid having to add a WMI query and Task Sequence step for each of the special drivers.
The WMI Code creator you referenced is very handy for making the queries.
Wednesday, September 12, 2012 7:06 PM
Thanks, Andrew. I'll take a look!