@wrcombs - Or drag and drop the PDF file to the local computer and print it locally.

@dbeato said in RDS 2016 Remote App issue:

@dafyre said in RDS 2016 Remote App issue:

@dbeato said in RDS 2016 Remote App issue:

@dafyre said in RDS 2016 Remote App issue:

@dbeato said in RDS 2016 Remote App issue:

I am also leaning to do this:
https://social.technet.microsoft.com/Forums/windows/en-US/96cf9ef3-6ec2-4c7a-9e9f-21aeb6ef794d/remote-desktop-collection-is-missing-properties-i-would-like-to-add?forum=winserverTS

That's essentially why the powershell script does... So you ran the script and you're still not getting correct RDP files from the RD Web site?

yeah, it didn't really work since it is not updating anything on the connection broker. I am going to redo it all...

Curious.

You mean after I finish redoing it?

Just strange that it isn't working. I have Gateway, Web, and Connection Broker on same system here, so that could be part of it.

@Minion-Queen -- Yes, this code is available for anyone to test. It needs to be run from the Connection Broker, for now.

If folks find it useful enough, I may change that.

@NetworkNerd said:

In the case of this application (Epicor), they made some big steps to just take out the Progress layer that was there even if you had a SQL back end. I'll take that for now.

Sounds like some seriously weak software from all descriptions. Have you guys looked at anything from this millennium? You might have your mind blown by how modern software works in this space. Running 90s software for a core function has to be really painful.

@NetworkNerd said:

So do you direct your users to the site where the RemoteApp gets published to use to connect to it, or do you put a shortcut on their desktops for the RemoteApp as well? I'm assuming there is no difference in functionality but don't really know at this point.

I push a shortcut. You cannot trust users to find anything via direction.