CtsRutland
asked on
Installing Remote Desktop Services on long established server 2008 R2?
This is a naive question I'm afraid - trying to work out if it's worth following up in detail. Will try to be brief.
We have an application on a domain member 2008 R2 server. The *.exe file is on a shared folder, and that is run by several users on their desktop PCs.
One user now wants to work from home. Over a VPN, the program concerned works but is excruciatingly slow in use. I'm not sure precisely why, but some combination of using a slow laptop, VPN latency etc is suspected. The slowest broadband link involved is 3Mb upstream from the office.
My favoured workaround is to get a spare desktop PC in the office that he can RDP into.
It's been suggested that we try Remote Desktop Services on the server (I know we'd need to buy a CAL). I know you are *supposed* to install RDS before the applications, but is it worth a try?
I'm not personally keen on messing about with the server, but could installing RDS break any application on the server for other local network users not using RDS? Or is it a fairly safe experiment to install the role to see what happens?
Thanks!
We have an application on a domain member 2008 R2 server. The *.exe file is on a shared folder, and that is run by several users on their desktop PCs.
One user now wants to work from home. Over a VPN, the program concerned works but is excruciatingly slow in use. I'm not sure precisely why, but some combination of using a slow laptop, VPN latency etc is suspected. The slowest broadband link involved is 3Mb upstream from the office.
My favoured workaround is to get a spare desktop PC in the office that he can RDP into.
It's been suggested that we try Remote Desktop Services on the server (I know we'd need to buy a CAL). I know you are *supposed* to install RDS before the applications, but is it worth a try?
I'm not personally keen on messing about with the server, but could installing RDS break any application on the server for other local network users not using RDS? Or is it a fairly safe experiment to install the role to see what happens?
Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Not one person has suggested that you simply add the user to the allow remote access to test it.
Since Windows 2008 R2 allows two concurrent connections for remote management without installing the RDS role, you could do this to temporarily test the performance.
Because they are REMOTE ADMINISTRATION connections and NOT User Connections.
Further, if you want to test performance over a VPN, if the App is installed on ANY workstation in the office then just remote into that for a test.
And does a remote admin connection utilise the RDP protocol or not? You will notice I said one user not multiple.
I've spent 25 years working with Citrix and RDS so I know the difference between admin mode and multi user mode.
My default answer isn't "buy new licenses" without even knowing if a) there's budget and b) 2016 will support the hardware c) and this one is rather important- the application can be run via RDP.
Would allowing the user to connect via remote admin therefore prove that the application will perform and/or work - or not - via RDP for a single user to test?
2008 R2 also includes virtualisation rights so my next suggestion would be disk2vhd the machine, rebuild with Hyper-v and use the additional license to stand up a server with RDS and the app. the vhd can be used for a second virtual server.
I've spent 25 years working with Citrix and RDS so I know the difference between admin mode and multi user mode.
My default answer isn't "buy new licenses" without even knowing if a) there's budget and b) 2016 will support the hardware c) and this one is rather important- the application can be run via RDP.
Would allowing the user to connect via remote admin therefore prove that the application will perform and/or work - or not - via RDP for a single user to test?
2008 R2 also includes virtualisation rights so my next suggestion would be disk2vhd the machine, rebuild with Hyper-v and use the additional license to stand up a server with RDS and the app. the vhd can be used for a second virtual server.
Remote Administration licensing clearly states for admin purposes only, not for running applications, which is why I suggested testing by accessing a PC. No licensing conflicts and performance would be similar.
Regardless, why configure a server for RDS, set up a licensing server, buy CALs, and risk corrupting an existing user for 1 user? I don't know if still the case but RDS CALs were only available in 5 packs last time I purchased.
Regardless, why configure a server for RDS, set up a licensing server, buy CALs, and risk corrupting an existing user for 1 user? I don't know if still the case but RDS CALs were only available in 5 packs last time I purchased.
Which bit about testing are people missing?
ASKER
Thanks for all the input everyone! It's much appreciated. I am pushing them to replace this server as they are getting old, but I don't hold the purse strings. I think you've persuaded me that it's not worth the risk/hassle of trying RDS. It'd probably be cheaper for them to buy a refurb PC for remote use than it would be to get RDS installed setup and tested too.
Or just an Win 7/10 license for a virtual PC
@Tony why are you pushing for testing by license violation rather than just test to another workstation that almost certainly exists?
@Rob I've had a conversation with Microsoft folks at my distributor (who are SUPPOSED to understand licensing). Unfortunately, a VM for that purpose would be considered VDI which would require Enterprise with SA. While they could have it, they probably don't. Alternatively, they could buy a VDA license, but that's actually a monthly / subscription type thing... long term, it's even more expensive
@Rob I've had a conversation with Microsoft folks at my distributor (who are SUPPOSED to understand licensing). Unfortunately, a VM for that purpose would be considered VDI which would require Enterprise with SA. While they could have it, they probably don't. Alternatively, they could buy a VDA license, but that's actually a monthly / subscription type thing... long term, it's even more expensive
Yes I have really wondered about the "VM thing" and licensing. Hard to get a definitive answer. I have heard different stories, but yours seems to be becoming the common answer. I suspect it was different before Microsoft offered a true VDI solution. Up until a couple of years ago I thought you had to use an FPP license, and if accessing via TS Gateway you needed an RDS CAL, but not so with VPN or local access. I.e if you used something like XPmode or Win 7 Hyper-V you were fine.
Hardware has become very cheap, it's the licensing that costs these days.
Thanks Lee
Hardware has become very cheap, it's the licensing that costs these days.
Thanks Lee
@Lee - because the answer of buy new servers without even knowing if the application would run when accessed via RDP is crazy.
You were advocating just going out and spending money on an untested solution on new hardware and licenses.
I have never suggested that what I said to try would or should be a long term solution but the original question was geared around whether or not the route to take was to add the RDS role to the current server (obviously no being the answer) but even so...but if the OP wants and RDS solution then they need to understand if that application will run via RDP if that's their preferred option.
I would say it's fair the neither you or I first thought to test on a workstation remotely - that was Rob's recommendation so in a way we both missed the mark, but spend money shouldn't be the first option in every case.
You were advocating just going out and spending money on an untested solution on new hardware and licenses.
I have never suggested that what I said to try would or should be a long term solution but the original question was geared around whether or not the route to take was to add the RDS role to the current server (obviously no being the answer) but even so...but if the OP wants and RDS solution then they need to understand if that application will run via RDP if that's their preferred option.
I would say it's fair the neither you or I first thought to test on a workstation remotely - that was Rob's recommendation so in a way we both missed the mark, but spend money shouldn't be the first option in every case.
You were advocating just going out and spending money on an untested solution on new hardware and licenses.
No, I as advocating upgrading a system that is about to go out of support in 18 months. Such an upgrade would result in an extra server license that could be used for this purpose. Any reasonable Pro who cares about security should see this as good advice in my opinion. NO WHERE did I say buy hardware. I advocate hardware reuse in most circumstances, though server hardware was not specifically addressed in this question. AND virtualization. ALWAYS virtualize.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Split:
-- 'Rob Williams' (https:#a42612665)
-- 'Lee W, MVP' (https:#a42612276)
-- 'Rob Williams' (https:#a42612271)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Split:
-- 'Rob Williams' (https:#a42612665)
-- 'Lee W, MVP' (https:#a42612276)
-- 'Rob Williams' (https:#a42612271)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
Not one person has suggested that you simply add the user to the allow remote access to test it.
Since Windows 2008 R2 allows two concurrent connections for remote management without installing the RDS role, you could do this to temporarily test the performance.
Note that this isn't the same as installing the remote desktop role but it would at least temporarily give you that testing.
Right-click Computer -> Properties
Click on Remote Settings
Click the Remote tab (just be aware it may want to turn on the firewall if not already on)
Allow connections
Select users - add your user you want to test
Bear in mind your user will still have to come in via VPN - I wouldn't recommend exposing just RDP to the internet - there are much better ways to do this.
Second, as I've already said - this is only with the intention of allowing you test the application performance. I actually wouldn't recommend installing RDS as a role at this point in its life...but...if it works, there's no reason why you couldn't stand up a desktop and do the same as above.