Oh, I misread the post . that's what happens when you skim :) I initially thought the post was referring to using a single task sequence to deploy a 32-bit and 64-bit WIM image, not an application.
Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Wednesday, March 19, 2014 10:35 AM To: [email protected] Subject: RE: [mssms] Task Sequence to install software I would think that is overkill. Just use the built in task sequence conditions? There are a few task sequence variables you could use. ARCHITECTURE SupportsX64 Or just do a condition for the OS? Daniel Ratliff From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Wednesday, March 19, 2014 11:27 AM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] Task Sequence to install software Check out the %PROCESSOR_ARCHITECTURE% environment variable, or you can use PowerShell with WMI: @(Get-WmiObject -Class Win32_Processor)[0].DataWidth; I *think* the %PROCESSOR_ARCHITECTURE% environment variable might be "x86" if you're running a 32-bit boot image on 64-bit hardware. Maybe someone else can confirm? Cheers, Trevor Sullivan From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Wednesday, March 19, 2014 10:23 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] Task Sequence to install software I have a task sequence that installed an application based off of the OS Architecture (x86 or x64). Some how it got whacked and I am trying to recreate it. I have everything except how I determined what the OS architecture is. How does everyone do this? I can't find my notes on how I did this anywhere. I think it was a simple thing, but I am coming up blank on all of my searches as well. Any input would be great! Mike L. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
<<image001.png>>
