Changes

Jump to: navigation, search

Identify Client Form Factor

428 bytes added, 22:18, 21 February 2010
no edit summary
It relies on a vbs script which queries WMI to identify the hardware chassis type then writes the returned value to wherever you specify in the Registry.<br>
I have added it to the Registry section which specifies Env Variables so you have the choice to query the variable "CHASSISTYPE" or directly query the registry key in a WPKG check condition.<br>
 
You can use [[Packages.xml#Check_conditions_.2F_check_type | logical conditions]] to determine if an application install package targets a specific platform (laptop or desktop for example). Remember that logical conditions are counter-intuitive, if you want to install an application on a specific platform you check for what your target platform '''isn't'''. <br>
You will then need to use [[Packages.xml#Check_conditions_.2F_check_type | logical conditions]] to determine if an application install package targets a specific platform (laptop or desktop for example). Remember that logical conditions are counter-intuitive, if you want to install an application on a specific platform you check for what your target platform '''isn't'''. <br>
For example:<br>
<source lang="xml">
</check>
</source>
<br>
Alternatively you can use an '''if''' statement in your install command to only install if the appropriate chassis type is detected, e.g.
<source lang="xml"><install cmd='%COMSPEC% /c if "%CHASSISTYPE%"=="Laptop" msiexec /qn /i ...</source>
Of course be sure to modify the xml and vbs below to your needs.<br>
41
edits

Navigation menu