This post is to give you heads up on the availability of new installers for Windows Server 2016. The new installers will be available before the end of April.

13 Comments to “Windows 2016 support”

  1. Alexander Hass
    I already asked support several times what issues currently exists... what took so long to get this done? I remember an Adobe policy to support CF on new OS within 3 months after MS releases a new OS.
  2. Aaron Neff
    Hi Rakshith,

    Awesome! Thanks!

  3. Rakshith Naresh
    @Alexander: You are right. It wasn't supposed to take this long. We encountered an issue with our installer SDK and had to follow up with a third party vendor for the fix. We finally received the fix. We will now be working on getting the installers out as soon as possible.

    @Aaron: You are welcome!
  4. Brian S
    We're looking to deploy a CF 2016 instance on a new Windows Server 2016 VM in the near future.
    If the updated installer comes in the next several weeks we should be fine.

    But just in case, what is the current state of CF 2016 on Windows Server 2016?
    Will it simply not install/run at all?

  5. Charlie Arehart
    Brian, the issue is that the CF *installer* (not CF itself) won't work with Windows Server 2016.

    Rakshith said in his comment (on the 13th) that it was issues with getting this installer software to work with Win2k16 that held them up.

    FWIW, this happened with Windows 10 and Server 2012 when they first came out. The issue has typically been that the JVM installed within that installer doesn't work with the new OS, because it has an OS version check that simply doesn't recognize it. Folks COULD work around that be extracting the installer exe (itself a zip), and find and change the config file to point to a JVM that IS supported by the OS. But there could always be other issues about CF support of the new OS that would warrant waiting for Adobe to come out with an official new installer for that OS.
  6. David Simms
    I installed CF 11 onto Windows Server 2016 in January of 2017, and wish I hadn't. Safari, when running on any Apple device, can not receive the default document when the default document is a ColdFusion file, and when the request is made across an HTTPS connection. This does not happen for any other browser (or even Safari running on a PC), and does not happen for non-CF files. Nor does it happen for non-encrypted connections. Adobe support tells me once CF is certified for Windows Server 2016 this will be corrected, but it isn't ready to run on Windows Server 2016 quite yet.
  7. Brian S
    Is this still on track for happening before the end of April (within the next 3 weeks)?

  8. Douglas T
    I am needing this as soon as it is available, so hopefully it will be posted to this forum when it becomes available and I will be notified.
  9. Alex
  10. Rakshith Naresh
    Yes, it is on track for end of April. I will update this post with a comment once it is available.
  11. Anton T
    It is April 21, 2017. Still no Windows Server 2016 support.

    Well, Macromedia did it much much better.
  12. Dave
    T-Minus 6 days...
  13. Andreas
    T-Minus 5 days...

Leave a Comment

Leave this field empty: