Client Management Suite

 View Only
  • 1.  CMS 7.1 Install Application based on OS bit version?

    Posted Apr 04, 2012 08:26 AM

    Hi,

    I have an application that uses two .exe installers, one is 32bit and one is 64bit. I want to be able to use an Applicability rule to run the relevant application based on whether the OS is 32 or 64 bit, can someone advise on this please? I'm trying to prevent creating a policy for each version and publishing them both to the Software Portal.

    Additional info:

    I can detect them as one software procuct but need help with deployment. I use managed software delivery policies, published to the Software Portal. When I add both versions to one managed software delivery policy the applicability rule for the non installed OS version halts the install.

    Hope you can help.

    Regards,

    Paul.



  • 2.  RE: CMS 7.1 Install Application based on OS bit version?

    Posted Apr 04, 2012 09:12 AM

    By the sounds of it, Altiris is tracking the applicibility failure as an install failure (which I guess it is).  A possible fix for that is to select the advanced options for the policy, click the 'results based action' tab, and change 'upon failure' from Abort to Continue.



  • 3.  RE: CMS 7.1 Install Application based on OS bit version?

    Posted Apr 04, 2012 09:49 AM

    You can try something diferent:

    Can you use a vbs or bat script to determine the OS version. So, the script calls the right executable.

    1. Create a script;

    2. Join all executable files and scripts in the same folder

    3. Upload the files to software library

    4. Make the SCRIPT the default installation file

    5. Create the Detection Rules based on MSI code or Executable version

    6. Distribute :)

     

    The con is: You will send two packages for the client.

     



  • 4.  RE: CMS 7.1 Install Application based on OS bit version?

    Posted Apr 04, 2012 10:40 AM

    We do this with a batch file that targets the OS and identifies what version it is based on the existence of C:\Program Files(x86)\ and then run the software off of a UNC path so that both do not need to be copied to the client. A quick check and then send to the right line in the batch file works well:

    if exist %windir%\SysWOW64\cscript.exe (set SCRIPTEXE="%windir%\SysWOW64\cscript.exe") else (set SCRIPTEXE="cscript.exe")

    if exist "C:\Program Files (x86)" (set PROGFILES="C:\Program Files (X86)") else (set PROGFILES="C:\Program Files")

    You can then check the value of PROGFILES or do a goto on the end, whatever you'd like. (The first line is there because if you run vbs scripts, in some cases on 64-bit machines you won't use the right version of cscript.)

     



  • 5.  RE: CMS 7.1 Install Application based on OS bit version?

    Posted Apr 04, 2012 12:52 PM

    but I've had it fail recently too.

    A workaround might be to add OS detection to the Detection Rule. So the detection rule will show as "Detected" for the 32 bit version if it find a 64 bit OS. That way the Policy execution shouldn't halt but go on to the 64 bit version that will be "Not Detected" when it tests for the app and 32 bit OS.