I know it was possible for version 7.0 and 7.1. I have not tried it since version 7.5 but I would guess it is still working. And it was exactly working the way you would expect it. You can run the SIM in "recording" mode which then generates an xml file which you can then use for the silent install.
The recording works like this:
1. Run SIM using the command line switch /configfile <filepath> /generate
2. Complete all of the necessary fields in the SIM UI
3. When you get to the “Begin Install” screen, cancel the wizard and close SIM.
The silent installation works like this:
1. Run SIM using the command line switch /configfile <filepath> /qb
You might even want to run the installation of the SIM silent:
- symantec_sim_7_1.exe /q /l*v c:\temp\sim.log INSTALLDIR="D:\Program Files\Altiris\Symantec Installation Manager\" ACTION=INSTALL CLIENTUILEVEL=2
##################################################################################
This the summary here below you can read the full extract which I have once received from Symantec:
Installing Symantec Installation Manager 7.0 (SIM) from a Command Line
Automated installation of SIM 7.0, Platform and Solution(s)
requirements:
1. .NET Framework 3.5 is installed
2. Windows Installer 3.1 is installed
3. ASP.NET script maps are properly configured (run c:\windows\microsoft.net\framework\v2.0.50727\aspnet_regiis -i)
TipIn order to run a silent installation of SIM 7.0, you must meet these requirements.
Installing SIM 7.0 from a command line prior to automated installation
Launch the installation of SIM by executing the installer executable Symantec_SIM_7_0.exe. You may use any of the available MSI switches to run it silently. Valid MSI command options are /qn (to perform a silent installation) and /qb (for installations with limited UI).
Tip -- Symantec_SIM_7_0.exe accepts any valid MSI command options.
Execute Msiexec /? for a list of all command options.
If you want to enable logging use the switch /lv (e.g. Symantec_SIM_7_0.exe /qn /lv c:\aim.log).
Also, the standard public MSI properties exist.
For example, if you want to change the default installation path or set any custom MSI property, you can use the Msiexec command line options to set the neccesary property INSTALLDIR: Setting Public Properties is performed by specifying the command [PROPERTY=PropertyValue](e.g.[INSTALLDIR="c:\Altiris\"]). UPDATEIn versions prior to SIM 7.0.408, silent installation of SIM itself is only supported on an initial install. The SIM installation will be skipped and SIM will automatically launch the SIM UI if SIM is already installed. Support has been added to SIM 7.0.409 and later builds to ensure that the SIM installer will remain silent with the /qn switch regardless of whether SIM is already installed. This should make authoring automation scripts easier.
Running SIM 7.0 with command line options for silent installation of the Symantec Platform and Products/Solutions
In order to run a Symantec Installation Manager command line (automated) installation, you should use the executable with the command options /configfile <filepath> /q OR /configfile <filepath> /qb., where <filepath> is the path to an xml configuration file that contains information necessary to perform the automation (See Creating Symantec Installation Manager (SIM 7.0) automation configuration files section below).
Using the option /q will run with NO prompts (and will terminate the process automatically if any prompts are necessary or exceptions are encountered), and using /qb will display any UI prompts if any are required during the process to allow the user to interact in order to continue.
Important! There are two executable files in the installation directory: SymantecInstallationManager.exe and SymantecInstallationManager.com. The first file is the Windows application for SIM. The second file is a special console wrapper that runs SIM and should be used in any automation script to ensure that the console does not return control to the calling process until the SIM automation process is complete.
The SymantecInstallationManager.com process (when running silently with /q or /qb) will return a 0 if SIM runs successfully, or a value > 0 if terminates prematurely because of an error or cancellation. The process will always return 0 if run with UI.
Tip SymantecInstallationManager.exe may still be used for automation, but since it is a WinForms application, execution of this application at the command line will return control immediately and automation can be more difficult. It is highly recommended that automation scripts use SymantecInstallationManager.com Console application instead. UPDATEIn versions prior to SIM 7.0.408, if a newer version of SIM is specified or available in your product listing, SIM automation will fail until SIM is upgraded to the newer version. This requires launching SIM with UI and stepping through the SIM upgrade process and allowing it to update. Support has been added to SIM 7.0.409 and later builds to ensure that SIM can automatically upgrade itself during the automation process if it is necessary using SymantecInstallationManager.com, without disrupting the automation installation. SIM will be able to automatically update itself and continue with the installation process.
SIM Configuration Xml File
The configuration file that drives the automation of SIM is an Xml file that contains the parameters necessary to perform an installation.
Auto Generating SIM 7.0 automation configuration files with SIM
SIM is able to generate the config file that is required for automating an installation, package creation, repairs, or uninstallations. The generated configuration file gets populated with selected options when going through the SIM UI. The config file can then be used later as you install through the command line.
1. Run SIM using the command line switch /configfile <filepath> /generate
2. Complete all of the necessary fields in the SIM UI
3. When you get to the “Begin Install” screen, cancel the wizard and close SIM.
After completing these steps, a fully commented, populated xml file containing the product(s) that you selected will be created at the filepath you specified. You can then use the config file to run an automated installation.
The comments in the xml explain how you can modify the file to perform an Installation, Package Creation, Repair or Uninstall, and also include details for each parameter specified to help you understand what each of the various options are and what can be modified to suit your automation.
TipThere are some xml items that won’t get generated if SIM has never been configured to use them or has never prompted a user for them (i.e., proxy configuration information and credentials and repository credentials). TipIf possible, it is recommended that you generate the configuration file in the same environment that you will be conducting automation in to ensure you have included all of the necessary configuration information for your environment. Once you are familiar with how to modify the configuration xml, it may not be as critical.
Executing a silent SIM 7.0 automation using a batch file:
A very basic example of what to include in a batch file (e.g SIM.bat):
C:\Symantec_SIM_7_0.exe /qn
C:\Program Files\Altiris\Symantec Installation Manager\SymantecInstallationManager.com /configfile <pathofxmlfile> /q
This example would execute the SIM installation silently, and then immediately launch the SIM automation operation after SIM is installed according to the configuration file specified.
UPDATEIn versions prior to SIM 7.0.408, silent installation of SIM itself is only supported on an initial install. The SIM installation will be skipped and SIM will automatically launch the SIM UI if SIM is already installed. Support has been added to SIM 7.0.409 and later builds to ensure that the SIM installer will remain silent with the /qn switch regardless of whether SIM is already installed. This should make authoring automation scripts easier.
Execution of SIM 7.0 command line automation prior to version 7.0.400:
The SIM command line options have changed extensively in versions 7.0.400 and later. Earlier versions have similarities, but do not include all of the functionality mentioned above.
TipIt is HIGHLY RECOMMENDED that you use a version of SIM (7.0.401 and later) that includes these new features to simplify your automation experience.
The required prerequisites to ensure your automation runs silently will still apply to earlier versions of SIM.
Some key differences:
SIM 7.0.3xx does not have the /generate, /q or /qb command line switches. You should only specify /configfile <filepath> if you are performing an automation.
SIM 7.0.3xx cannot generate configuration files. You must create a specifically formatted xml file to automate SIM. An example can be found at http://ali-mydev.altiris.com/wiki/content/upload/files/SIMcli.xml
SIM 7.0.3xx configuration files are incompatible with SIM 7.0.4xx configuration files. They are very similar, but have slight differences and are not interchangeable.
SIM 7.0.3xx (configuration file) requires that you specify dependencies explicitly in order to launch an install successfully (SIM 7.0.400 and later will automatically select latest dependencies for you).
SIM 7.0.3xx may display UI prompts at any point during the installation process.
SIM 7.0.3xx does not include the console entry "SymantecInstallationManager.com". You must use SymantecInstallationManager.exe.
SIM 7.0.3xx does not return any return codes(related to the previously mentioned limitation).
SIM 7.0.3xx automation typically requires that the calling process provide a loop to watch the SymantecInstallationManager.exe process for completion.
An example of how to execute an automation of SIM 7.0.3xx:
C:\Symantec_SIM_7_0.exe /qn
C:\Program Files\Altiris\Symantec Installation Manager\SymantecInstallationManager.com /configfile <pathofxmlfile>