@scottalanmiller said in Making an RDP Terminal Server with Ubuntu Linux:

I recommend the Remmina RDP client tool, it's the bomb.

I love Remmina as a client.

@ilyas said in Reset 120 Day Grace Period for Windows RDS Server with PowerShell:

@scottalanmiller

Hi, Thanks for wonderful script that save my time.
Could You please guide me how we can run this script on multiple servers?

I tried foreach PowerShell method but it does not work.

From the ISE, load the script and then enter-pssession for each system. Once connected, run the script from the ise. Sorted.

@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.

Only the other night for me and it was all on one project so I'm not sure what it was, yet.

@wirestyle22 said:

Sorry for the lack of information. I'm currently researching LAN-less technology and was looking at thin clients just for funsies. We would be using ZT already and I was just wondering if thin clients would even work over the WAN. This is something I would possibly implement. We used to have them on mobile carts at the hospital I used to work at (LAN based). Bear with me here. I came in to get my cup of coffee today and someone didn't re-fill the Keurig so my life is meaningless for the next five minutes.

Well thin clients are used over a WAN all the time. Think about any time you RDP into a remote server. Remember a WAN isn't a different technology from a LAN, the devices can't tell them apart. It's all just the same TCP/IP network to the devices.

And when you use ZT, there isn't a WAN, it's all LAN.

We run E10.0.700.3 at the moment (1 Server 2012 VM that runs SQL 2012, 1 Server 2012 VM that runs the E10 appserver, and 1 Server 2012 VM that runs RemoteApp for the E10 client - all on the same ESXi host) and will likely move to E10.1 in the next few months. We actually found that at sites with low internet bandwidth, RemoteApp is a little slower than when the client is installed locally. One site running a T1 told us that, and we confirmed it to be the case. It may have had to do with the nice metro interface in E10. The sites with 35/5 coax or 10/10 fiber seem to run RemoteApp about the same as installing the client locally.

I actually heard someone say at Epicor Insights 2015 that Epicor 10 ran better when installed locally on client machines connecting over site-to-site VPN. We never really had to test that theory other than at the site with a T1 that I mention here.

Just an FYI... These instructions also still work on Mint 18 as well.

@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.

how do they compare to the Ubiquiti?

@alexntg that's how I always understood it.