package delivery task - setup.exe with .iss ?

[Iskyfly]

I have tried just about switch combination that I know of. I can get it to work at the PC itself.

SW Resource - "Illiad Clientsetup"
Package;
-Illiad_9.1.3_ClientSetup.exe
-setup.iss

command line for package delivery task;

Illiad_9.1.3_ClientSetup.exe /s

When pushed;
Return Code -3

This command line works in a dos window from the SoftwareDelivery\{xyz}\cache on the PC.

PD works with command line;
Illiad_9.1.3_ClientSetup.exe

How do I get it it pick up on the .iss, please?

Thank you


------------------------------
Giles
------------------------------

[WSH_vly01]

Try Illiad_9.1.3_ClientSetup.exe -s -f1"<FULL PATH TO ISS>"

[Iskyfly]

Thank you WSH_vly01 for your reply.

Unfortunately that did not work. We have tried every combination of things. They all work locally but not when pushed with Altiris.
We have even copied the exe up to file a share and created a batch file to copy it down to the workstation to c:\install (for example) and then used all the iterations of the command line that we could think of to install it but the same problem occurs.

Thank you again!

------------------------------
Giles
------------------------------

[WSH_vly01]

If I use Location on destination computer in the Advance settings, then the install works. 

To troubleshoot the issue, I changed these settings under the Advance settings:
Download Options tab:
-Destination download location
--Symantec Management Agent cache

Run Options tab:
-Check Allow user interaction
--Display window: Normal

I got the message "Unable to read file:<path to file>". Maybe you are experiencing the same thing. Also, do not use any switches or parameters, just set the commandline to execute the .exe file itself.

[Arthur Prosso]

Hello Giles!
You may try to run the task NOT under system account by specifying currently logged in user or specific user.
These are selectable in the advanced options of the task
Regards,
Artur

------------------------------
Software Engineer 5
Broadcom Inc.
------------------------------

[Iskyfly]

Hello Artur,

Thank you for your reply.

When you mentioned;

Try Illiad_9.1.3_ClientSetup.exe -s -f1"<FULL PATH TO ISS>"

what would be the full path, considering this is a package delivery task?
The SW resource package has both the .exe and .iss in it with the .exe being the highlighted / default.

Thank you,
Giles

------------------------------
Giles
------------------------------

[WSH_vly01]

Before I would even worry about the path, change the command line to Illiad_9.1.3_ClientSetup.exe. Then configure the Advanced settings as I listed previously. See if the setup even executes or you get an error.

[Iskyfly]

Thank you for your reply.

Yes the install starts when I am logged in as admin. However, it isnt silent.

EDIT to add- it also starts when "Current logged-on user" is selected. When that is selected, "Task can run: Only when user is logged on" and "Allow user interaction" is checked and "Display windows: Normal" gets selected by default. Obviously I have to be logged in to see if this works.

Some screenshots;

Thank you!

------------------------------
Giles
------------------------------

[WSH_vly01]

So you are not having the same issue as I am. While the setup is opened, you can go into Task Manager > Details tab > Right click the Name column > Click on Select Column > Check Command line > Click OK.

Look at the Command line column and you should see where your exe is executing from. Then you can use that path for you command line.

[Iskyfly]

Thank you for your reply!

PROCMON shows the following;

------------------------------
Giles
------------------------------

[Iskyfly]

------------------------------
Giles
------------------------------

[WSH_vly01]

Try this then:

Illiad_9.1.3_ClientSetup.exe -s -f1"C:\Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery\{40BB63E6-5009-4BB8-93D7-A72C17E427C3}\cache\setup.iss"

If that doesn't work, then I'm out of ideas.

[Iskyfly]

Thank you.

Perhaps the question should be;

Does altiris support deployment of installshield .exe with an .iss answer file?

If so;

Is this a bug with Altiris?



------------------------------
Giles
------------------------------

[Iskyfly]

Thank you.

Unfortunately, same as before.

The .exe starts (I see it pop up in taskbar) but errors out with the same error code as always -3.

------------------------------
Giles
------------------------------

[Martin Sapsed]

I'd say there's a good chance that the path to the altiris cache folder is too complex for the installer to understand, what with spaces and brackets. I'd copy the setup.iss to somewhere simpler first (make a c:\temp for the purpose perhaps?) and then try
-f1c:\temp\setup.iss
I usually put complex install commands in an "install.cmd" batch file and refer to that in Altiris. I've only skimmed over the thread but I presume you've tried all this manually and it's only the loading it into Altiris bit that's causing a problem?
Regards
Martin
P.S. Broadcom: why do you expire the passwords for community members so quickly - I need to change mine nearly every time I come back here!

[Iskyfly]

