Replacing a Windows 2003 Terminal Server - RemoteApp, RDS, or Run over VPN?
-
Epicor is pretty big about trying to strong arm people into going physical. Their hardware sizing guide recommends it, even after they re-wrote their app in .NET to run faster and more efficiently. I'm running ERP 9 virtual (which we went against them on), and it runs just fine. And ERP 10 will be even leaner, so I am certainly not worried there.
-
@NetworkNerd said:
That does sound pretty attractive. I think it would help those who are less tech savvy. So when users try to print from the application that is via RemoteApp, they see a list of printers on the server rather than the ones installed on their local machine, right? But as long as the proper print drivers are installed on the RDS server, users should theoretically be able to print back to a local printer with no issues.
When you create the Remote App you can choose which, if any, remote resources to allow. I would highly suggest nothing but clipboard.
I just logged in to the Epicor system... They apparently installed Server 2012 + Hyper-V as the base Host and then the Prophet 21 VM is actually Server 2008 R2 running SQL Server 2012. I guess I will have to be "that guy" that pesters them about using such an old OS for the main application.
Anyway, here is a screenshot of the RDS Remote App settings..
-
If a user does get really hosed, then you can always log in to a full RDP session as the user. It has been pretty rare for me at the client with the Dysel accounting system.
-
@NetworkNerd said:
Epicor is pretty big about trying to strong arm people into going physical. Their hardware sizing guide recommends it, even after they re-wrote their app in .NET to run faster and more efficiently. I'm running ERP 9 virtual (which we went against them on), and it runs just fine. And ERP 10 will be even leaner, so I am certainly not worried there.
Yeah look at this config..
-
RemoteApp is an aspect of RDS.
-
-
Yes you need the normal Windows CAL and then a RDS CAL for each RDS user. Epicor charged $115 for it.
You could also get RDS Machine CAL instead. not sure on the pricing of those.
-
@JaredBusch said:
Yes you need the normal Windows CAL and then a RDS CAL for each RDS user. Epicor charged $115 for it.
You could also get RDS Machine CAL instead. not sure on the pricing of those.
I remember Epicor trying to sell us the SQL licenses for 2014 / 2012 to use with their new ERP product, but with the runtime license (or whatever they call it), you get the full SQL but only license to use it for Epicor and nothing else. We have a few custom SQL databases in addition to the one for Epicor and had to get the full version.
But if they can do RDS CALs for cheap we will definitely check it out. My guess is that would mean your RDS server is really only licensed to run Epicor and no other applications, but I do not know.
-
@NetworkNerd said:
But if they can do RDS CALs for cheap we will definitely check it out. My guess is that would mean your RDS server is really only licensed to run Epicor and no other applications, but I do not know.
This all standard Microsoft Open Licensing. I have the admin access to that account, so it is anything we want it to be.
I quoted this against Epicor and lost because they wanted it all in one. Such a pain in the ass simply because the owners do not understand. That IS what they pay us to know. I mean of course, let Epicor set up Prohpet 21, but really I would have liked to setup the server myself and not be stuck with SQL1 and HV1 when there was already XXXXHV01, XXXXDC01, XXXXDC02 on the network....
-
@NetworkNerd My vendor quoted me $106 for the RDS CALS for a bid I recently sent to another potential client.
-
@JaredBusch said:
@NetworkNerd My vendor quoted me $106 for the RDS CALS for a bid I recently sent to another potential client.
Yep - that's essentially what I am seeing in terms of price.
-
@JaredBusch said:
If a user does get really hosed, then you can always log in to a full RDP session as the user. It has been pretty rare for me at the client with the Dysel accounting system.
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.
-
Well, I have a shiny new RDS server built and somewhat working. RD Web Access seems to work fine to get into Epicor. Next I will need to test printing, saving PDFs to mapped drives, and probably look at SSO.
-
@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.
