WSE RemoteApp 2016 and Windows Server versions (2016/19/22)
Hello Mike,
WSE RemoteApp 2016 seems to be the same product for all Windows Server Standard versions starting with 2016 and going to 2022 and with the same end-of-life for all three Microsoft product.
I want to buy a starter version to test some Oracle-based application: do I need to buy three WSE RemoteApp 2016 licences to carry-on these tests or can I buy one licence, install and test WS2016, uninstall, install and test WS2019, uninstall, install and test WS2022 (yes, I know, it’s only an evaluation version so far ;-)?
Kind regards,
Serge Caron
- Serge Caron asked 4 years ago
- last edited 4 years ago
- You must log in to post comments.
Since Microsoft has now completely abandoned the Windows Server Essentials Experience (WSEE) server role (with Windows Server 2016 being the last “official” version of Windows Server to have the server role available), there will be no more “new” versions of the WSE RemoteApp add-in going forward (i.e. there will never be a “WSE RemoteApp 2019” or “WSE RemoteApp 2022“). However, since the WSEE server role can quite readily be extracted from Windows Server 2016 and installed on Windows Server 2019 and/or Windows Server 2022, I have adapted WSE RemoteApp 2016 to work under those newer versions of Windows Server (with WSEE taken from Windows Server 2016 and installed on 2019 or 2022 via our WSEE Installer). As such, a purchased license of WSE RemoteApp 2016 can indeed be used under Windows Server 2016, 2019 OR 2022.
However, as per our Policy page, your purchased license is valid for use on a single server only. While you are free to move the license to a new/different server once in a 21-day period, you cannot randomly move it between the three different server versions for “testing” purposes (unless you wait at least 21-days between moving the license that is). The only way for you to do that would be to run a 21-day “evaluation” of the add-in on each of the different server versions in order for you to decide which one you’d like to use. Unfortunately, not all of the add-in’s features are available while it is running in evaluation mode though (and the only way to get around that would be to purchase three completely separate licenses I’m afraid).
That being said… Since the core WSEE is taken from 2016, your “Essentials” experience would be nearly identical under each different version of the OS.
- Mike answered 4 years ago
- last edited 4 years ago
- You must log in to post comments.
Hello Mike,
As pointed out, the idea is to test some Oracle-based application. I understand perfectly that WSEE stays the same across all three server versions. It is the Oracle-based application that will be under test.
In order to carry on with these tests, I must install and test under 2016 and wait for the 21 days delay if my tests are not completed by then. After, I can repeat this process for the 2019 version, and again for the 2022 version. So I am looking at a 2 months testing period altogether.
Of course, I can elect to buy more than one licence. Can I migrate a three users licence to a larger number of users, if we decide to go ahead with your product?
Kind regards,
Serge Caron
- Serge Caron answered 4 years ago
- last edited 4 years ago
- You must log in to post comments.
The only features that won’t be available during the 21-day evaluation period are the RADC web feed and multiple simultaneous connections features. Therefore, you should be able to adequately test your Oracle-based application during the 21-day evaluation period in my opinion.
Other than that, we do offer a 30-day no-questions-asked refund policy and so you could always purchase three licenses and then request a refund on two of them as long as you do so before the 30-day refund window expires. That being said, I’d also be happy to entertain your suggestion of applying the cost of the three purchased licenses towards the cost of a single higher edition license (with a greater number of users) if that’s the route that you’d prefer to go.
- Mike answered 4 years ago
- You must log in to post comments.
