WEB12 – Windows Server 2016 / IIS 10 Upgrade – Incomplete

Tomorrow, Saturday the 14th at 8PM MDT we will be performing the Windows Server 2016 upgrade for this web server farm. We are allocating a 2 hour window for completion of this. This will upgrade the core OS to Windows Server 2016 and upgrades IIS to v10. IIS 10 introduces support for HTTP/2 as well as additional performance improvements for our web server farms.

During this time, all websites and access to FTP as well as SmarterStats will not be available to the WEB12 farm. If you are unsure as to which web server your account is assigned to, you can review the “Services Information” area of the control panel at https://panel.aspnix.com/, the “Web Server” section.


All dates & times are listed as UTC.

Scheduled Date: 
Scheduled Time:
 
Max Outage Duration: 2 Hours


If you have any questions or concerns, please do not hesitate to contact our support department.

Thank you again for choosing ASPnix as your web-hosting provider!

UPDATE #1: – The upgrade is still processing at this time. Is just over half-way completed. We will add additional updates periodically while we wait for the upgrade to complete.

UPDATE #2: – The upgrade is still processing at this time. Is just over half-way completed. We will add additional updates periodically while we wait for the upgrade to complete.

UPDATE #3: – The upgrade is still processing at this time. Is just over half-way completed. We will add additional updates periodically while we wait for the upgrade to complete.

UPDATE #4: – The upgrade is still processing at this time. Is just over two-thirds completed. We will add additional updates periodically while we wait for the upgrade to complete.

UPDATE #4: – The upgrade is still processing at this time. It is nearly completed and is working on final updates. We will add additional updates periodically while we wait for the upgrade to complete.

FINAL UPDATE: The upgrade unfortunately did not complete. We are working with Microsoft to find the root cause. We will create a new blog post once we have determined the cause and fix.