2

I'm working on migrating our current terminal server (Windows Server 2008 R2) to a new server with Server 2016. I've installed all the roles on the new server and setup my apps. Works perfectly (almost) through RemoteApp Website. However I can't figure out for the life of me how to create an MSI executable of any of my apps I publish on the Server 2016 terminal server. This was so simple in Server 2008 (see below).

enter image description here

How can I do this in Server 2016? I was able to create one by logging into my Server 2008 TS REMOTE APP MANAGER and connecting to my Server 2016 Terminal server. It created the MSI but it's dicey and when I install the app on a client the icon is "damaged" and corrupted looking.

Is there a better way to make an MSI Executable directly on the Server 2016 terminal server? I plan on decomissioning the old 2008 Server anyway once I have the new Server 2016 up and running.

The whole process for managing terminal services in 2016 seems to have taken a step back and become difficult. At this point I kind of regret purchasing the licenses for it.

2

This feature has not been available since Server 2012. It may be inconvenient, but there are other, possibly better ways to accomplish the same functionality.

See this extended discussion here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/e81e16b0-6e64-4c71-87a9-47a1648224ea/remoteapp-msi-file-publishing-in-win-server-2012?forum=winserverTS

I’ve not found the missing MSI feature to be a roadblock. There is the “RemoteApp and Desktop Connections” feature which is as easy to setup.

  • Wow that is very unfortunate (from my perspective). I always enjoyed pushing out the msi to manage the remote apps. Thanks for the information. I'll look to adapt to this. Thank you! – drpcken Nov 27 '17 at 14:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.