EPi 9+ with Windows server 2008 r2

Vote:

I'm currently on Epi 8.11 and beacuse of the bug http://world.episerver.com/documentation/Release-Notes/ReleaseNote/?releaseNoteId=CMS-2057 I need to update to the latest version (today 9.6).

I was reading the breaking changes for Epi 9 and came across this:

"Note: System Requirements have changed for CMS 9. Windows Server 2008/2008 R2 and Windows 7 are no longer supported due to missing websocket support."

Of course my clients servers are 2008 r2. What will be the impact on the intranet site if I go ahead and upgrade to Epi 9.6?

#143382

Jan 21, 2016 17:00

Ted

Vote:

Off the top of my head you won't actually miss out on any (current) features. I think there are plans to make use of websockets in the Episerver UI going forward, but to my knowledge there are no such features currently in place.

#143385

Jan 21, 2016 17:35

Richly Chheuy

Vote:

Hi,

The one feature you wouldn't be able to use is the Projects feature which relies on WebSockets support. Otherwise, other current features are available and CMS 9 should work for the most part. It's just that we won't officially support that version of Windows moving forward.

#143386

Jan 21, 2016 18:12

Wacdany R.

Vote:

Hi Richly,

From the looks of it in the Alloy Demo Kit (https://github.com/episerver/AlloyDemoKit) I am guessing that the EPiServer Projects feature uses SignalR (http://www.asp.net/signalr) which provides abstraction over the communication mechanism (websockets, server sent events, ajax long polling, etc).

Websockets being the preferred approach, upgrading to Windows Server 2012 would enable the usage of websockets for better performance in the bi-directional communication. However I think EPiServer Projects might still be able to fallback if Websockets is not supported.

TL;DR: I think EPiServer Projects relies on SignalR, hence it would still be supported on Win 2008 (R2) using a fallback mechanism - instead of websockets -.

A quick test should be able to confirm the dependency.

Regards,

#143514

Jan 26, 2016 3:18

henriknystrom

Vote:

@Wacdany, I'm afraid that your guess in this case is incorrect. The AlloyDemoKit is a demo project created to showcase possibilites with the platform and while it uses SignalR, this has nothing to do with the Projects feature in the CMS platform. The Projects feature uses WebSockets directly which is why Windows Server 2012 is required. The reason for this is that SignalR carries quite a few dependencies with it both on server and client side and uses a initialization model (Katana) that does not match up very well with the framework initialization model in Episerver CMS.

A quick test would indeed be able to confirm the lack of such a dependency ;)

#143515

Jan 26, 2016 4:45

Wacdany R.

Vote:

@Henrik, Thanks for the double confirmation!

#143516

Edited, Jan 26, 2016 4:48

A.D

Vote:

I can live with not having access to certain new features, but could running EPi 9 on win 2008 cause any issues?

Thanks

#145467

Mar 04, 2016 7:26

Arild Henrichsen

Vote:

I'm interested to hear how this went. Upgrading to the newest Episerver.UI (9.4.0), Episerver would throw an error if Websockets was not installed on the server (required by the Projects feature, even when it was not enabled yet by the site admin). See this blog post: http://world.episerver.com/blogs/Eric-Pettersson/Dates/2016/2/fixing-the-websocket-protocol-support-issue-when-upgrading-to-episerver-ui-9-4-0/

So if Windows Server 2008 does not support the installation of Websockets, this could be a showstopper.

Any update on this, Sara?

#145472

Mar 04, 2016 9:52