Citrix Web Interface 5.4 – Why You Need To Upgrade

Last week Citrix announced a Cross-Site Scripting Vulnerability in Citrix Web Interface 5.x. It’s highly recommended that you upgrade to the newest Citrix Web Interface 5.4 that fixes this issue and also give you the new facelift. After the release of the previous Web Interface 5.x in black a lot of people have been spending much time on adding the white template and customizing it.

I would highly recommend you to take a look at my previous post “How to Load Balance Citrix Web Interface with NLB” since your Web Interface Server is probably one of your single point of failures. The nice thing with the release of Citrix Access Gateway is the possibility to use your internal Citrix Web Interface, which means you will have an Load Balanced Web Interface cluster for both internal and external access.

Be aware that some people have problems installing Citrix Web Interface 5.4 on a domain controller (Citrix Support Forum). I haven’t had time to take a closer look at this error message, but I confirmed it when I installing it in my RackSpace Lab.

Update 23/10/2011 – Citrix now states that they don’t support installing Citrix Web Interface 5.4 on a domain controller, actually they’ve never supported this even tough it worked before.

How hard would it be for Citrix to create a framework that people around the world could use to create their own look and feel, similar to the themes we have with WordPress blogs? In the comments section below tell me what you think.

Resource :

12 Responses to Citrix Web Interface 5.4 – Why You Need To Upgrade

  1. Problem with this version is that it is a departure from the 5.3 version, skin wise. We used the 5.0-5.3 format and arbitrary changes to the WI by the Citrix team cannot be expected to be deployed. Look and feel changes MUST be vetted by management. Say upgrade to 5.4 to fix the cross-site scripting problem is BS, they need to release a HF for the prior 5.3-5.1 versions. 5.4 is too much of a visual change for many to implement. Not to mention change control requirements, etc. A security HF needs to be released in situations like this, not a new version.

  2. +1 on Mark’s comment.

    Organisations that are currently rolling out Web Interface 5.3 in production cannot switch easily to 5.4 with such design changes !

    For lots of customers I’d say it’s now too close to production to stop the project because of a new Web Interface release.

    Also, almost all my customers do have a customized Web Interface and it’ll take time to adapt these customizations to 5.4 (morever with the new look !).

    I really agree on the point stating that Citrix has to patch older releases and can’t only say upgrade to 5.4.

    • I agree with Mark and Pierre. This update is a pain for company’s with strict Change Management. For those of you looking for the White Themes for Citrix Web Interface 5.3 it can be found on here.

  3. Hello Eric,

    I think Citrix is doing the right thing. They change the CI of all their products to look like one software. It is also possible to change the background and structure via css. Citrix has the problem, that they use the aspx surface and a old version of html. Citrix architects should install the WI 5.4 at their test environment to get use of it.

    I agree with Mark and Pierre, but Citrix has to do this step to move forward and use the functions of their Citrix Clients.

    Regards,
    Frank

  4. Dear Frank,

    I agree with you BUT when a company is becoming a strategic infrastructure layer (like Citrix is) you have to follow strict change rules when your updates are impacting user experience.

    If you do not, I’d expect companies like MSFT to change the Windows GINA with every service pack !!!

    Imagine what it could lead to …

  5. I totally agree with Mark, the design and interface change is the biggest challenge in a change controlled environment.

    I believe we also face another problem. Using Netscaler/access gateway enterprise, the interface is still 5.x. So you get a mismatch there if Citrix doesn’t soon supply a new firmware with a 5.4 changed interface. Until then, external web interfaces will have to stay on 5.3.

    The only way around the vulnerability, is that Citrix should release a patch for 5.3.

    Henrik

  6. Problem with this version is that it is a departure from the 5.3 version, skin wise. We used the 5.0-5.3 format and arbitrary changes to the WI by the Citrix team cannot be expected to be deployed. Look and feel changes MUST be vetted by management. Say upgrade to 5.4 to fix the cross-site scripting problem is BS, they need to release a HF for the prior 5.3-5.1 versions. 5.4 is too much of a visual change for many to implement. Not to mention change control requirements, etc. A security HF needs to be released in situations like this, not a new version.

  7. I think there’s a problem with any change management initiative that makes it harder to adapt to industry changes. Nonetheless, while it may be easier for us IT folks to adapt to change, it is not so for most users.

    I think Citrix should be more mindful of these objections and give people oppotunity to update their environment rather than change the look and feel–look and feel should be an optional enhancement not a requirement.

  8. Last week Citrix announced a Cross-Site Scripting Vulnerability in Citrix Web Interface 5.x. It

  9. I think Citrix is doing the proper factor. they modify the CI of all their merchandise to appear like one software package. it’s conjointly doable to vary the background and structure via css. Citrix has the matter, that they use the aspx surface and a recent version of hypertext mark-up language. Citrix architects ought to install the American state five.4 at their check atmosphere to induce use of it.

    I believe Mark and Pierre, however Citrix must do that step to maneuver forward and use the functions of their Citrix shoppers.

Leave a reply