I have msi file for iisnode, my machine is winx64. I want to install iisnode in preferred location. When I run the msi file it is installed, by default at C:\programFiles
I want to install in different location, because, TFS server will be deploying and replacing artifact inside the iisnode\www. It is not good idea to have replacing contents inside C:programFiles.
I tried msiexec.exe /a yarn-1.10.1.msi TARGETDIR=C:\cygwin64\home but didn't succeed,I have in the pic below (installation package cannot be opened)
If anyone have suceeded in installing msi file in different location when customization doesn't exist will be great, thank you
Firstly, I'm not sure why your screenshot specifies an /a switch for an administrative installation? You want to use /i instead for a normal installation.
Use this command line (/qb for a 'basic' user interface, or change to /qn for a silent installation):
msiexec /i yarn-1.10.1.msi INSTALLDIR=c:\cygwin64\home /qb
Not sure if you are trying to install the app or creating administrative installation?
but the above mentioned error suggests that the yarn-1.10.1.msi is not available in C:\iisnode1 folder. Could you please check that once.
Related
I need to re-create the development environment on my machine, and put exact applications on co-workers machine ( not in same office ).
What We Need Installed
So basically we need a NativeScript development environment created.
This will include programs like, NativeScript CLI, Android Studio, Node, etc.
Ideal Solution
Ideally I would like to write a script that would install the necessary programs without any ( or minimal ) attendance .
Can someone show me how I would create such a script?
Thank you
You can install NodeJS silently by downloading the most recent MSI installer and running msiexec /qn /l* node-log.txt /i node-vX.X.XX-x64.msi. This will install Node and NPM.
Once you've installed NPM, you can install Nativescript with npm install -g nativescript
You can install the Android studio IDE silently with the /S switch, and the SDK silently using /S /Allusers.
You can set the Android_Home environment variable inside HKLM\System\CurrentControlSet\Control\Session Manager\Environment
References:
https://gist.github.com/manuelbieh/4178908
https://www.nativescript.org/blog/installing-nativescript-on-windows
http://www.edugeek.net/forums/windows-7/173153-android-studio-unattended-install.html#post1485712
You can use autoit to create script, code what and in what order need to be installed. Than you can either put all programs version on one usb with your script - in this way you can also controll version of software installed or call to download and install from internet.
You can also include GUI with the script as well as you can create .exe file and end user need just to execute it.
Another option would be to create .bat file and code step by step what need to be installed. Look at batch file command list to see what commands are available.
Those are just two options, possibilities are endless, depend on what you feel most comfortable.
By default, mariadb comes with HeidiSQL, so HeidiSQL is automatically installed when installing Mariadb silently on Windows. https://mariadb.com/kb/en/library/installing-mariadb-msi-packages-on-windows/#silent-installation
There is an option to remove the HeidiSQL if I install with UI, but I am not sure how to do with silent-installation. Can anyone help me to unselct HeidiSQL in silent-installation process?
Thank you
pass following properties to msiexec /i
ADDLOCAL=ALL
REMOVE=HeidiSQL
Example:
msiexec /i mariadb-10.3.9-winx64.msi ADDLOCAL=ALL REMOVE=HeidiSQL /L*V log.LOG /q /passive
HeidiSQL is a normal MSI feature, you do not need transforms or such.
If you have an option to remove something with UI, you can do that also with commandline.
It's pretty straightforward - create a response transform for the GUI installation with HeidiSQL deselected. Then, apply the transform to the existing MSI via the command line.
There are lots of guides on how to create a response transform using different tools; here's some video guide: https://youtu.be/-Thj8rK-Wok
Sorry for the newbie-ish question, but for all my years, I've never dealt with windows installation except as a user and I'm not sure how to start this.
I have two 3rd party packages to install. One I know is msi based but the other I have not found out yet. It comes with a setup.exe and a wrapper.exe - which we use to install.
Both installation prompt the user for language and a number of various options.
I need to wrap or do something to make these unattended installations.
I may be able to get some property information and I've read Silent installation of a MSI package - is that how I go about doing this? There will be a boat load of properties.
Basically, how do I go about wrapping the setup.exe and building / providing some type of response file.
thanks,
jon
Try this procedure to test if the setup is an MSI:
In the folder where your setup.exe is located, hold down shift, and right click in an empty space. Click "Open new command window here".
Type in setup.exe /a and let the setup start. This should launch an "admin install" if the setup.exe is an MSI setup at all. If you see a way to specify a path, define one and press next. This should now extract all files from within the setup.exe exposing the MSI file.
Once you have the MSI file extracted, it can in most cases be installed via a standard msiexec.exe command line like this: msiexec.exe /i setup.msi
To learn how to install an MSI file silently, check this thread:
How to interactive a silently installing msi? (Progress data and cancel it)
Just one final question: are you delivering these setups as a product, or are you trying to install to your work network or similar?
If those wrapper/setup programs don't have a silent mode then the whole process can't be silent. As far as the MSI files are concerned, the msiexec command line stuff is what you need, including specifying properties on the command line, such as TARGETDIR- if the default is wrong, and TRANSFORMS= assuming the language choice is a transform choice. If you turn on Windows Installer logging policy (or the wrappers let you create a verbose log) you'll see what command lines the wrappers use, so duplicate them except you'd add a /qn type of option to make them silent. If they require elevation to admin to install you'd have to launch them from an admin prompt because a silent install won't ask for elevation on UAC systems.
I have been trying to install a msi file using cmd. The command looks like
C:\Windows\system32>msiexec.exe -q -i "Installer.msi"
But every time I run this the window for help options is opened for msi instead of running the installer. What could be the problem?
First, you need to specify the full path to the MSI file. Also, the command line is really picky if you are specifying anything else, and sometimes it doesn't like spaces between value=proprtyname. Those errors will give you the help screen because you got the syntax wrong in some way.
Note that the MSI file will not install successfully in silent mode if it requires elevation. It won't ask for the elevation prompt if you are in silent mode. That means you should try the command line install from an elevated prompt.
I think msiexec.exe /i installer.msi /qn should work.
See here for a similar thread on serverfault: https://serverfault.com/questions/30068/silent-install-of-msi/67001#67001
To deal with the complicated msiexec.exe command line interface, try this free tool from Installation tool developer Altiris: http://www2.wise.com/filelib/WICLB.exe - broken link resurrected from Wayback machine. Seeing as the tool was freeware I assume that is legal.
Please run the download by virustotal.com for safety.
Here is a screenshot:
I want to send my users a package of 3 applications (each of them are an exe file that can be installed) for them to download and install.
These packages are depended to each other so for example to install the second package the first installation file should get installed properly. Is there a way to find out if the windows installer fails during the installation? (By Failure i mean: User cancels the installation - error in installation - driver installation problem or anything that leads to failure of the installation)
You can start the install packages with msiexec and creating a log file:
msiexec /i InstallPackage.msi /log log.txt
In Windows-Installer packages you can use Conditions to check if a package could be installed.