Thank you for your reply.

Yes have tried the batch file method and with "****" file naming.


batch file copies setup and .iss to c:\install and then

IlliadClientSetup.exe /s

same thing- the exe starts up (I see it in the taskbar) and then quits about 5 seconds later. Altiris returns error code 3.

Bit disappointed with Altiris (the product) on this one.

------------------------------
Giles
------------------------------

[Martin Sapsed]

Hi again,
Sorry - I wasn't clear. Altiris will copy the files down to the cache folder. The batch file would then be something like

MD C:\install
copy setup.iss c:\install
Illiad_9.1.3_ClientSetup.exe -s -f1c:\install\setup.iss

You don't need to move/copy the setup exe as finding that isn't the problem - Altiris knows where that is. From my experience the problem here isn't Altiris, it's the flakiness of installShield installers. Theoretically there's a default in c:\windows or somewhere but I could never get that to work!
Regards
Martin

[Iskyfly]

hello!

well, it all works by command line or bat file when done locally on end user pc.
but obviously that isnt viable.


------------------------------
Giles
------------------------------

[Martin Sapsed]

Sorry - you need to spell it out. What command line? What's in the bat file? What works?
My example above should have had the line

Illiad_9.1.3_ClientSetup.exe /s /f1c:\install\setup.iss

having checked my go-to reference for silent installs at http://unattended.sourceforge.net/installers.php. Note the /'s not -'s. That page includes the comments
"WARNING: Be careful what characters you use in these file names, because InstallShield silently strips certain non-alphanumerics (like hyphens)." - which probably means having brackets in won't work, or quotes perhaps. There's also the comment:
"Oh, one more thing. The /r and /s switches only work if the release engineer is competent." !
If that doesn't work as SYSTEM, you may need to set it to install as a specific user but obviously that user will need admin rights.
Martin

[Martin Sapsed]

The comment about the "release engineer" reminds me that I have seen situations where the generated setup.iss file doesn't contain all the answers that the /s option requires, and results in the UI being displayed. If that's your situation you'll have to make do with /s and live with its defaults. Are you changing any of the options?
Martin

[Iskyfly]

In C:\install\illiad\
-ILLiadClientSetup.exe
-setup.iss

setup.iss

