Remote application installer program

The next thing an administrator wants to do is install it on a remote system. That is the logical next step. To keep these samples cleaner, I am going to use an imaginary installer that is not an MSI but the approach is the same.

I am assuming that you already have PSRemoting working in your environment. If you need help with that, consult the Secrets of PowerShell Remoting ebook. I am also using Invoke-Command in all my examples because that is what you would use in your scripts. If you already have the file on the remote system, we can run it with Invoke-Command. The first detail is that you need to maintain a remote session while the installer is running.

If the installer does not block execution it returns control back to the shell while it executes , your script may finish before the installer finishes. This will cancel the install as it closes the remote session.

You will need to call Start-Process -Wait if you are having that issue. This brings us to our second important detail.

The install needs to be truly silent. Remote sessions are non-interactive. That means that they cannot popup or show windows. This will either cause the program to fail because it cannot show the window or it will cause the installer to hang because it expects someone to click a button that you have no way to click.

Most of the time if you are running installers on a remote system, you have the installer on a network share UNC path.

At first glance, this looks like it should work:. This can be the source of a lot of headaches. Ideally you want to run the installer from a UNC path, but you discover that it does not work. Everything tells you that the file either does not exist or you have no permissions to the file. Do you want to continue? Published packages are displayed on a client computer after you use a Group Policy to remove them.

This situation can occur when a user has installed the program but hasn't used it. When the user first starts the published program, the installation is finished. Group Policy then removes the program. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note Windows Server Group Policy automated-program installation requires client computers that are running Microsoft Windows or a later version.

Important Don't use the Browse button to access the location. Note Because there are several versions of Windows, the following steps may be different on your computer. In this article. The icon file specified in the IconPath parameter resides in this virtual desktop. The virtual desktop must be a member of the collection specified by the CollectionName parameter.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Module: RemoteDesktop. Publishes a RemoteApp program to a Remote Desktop deployment. The acceptable values for this parameter are: Allow. Accepts command-line arguments. Does not accept command-line arguments. Allows only command-line arguments specified in the RequiredCommandLine parameter.

Specifies a name to display to users for the RemoteApp program. Submit and view feedback for This product This page.