KACE Product Support

I'd probably create a custom inventory rule for the 64 bit version. Check out here http://www.kace.com/support/kb/index.php?action=artikel&cat=3&id=807&artlang=en

I'd then upload the file to that custom inventory record and deploy it that way. We do that for Mac software all the time.

What ms01ak said.

It also makes writing SQL filters/reports much easier if you include the version and architecture (e.g. "v10.01 x64") in the title of the custom software item.

We've just been using a cmd script that checks to see which OS architecture you are using and then calls the appropriate command line based on the results. This works for us whether we have 2 separate installers for each architecture or one installer with different configurations based on architecture. We're using the output of WMIC to determine the architecture, but assuming that XP is 32 bit because the value we are trying to read does not appear to be available in Windows XP (we only have XP 32-bit and Windows 7 32/64 that we support). It may increase the upload/download size, but it works for us.

Here is a sample of the bit that checks the architecture:


for /f "tokens=2 delims=[]" %%i in ('ver') do (
if "%%i"=="Version 5.1.2600" (
set OS=WinXP
)
)
REM WinXP 32 bit doesn't appear to have the OSArchitecture value in WMI
if "%OS%"=="WinXP" (
set KACE_OS_ARCH=x86
) else (
for /f %%i in ('"%SystemRoot%\System32\wbem\wmic.exe" os get OSArchitecture') do (
if "%%i"=="64-bit" set KACE_OS_ARCH=x64
if "%%i"=="32-bit" set KACE_OS_ARCH=x86
)
)


Just some thoughts to pass along...

We have application(s) as well where there are 32 and 64 bit versions, however, the software shows the same name for both versions in KACE. Our work around is to edit the MSI file with ORCA - specifically the Product table, Property = ProductName.

I change the ProductName's value to something like this: "ApplicationName_ApplicationVersion_ProductArchitecture". = 'AdobeReader_9.4.6_32bit' or 'AdobeReader_9.4.6_64bit'. It will show up in Add/Remove programs as the name you provide in the ProductName's Value filed in the MSI.

Like airwolf stated - this will help with SQL queries and internal reporting as well.


Dave

Thanks Dave. I'm giving that a try. (I used InstEd instead though.)

djz