It has furthermore been put to Medium in the policy Progressive Compression Level, as was indicated in the guidelines for ThinWire Plus.
This is done by implementing the following registry key: This forces you to use each session to ThinWire, even where the lines have enough bandwidth and the Super Codec can be used. A moment of choice, because to do so we had to turn off the Super Codec in its entirety for the server for all users that are on there. This would again reduce the bandwidth to a level which previously Windows 2008R2 was feasible.Īfter installing the beta on the test servers turned out that we had to force the server to choose the compatibility mode. The 35 kbit / s never seemed to be achievable.Īfter some phone calls with Citrix Project Snowball, we decided to embrace a project that focused on optimizing ThinWire within the ICA protocol and what we call since Feature Pack 3 now ThinWire Plus. On average, we came out of around 170 kbit / s. We had the h264 (Super Codec) compression already disabled because it caused a lot of high bandwidth and a lot of optimization applied in the policies, but we did not get the line under the 150kbit / s. The narrowest lines were 256kbit and there were about seven session running over, which equates to approximately 35 kbit / s per session. Unfortunately, this client had a number of low bandwidth locations. without tuning halfway this year we were at one of our customers engaged in a deployment of XenApp 7.6 Windows 2012 R2.
This was evident at the ICA protocol, which was heavily optimized for GDI and triggering a higher bandwidth in Windows 2012R2.ġ. Since Windows 2012R2, Microsoft make more use of DirectX for the graphic design of the desktop, where they previously used GDI / GDI + API calls. What I read and was delighted by is the google translated version below: You can read the original article by Patrick here (if you know Dutch!): Unfortunately (if you aren’t Dutch) it is written in Dutch so I had to pop it through google translate (which did an amazing job). In particular it’s a good read because it contains really specific detailed information on the configuration and bandwidth levels achieved per session (<30kbps). I was delighted to read a detailed review by a Dutch consultant ( Patrick Kaak) who has been using this at a real customer deployment. During its development and various private and public tech previews this feature has been known as Project Snowball/Thinwire Plus/Thinwire+/Enhanced Compatibility mode but in the documentation it is now “Thinwire Compatibility Mode” ( read the documentation – here). My colleague, Muhammad, blogged a few weeks ago about a new optimised graphics mode that seems to be delighting users with significant ICA protocol innovations, particularly those users with constrained bandwidth ( read the details – here).
0 kommentar(er)
