I am having an issue deploying Agfa IMPAX 6.3.1.4527 via Altiris Software Delivery Solution.

I have a working package/command line installation that runs when logged into the system. However, when deploying via Altiris the installation isn't successful for all users. I have run as the default System Account, a local admin and a domain admin. I get the same results. The funny thing is, the installation does happen and there is an application installed in C:\Program Files\Agfa\IMPAX Client. I can also run the application from this folder.

The problem is that no desktop or start menu icons are created and the uninstall doesn't function. It does write the regiestry key to the following path, but the uninstall fails saying that the application isn't installed. This could be an issue troubleshooting and removing the application later.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AF4FCC6E-88E8-4541-9CC2-254B8195BCD2}

My backup plan would be to deploy the application and add the shortcuts via a vb script, but I don't like that I don't have an ability to uninstall the application.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Looking in the verbose log which you, of course, specified on the command line for the install, what value does ALLUSERS have? Do the user and All Users profile folders resolve correctly?
Answered 10/20/2009 by: VBScab
Red Belt

Please log in to comment
0
1) Before deploying through sms, you can check behaviour of your application, by installing through system account. That will be easier for you to troubleshoot. copy below code and save it as a bat file. Then doubleclick on that bat file, you will get a yellow command prompt window. put your commandline in this window.
2) compare your source installation and your package installation through any snapshot tool


@echo off

sc create CmdAsSystem type= own type= interact binPath= "cmd /c start cmd /k (cd c:\ ^& color ec ^& title ***** SYSTEM *****)"

net start CmdAsSystem

sc delete CmdAsSystem

Answered 10/20/2009 by: abking99
Second Degree Blue Belt

Please log in to comment
0
It is wrapped in an
It is wrapped in an InstallShield exe.

I am running the following command line:

ImpaxClientSetup.exe /S /v"APPSERVER=servername.domain.ca ALLUSERS=1 AUTHENTICATION_TYPE=1 /qb /l*e "C:\Source\IMPAX.log""

When I review the install log file, it isn't showing any error. It does show that it is getting ALLUSERS=0 even though I have given it a different value.

If I manually run the command line on the workstation, it installs correctely. It seems that the install doesn't seem to accept that it is installing as an Admin.
Answered 10/20/2009 by: stkikker
Senior Yellow Belt

Please log in to comment
0
Is there any setproperty custom action, in msi? which changes allusers property?
Answered 10/21/2009 by: abking99
Second Degree Blue Belt

Please log in to comment
0
Don't make me do it...don't...you won't like it... http://www.lmg.....

Anyway, why use a CA when you can just add it to the 'Property' table? Or specify it on the command line?
Answered 10/21/2009 by: VBScab
Red Belt

Please log in to comment
0
I think the whole point is that it doesn't work via property table/command line:

ORIGINAL: stkikker
I am running the following command line:

ImpaxClientSetup.exe /S /v"APPSERVER=servername.domain.ca ALLUSERS=1 AUTHENTICATION_TYPE=1 /qb /l*e "C:\Source\IMPAX.log""

When I review the install log file, it isn't showing any error. It does show that it is getting ALLUSERS=0 even though I have given it a different value.
Answered 10/21/2009 by: Rheuvel
Brown Belt

Please log in to comment
0
Since the '/V' argument indicates that an MSI is being run, why bother with the complication of the EXE getting in the way? Extract the MSI, create a transform, add the ALLUSERS property and assign it the value '1'. Then use the MSI/MST for deployment.

Before that, though, remember to test that your package exactly duplicates the vendor install by renaming the ProductCode key in the Uninstall registry branch (so that the engine thinks the product is not installed), run a lightweight snapshot tool and take a 'Before' snapshot, then run the vendor install followed by an 'After' snapshot. Add any relevant changes to your transform.
Answered 10/21/2009 by: VBScab
Red Belt

Please log in to comment
0
It can be possible that, in some vendor msi, property table has different value, and through custom action, it sets different ALLUSERS value. So I asked him to check, is there any similar kind of scenario? I did not ask him to use custom action, to set property, and one thing I missed, that is..if he is passing allusers value through commandline then that value will be taken.
Answered 10/21/2009 by: abking99
Second Degree Blue Belt

Please log in to comment
0
I had issues with this app as well, where a wise package/batch file/hand install would work perfectly fine (and for all users), but anything installed by remote delivery tools like BigFix or SMS would not, despite using the above and /or exactly the commands on their installation manual ! 

I ended up extracting the MSI instead, and using that:  msiexec.exe /i "c:\Test\agfa impax client.msi" APPSERVER=xxx.radiology.x.edu ALLUSERS=1 /qn  and it worked fine !  (insert other settings as desired) - the manual recommends /Quiet but /qn worked better. 

Same in SMS except for a relative path for the msi location (your distribution point)... prior to doing that we could see in the logs that running the EXE was failing with weird messages related to access rights. I don't understand why, other reported parameters not passing properly from exe to msi, but use the MSI and it will work ! (you can find it when doing the exe install under users\appdata\local\downloaded installations )
Answered 01/22/2016 by: Deschodt
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity