I have finished testing but have not found any issues. Now looking for a good reason to migrate...anyone?

I don't see why not..

I have done a lot of testing and comparing. I cannot see a reason to upgrade or migrate to 2019. It feels slower and there is hardly a difference in functionality. The only nice new feature (?) in IIS is some setting that allows you to enable HTST but we can do that already using URL Rewriter module.

I was looking for TLS 1.3 support but is still not included in 2019

(Not a reply, but a question.)
Looking to find out what is the latest version of Sever&SQL DNN 9.5+ can Run on?
The official(?) sheet has Server 2016. But from this post it looks like Mariette was successful with 2019.
I need my network team to spin up a new server for me and would like to go as far as possible.
Thanks, CD

I recently upgraded to Windows Server 2019 (but kept SQL Server 2014) without problems. Although there seems to be an issue when recycling the IIS apppool, causing the DNN website to hang for several seconds and returning 503 errors to the users. But I'm quite sure it's not DNN related. When migrating to Win2019 we went from one Win2008 server to splitting web server and database into 2 virtual servers. So there's a lot of other potential causes of this issue.

Regarding the question of WHY to upgrade. It depends on which version you are upgrading from. I went from 2008 on an old server to 2019 on a brand new server. 2008 is not supported anymore, so that's the main reason. I wouldn't bother upgrading from Win2012+ to Win2019 on the same server.

Regarding TLS, HTST, compression etc., you can easily achieve that by using fx. Cloudflare in front of your server.

But a couple of nice new features compared to Windows Server 2008 R2 is: wildcard SSL certificates and support for Docker containers. I'm running Solr (search engine) as a container now instead of installing and maintaning Java etc. on the server.

Hi,

This AppPool problem can propably be solved by enabling preloading. See https://docs.microsoft.co...ation-initialization for more information.

Happy DNNing!
Michael

Thanks Michael,

Maybe it can help. I'll give it a try. However, the same website it worked fine without preloading / "application initialization" before (in IIS 7.5) and I would expect it to work in the same way in IIS10....it should definitely not throw errors like this.

But I'll give it a shot.

Hi,

IIS 7.5 did not support preloading out of the box, so if you haven't installed this module, it would not have worked - or you installed it and didn't change the settings on IIS 10.

Another way to solve this was something I described in a blog some years ago: https://www.dnnsoftware.c...-on-your-web-server. Maybe you had some script like this running on the old server, and did not install it on the new one...

Happy DNNing!
Michael

Wow everyone, great conversation.

For ourselves, don't know why we'd "need" server 2019; other than to delay any server upgrades later.
I'll be sharing this info with the team. Thank you!