#Batch file to install msi install
#Batch file to install msi update

#Batch file to install msi install

A package that performs a nested installation of an application should also uninstall the nested application when the parent product is uninstalled.ДЄlternative 1: ( if you really don't want to configure this within SCCM ( which is the best way) is to create a wrapper exe and install the products seperately.

Resources that are to be advertised cannot be installed by the nested installation.

If none is assigned to it, the batch file will try to find the right MSI file. neroMsiFile none Set this variable to just the file name of the installerвЂ™s MSI file, e.g.

Integrated ProgressBars cannot be used with nested installations. If the bat file is located in the installer folder (which is highly recommended), it is not necessary to change this variableвЂ™s default value.

The installer will not correctly cost a nested installation.

Silently install the msi package and write the installation log to file.

Patching and upgrading will not work with nested installations. Silently install the msi package, no reboot.

An administrative installation cannot contain a nested installation.

It works great so Im trying to do this for the 98 clients but the dsclient for 98 is an msi package and I cant seem to get it to run unless I click on it which defeats the purpose of unattended install.

#Batch file to install msi update

Choose the batch script file and click on the Open button. Ive created a batch file to install patches, delete temp files, update virus definitions and deploy the dsclient.exe file to our NT4 clients. If you want to save the deployment for execution at a later time, add a title in the вЂ Deployment Title вЂ field, and then save the deployment by clicking the double-right. At this point we are ready to execute the deployment. Click on the Open button icon at the top. MSI file is executed, it will be able to find the other files that it needs to complete its work. Downloading BAT to EXE Converter Double-click on the BAT to EXE Converter shortcut to open it. Install the tool by running the installer.

Nested Installations cannot share components. Open your browser and download the BAT to EXE Converter installer.I would not recommend this method ( Nested MSI)

Thank you for your reply.This will all be deployed through SCCM for the most part but I would like to be able to just send a file to a user or a network location if need be (Our SCCM environment is not exactly quick)ДЄfter working on it a bit I came to the conclusion that a chained MSI would be the best way to do this in my environment but I'm having trouble since this package uses msi's and exes, msps (which can't be used in a chained msi at least not that i can tell) as well as some various file copies that need to happen.Д¬an you recommend any further reading on chained MSI's and best practices for using them?