FOG - Single Snappin
-
@msaglioc99 Hint: User the snapin template of MSI, if you are trying to deploy a msi file.
-
@george1421 You would use a snapin verses the snapin packet? Also just upload the installer not the zip file with the installer and batch file?
-
@msaglioc99 A snapin pack would be used if you need to send multiple files to the target computer. But if you are only installing a single msi file then you can send that one directly. NO need to zip anything, just upload your msi and use the msi template.
-
Okay I replicated the screenshots you sent me and I am going to try this. I’ll let you know what happens! Thank You!
-
@msaglioc99 I would use a snapin pack if, for example I needed to deploy a MSI, but then also deploy a preconfigured .INI file with the configurations for the application. So in this example I would create a batch file (like you did) and then include the MSI and the INI in the snapin pack. I would then make fog call the batch file to install the msi and then copy the INI file to the proper location.
-
@msaglioc99 You should find out if that TeamMate_R11.0.2_Desktop file is a .EXE or .MSI file, because the msi template is for .msi files only. The icon you showed us might indicate its a .exe and not a .msi.
-
@george1421 Okay so how can I go about finding this out? What I sent you was by right clicking on the file and then just viewing the properties.
-
@msaglioc99 In windows you need to change your view properties to show you know file extensions. I use a linux laptop so I can’t give you a step by step on how to enable this.
-
Okay I just deployed that file to a target computer using the settings / screenshots you sent me and I was able to see the installer go into the TMP folder and the computer rebooted and said the software was successfully installed but still no software…
-
I believe this file is .exe not .msi
-
The screenshot in the 2nd or 3rd post very clearly indicated that the installer is a .exe. You do not want/need to use the msi template.
Before uploading anything to fog you should be trying to install the application silently on a computer. Try opening a command prompt and typing the filename with /S after it. It’s an InstallShield installer, so if it supports silent installation that will be the switch for it.
-
-
@msaglioc99 Ok, then until you can find a way to install the application silently, uploading it to FOG is useless.
Since it’s an InstallShield installer, you may be able to create a response file. Basically, this records the settings you choose during your installation and lets use that file to silent install the application.
To try this, open a command prompt at the location of your file. Type
TeamMate_R11.0.2_Desktop.exe /rThe installer should appear to run normally. Install the application the way your normally would.
Find the response file. Default location will be
C:\Windows\setup.iss. The modified data on the file should match the time you ran the installer.More directions can be found here:
http://publib.boulder.ibm.com/tividd/td/framework/GC32-0804-00/en_US/HTML/instgu25.htm -
@Avaryan Do I have to runthe installer via command prompt? Or can I just double click and run the installer? Idk how to run the installer via command prompt?
-
If I type
C:\Users\username\Desktop\TeamMate_R11.0.2_Desktop /r the installer does open. Is this what you’re asking?
-
@msaglioc99 Lets do a quick recap here since you are new to package building and it does require a bit of the black arts to make things work well.
Some applications have features to allow software to be installed in an unattended or silent manner. These usually take command line switches to set the installer options. The user is typically not presented with any panels asking questions it is just installed automatically. These are the easiest to be deployed no matter what the deployment tool you’re using.
The other and typically older kind require the installer to click through several panels making option selections sometimes these type of installers can be launched in a admin or configuration mode where they will write the users selections out to a setup file that can be used on the next deployment where you just reference the setup file [setup.iss] for all of the selections. When run this way the user is not presented with any setup panels. The application just installs.
The last kind are the ones that don’t support automated installs in any manner. These type require a different kind of tool that takes a snapshot of a sample computer before you install the software and then just after you install the software. The difference between the two becomes your automated installation package. These tools are expensive and not typically needed now days.
-
{from discussion via IM}
I might assume this might get you pretty close.
-
@msaglioc99 After testing with this application I see its throwing the following error and returned a not successful response to the fog snapin tool
But it looks like it installed something though
-
@george1421 what template and snapin settings did you use to deploy what you were able to install
-
@msaglioc99 None so far, I just wanted to see if the installer ran to completion without any errors. The next step was to deploy via snapin. But since there was an error I stopped.
