Flexibility in Windows Server Version Installations

0

Since your two primary sales products state that the WS 2016, 2019, 2022, or 2025 must specified to order, it’s not clear to me whether they — or the WSEE Installer can be used on one version of WS, then moved to another version.  For example, I’m using WS2012R2, but I want to upgrade to WS 2022 now, since I’ve read too many comments about WS 2025 not being quite ready for prime time. So I plan to specify WS 2022 for my order. However, I’d like to move WSE WorkFolders, and particularly WSEE Installer on over to WS 2025 within a year. Is that acceptable under your licensing and support terms?  Thanks for clarification.

  • You must to post comments.
0

My software products (WSE RemoteApp and WSE WorkFolders) can be used on Windows Server 2016, 2019, 2022, or 2025, and the WSEE Installer can be used on Windows Server 2019, 2022, or 2025. You can switch between using any of those versions of Windows Server as desired. However, since your license is valid for single server use only, you cannot run the software on multiple versions of Windows Server at the same time (i.e., it’s one server install per purchased product). Additionally, in-place upgrades across those different versions of Windows Server are fully supported by the WSEE Installer as well.

That being said… If you are currently running Windows Server 2012 R2 Essentials, then I strongly recommend that you in-place upgrade it to Windows Server 2016 Essentials first (and verify that everything is working) before you then in-place upgrade it on to Windows Server 2022 (or 2025). I talk about doing that over here.

So… The answer to your question is yes.

Lastly, Windows Server 2016 (and hence my software products and the WSEE Installer) will reach end of life on January 12, 2027 (i.e., in about one years time). I plan on retiring at that time and so I (nor my website) will be available going forward from there and so you might want to take that into consideration as well. I haven’t decided what I’m going to do with my software products and the WSEE Installer as of yet, but I’ll most likely release final “sunset” versions of them that my paying customers can continue to use once I’m no longer around (at least until Essentials itself goes kerplunk in the night anyway).

  • You must to post comments.
0

Thanks, Mike. That spelled it out well for me. (When I got to the add-to-cart and pricing page, the note there seemed to conflict with ability to use between the different supported versions — not at same time, of course. “NOTE: Each of our products are licensed specifically to the server operating system for which they were designed to run under. Therefore, you must choose the EXACT operating system that your server is currently running in order to receive a functional license for your product purchase.”)

I appreciate your very honest and appropriate caveat about the EOL for WS 2016 WSEE.  I think it will still be worth it. And I’m even more appreciative of your time and talent in making the WSEE Installer available along with the extensive support you’ve already provided.

In preparation, I’ve already done an in-place upgrade of WS 2012 R2 and its WSE VM to WS 2016. Unfortunately, I’m one of the users that ran into complications:  Windows updates failed, and event logs are chock full of errors, apparently caused by leftovers from the upgrade change. I was able to troubleshoot enough to get all the updates on the host but not on the VM – so far, anyway.  It would be nice to have a script or similar tool that could extract full settings of currently used WSEE and apply them to a clean install of a newer WS.

  • Mick Mickle answered 1 month ago
  • last edited 1 month ago
  • Mike
    Good catch. That statement has been there for many years now and actually referred to the time back when each new Essentials release was specific to the version of Windows Server it was released for (and thus my software products were written specifically for each of those different versions of Essentials). However, since 2016 is the last version of Essentials, and since the WSEE Installer allows you to install the 2016 versions of my software products on Windows Server 2019, 2022, or 2025, you are correct in that the statement doesn’t really make sense any longer. I’d remove, or reword, it but at this point, I’m not sure that it matters any longer. Thank you for your kind words as they are much appreciated.
  • Mike
    As for the script you’ve mentioned… I’m sure it could be done, but unfortunately, this late in the game it’s probably not a productive use of time (sadly). :- (
  • You must to post comments.
Showing 2 results
Your Answer
Post as a guest by filling out the fields below, or you may to post using your existing user account (register to create a user account if you do not already have one). Guest's questions will be moderated before being posted. NOTE: Your email address will not be published, nor will it be used for marketing purposes, etc. (as per our privacy statement).
Name*
E-mail*
Answer Details*
Screenshots
File Name Size
There are currently no files uploaded.
Maximum number of files 4, maximum file size 5MB.
Supported file formats: gif jpeg jpg png

Featured Questions

Recent Questions & Answers

Q&A Toolbox