[{02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-DlgOrder]

Dlg0={02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdWelcome-0

Count=6

Dlg1={02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SetupType2-0

Dlg2={02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdAskDestPath-0

Dlg3={02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdComponentTree-0

Dlg4={02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdStartCopy2-0

Dlg5={02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdFinish-0

[{02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdWelcome-0]

Result=1

[{02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SetupType2-0]

Result=303

[{02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdAskDestPath-0]

szDir=C:\Program Files (x86)\ILLiad\

Result=1

[{02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdComponentTree-0]

szDir=C:\Program Files (x86)\ILLiad\

Component-type=string

Component-count=4

Component-0=ILLiadClient

Component-1=StaffManager

Component-2=CustomizationManager

Component-3=SAM

Result=1

[{02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdStartCopy2-0]

Result=1

[{02A0715B-DBC4-40E3-B413-77C5F3FDFB9D}-SdFinish-0]

Result=1

bOpt1=0

bOpt2=0

The .iss was generated by;
IlliadClientSetup.exe /r


If I run this manually at command prompt;

C:\install\ILLiadClientSetup.exe /s /v/qn
It works perfectly.

https://docs.revenera.com/isxhelp19/helplibrary/IHelpSetup_EXECmdLine.htm

Running Setup.exe Silently

If you do not want the Setup.exe file to display a progress bar when it launches, you can use the /s command-line parameter. For example, if you enter the following command-line statement, Setup.exe launches, but the user interface is not displayed:

Setup.exe /s

If you want the .msi setup to run silently as well, you need to pass the /qn command-line parameter through Setup.exe using the /v parameter-for example:

Setup.exe /s /v/qn

------------------------------
Giles
------------------------------

[benjamin.barker]

Illiad_9.1.3_ClientSetup.exe -f1"%CD%\setup.iss" /S /v /qn

?

[cid:image001.png@01D8596C.92E2B260]

Ben Barker
Systems Engineer | Baptist Health System | 3451 Beach Blvd. Jacksonville, Florida 32207

904.202.0686 (w) | 904.477.2705 (c)
[e-mail]

[benjamin.barker]

There’s no need for a batch file if you reference the current path using %CD% .
Illiad_9.1.3_ClientSetup.exe -s -f1"%cd%\setup.iss"

On top of your good tip ( trying to run it with explicit user credentials ), I’ve seen some that will only install if “Allow User Interaction” is unchecked altogether.





[cid:image001.png@01D8596A.A6F9E4F0]

Ben Barker
Systems Engineer | Baptist Health System | 3451 Beach Blvd. Jacksonville, Florida 32207

904.202.0686 (w) | 904.477.2705 (c)
[e-mail]

[Arthur Prosso]

Programmatic way to specify the path is
"%ProgramFiles%\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery\XXX\cache"
where XXX stands for the Guid of the package containing the installable stuff.

Regards
Artur

------------------------------
Software Engineer 5
Broadcom Inc.
------------------------------

[benjamin.barker]

Illiad_9.1.3_ClientSetup.exe -s -f1”%cd%\setup.iss”

Maybe

[cid:image001.png@01D85966.D6833950]

Ben Barker
Systems Engineer | Baptist Health System | 3451 Beach Blvd. Jacksonville, Florida 32207

904.202.0686 (w) | 904.477.2705 (c)
[e-mail]

[Iskyfly]

I'm going to try everyones suggestions (some again) but it will take some time as it involves reverting to vm snapshots on the client pc for each attempt and creating all the different command lines and other options suggested.

Is there anyway I can upload the install somewhere incase anyone wanted to have a go at it? It is 160 MB. It does require authentication when it starts up and a db to connect to so it isnt functional, other than presenting you with a login screen at startup and that is all that is desired.

thank you

------------------------------
Giles
------------------------------

[Iskyfly]

In the "Add or Edit Command Line" for a Package Delivery task;

What is the difference between;
Installation file type: "InstallShield EXE Installation File" and "EXE Software Installation File" ?


Thank you

------------------------------
Giles
------------------------------

[Martin Sapsed]

Installation types - not sure what the difference is except it might offer some intelligence around return codes?
I've just noticed you said that
C:\install\ILLiadClientSetup.exe /s /v/qn
works perfectly. Unless I'm missing something, that isn't using the setup.iss file? Do you change any of the settings when using /r?
The other thought it's provoked is that if you're adding "/v/qn" to pass to an MSI, can you find the MSI and use that directly instead? Perhaps start the install and use PROCEXP to see where it's unpacking the MSI file to and if there are any **** parameters?
As mentioned though I have very occasionally seen software that doesn't agree with being installed as SYSTEM due to the lack of much of a user environment.
Regards
Martin

[Iskyfly]

Thank you for your reply Martin!  Per email conversation between vendor and me they said, and tested, to use /s /v/qn.

I can take the install .exe and the .iss file and put them in the same directory anywhere on c:\ and run the following manually at the command line;
C:\ILLiad_9.1.3_ClientSetup.exe /s /v/qn

It works. I don't know why Altiris can't handle that. I would say the problem is with altiris given that the software installs fine by command line manually on the destination PC. I can't seem to find Altiris documentation on how to syntax an exe install with an .iss.

Email between vendor and me.

George (Atlas Systems)

Feb 4, 2022, 1:58 PM EST

ME
After reading this;
https://support.atlas-sys.com/hc/en-us/articles/360058986953-Silent-Installation

I'm assuming that as long as the setup exe and .iss file are in the same directory than the install command line should be;

 

ILLiad_9.1.3_ClientSetup.exe /s

 

Is that correct?

VENDOR:
Yes, that's correct.

 

ME

Is it possible to do the silent install of illiad such that SQL Atlas Manager doesn't pop up at the end of the install so that it can be configured sometime later?

VENDOR
On the last step of the install there is an option for Launch the SQL Alias Manager.

If you uncheck that box and click Finish it should save your selection to the response file, and the SQL Alias manager won't pop up after the ILLiad install is finished. I just tested this on my VM by creating the response file and then running "C:\ILLiad_9.1.3_ClientSetup.exe /s /v/qn" in command prompt.

Thanks,

George

------------------------------
Giles
------------------------------

[Iskyfly]

Martin (and all)-

I did extract the MSI several weeks and tried to install but got a pop up stating something to the effect that the MSI cant be used to do the install and to use the setup instead. So I axed that idea. However yesterday I imported the MSI into Altiris and selected the altiris predefined "Install for all users with no UI" command line.

msiexec.exe /i "ILLiadClientSetup.msi" /qn ALLUSERS=2

While that worked, obviously the customization i wanted (certain modules to be installed) as defined in the .iss was not done.

As a work around, I made a Job that;
-Installed the MSI.
-Deleted the icon off the desktop for the unwanted modules.
-Reg import of certain registry settings.

Also;

The setup.exe detects? for and installs;
Microsoft SQL Server 2012 Native Client

The MSI doesn't.
 



------------------------------
Giles
------------------------------

[Chris Farrell]

Keep in mind that Altiris is a only a messenger and delivery driver. We deliver the package files and then pass on the command line and credentials to run as (default is to run as the Windows System account, what the agent runs as). If it fails, it is either because the package files didn't arrive, because the command line is incorrect, or the credentials are not sufficient. 

When deliveries do not successfully install or run what was intended, there are only a few places to troubleshoot.
1. Does the package get to the client with all the files intended?
2. Does the command line start (hand's off to the Operating System - at this point it is out of our hands)?
3. Is the command line suitable per the vendor (vendor writes the exe and builds any switches)? In your situation, is the ISS file correct? Testing locally helps here before setting up an Altiris delivery.
4. Does the command session (cmd.exe) open with rights and permissions needed - common issue is you test locally logged in as you, and then leave the default of System (what the agent runs as) in the delivery task/policy, which may not have the rights needed. System as built in is a local administrator with no network rights. 

[Iskyfly]

Thank you for your reply Chris!

Please don't misconstrue my reply as being unappreciative, aggressive or rude. Maybe slightly frustrated. :)

I worked with the vendor back in Feb in determining if their software could be silently installed. They have documentation in the link below. Thus I would assume their software is engineered well enough to do silent installs.

I can take the install .exe and the .iss file and put them in the same directory anywhere on c:\ and run the following manually at the command line;
C:\ILLiad_9.1.3_ClientSetup.exe /s /v/qn

It works. I don't know why Altiris can't handle that. I would say the problem is with altiris given that the software installs fine by command line manually on the destination PC. I can't seem to find Altiris documentation on how to syntax an exe install with an .iss.

Email between vendor and me.

George (Atlas Systems)

Feb 4, 2022, 1:58 PM EST

ME
After reading this;
https://support.atlas-sys.com/hc/en-us/articles/360058986953-Silent-Installation

<o:p></o:p>I'm assuming that as long as the setup exe and .iss file are in the same directory than the install command line should be;

 

ILLiad_9.1.3_ClientSetup.exe /s

 

Is that correct?

VENDOR:
Yes, that's correct.

 

ME

Is it possible to do the silent install of illiad such that SQL Atlas Manager doesn't pop up at the end of the install so that it can be configured sometime later?

VENDOR
On the last step of the install there is an option for Launch the SQL Alias Manager.

If you uncheck that box and click Finish it should save your selection to the response file, and the SQL Alias manager won't pop up after the ILLiad install is finished. I just tested this on my VM by creating the response file and then running "C:\ILLiad_9.1.3_ClientSetup.exe /s /v/qn" in command prompt.

Thanks,

George

------------------------------
Giles
------------------------------

[Chris Farrell]

Hi George - no worries, sounds frustrating for sure!

So I'm assuming the exe looks for the .iss file since it is not specified in the command line?
I would test manually again. Copy the command line from Altiris and paste it directly into the command window when in the SW Delivery folder where it has been downloaded to by the agent. If it succeeds, its not the command line - I have seen cases where a double quote is to blame. There are curly double quotes and those will throw an error as they are interpreted as other characters. 
Also, if it succeeds, put your credentials into the SW delivery to run as you (or whatever account you logged in to the client with when it succeeded.).

All we are doing is opening a CMD.exe process with the rights specified in the task/policy and passing the command line from the SW resource. We don't care about anything else - the fact that there is an .iss file present and involved should not matter. We run the command line in the SW delivery\GUID(PackageID)\cache folder, so as long as all files needed are there its no different than a manual test.

[MATT SWALLOW]

I've done this in the past using VB script-
The account that ran it has admin rights to the server location and was a desktop admin to do the install.

Option Explicit
On Error Resume Next
Dim WshShell, objFSO
Set WshShell = WScript.CreateObject("WScript.Shell")
Set objFSO = CreateObject("Scripting.FileSystemObject")


'**************************************  Copying the Install files locally  *******************************************
objFSO.CopyFile "\\swl_server\altsw_repo\msi_prod\Serena_PVCS_Version_Manager_85\vm8500w32.exe", "c:\desktop_support\", OverwriteExisting
objFSO.CopyFile "\\swl_server\altsw_repo\msi_prod\Serena_PVCS_Version_Manager_85\setup.iss", "c:\desktop_support\", OverwriteExisting

'************************************** Install line *********************************************************************
WSHshell.Run ("c:\desktop_support\vm8500w32.exe /s /v /qn /f1""c:\desktop_support\setup.iss"),1,True

[MATT SWALLOW]

Have you tried the run script option with adding your command line in that worked for you?

[Iskyfly]

Thank you for your reply!

Yes. Unfortunately same behavior and exit / return code (-3).

------------------------------
Giles
------------------------------

[Chris Farrell]

I would try adding InstallShield logging to your command line in Altiris. 

/f2"C:\Setup.log"