Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Quick Tip Corner: Running Windows Installers on Windows Server

DZone's Guide to

Quick Tip Corner: Running Windows Installers on Windows Server

When installers don't do their job, it can be a frustrating experience to troubleshoot, especially on Windows. Read on to find out one solution to a particular installation problem.

· Integration Zone ·
Free Resource

The Future of Enterprise Integration: Learn how organizations are re-architecting their integration strategy with data-driven app integration for true digital transformation.

I recently came across this particular scenario whilst attempting to install a driver package on Windows Server 2008 R2 and figured that others might have run into a similar situation.

The Problem

While logged into an account on Windows Server 2008 R2 that had administrator privileges, I needed to install a package bundled in the traditional MSI format. Double-clicking on the file, nothing happened.

Going into a shell (even with administrative privileges), I tried running the .msi file from there. The same thing happened but with the message, "Access is denied".

Thinking back to days past when I used the Windows shell more exclusively, I recalled the msiexec command. To be safe, I ran it with the "administrator" switch, i.e. msiexec /a package.msi.

Ah ha! This time, an installer wizard GUI was produced; however, after only one window, the "finished" screen came up. I had been expecting the configuration wizard to carry on at least a couple more steps.

Clicking "Finish" and checking the Event Viewer, the logs indicated that the installer had successfully completed and that the package had been installed.

Nope.

It was simple enough for me to verify that none of the files from the package had been installed.

After trying the same process a few more times to make sure I wasn't imagining things or making a simple mistake, the same result happened each time.

The Solution

After much consternation on my part and several rabbit holes, I found that replacing the administrative switch for msiexec with the installer switch (i.e. "/i") solved my issue: The installer wizard came up and, this time, I was presented with all of the configuration options I was expecting.

Completing the wizard did, in fact, install the files I needed.

Hopefully this saves someone some headaches down the road.

Make your mark on the industry’s leading annual report. Fill out the State of API Integration 2019 Survey and receive $25 to the Cloud Elements store.

Topics:
windows ,windows server ,msi ,installer ,problem ,solution ,tip

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}