'; include $_SERVER['DOCUMENT_ROOT'].'/support/desktop/googlead1.html'; } if ($mode=='mobile') { include $_SERVER['DOCUMENT_ROOT'].'/support/mobile/header.html'; include $_SERVER['DOCUMENT_ROOT'].'/support/mobile/googleadsense.html'; echo '
'.PHP_EOL; echo '
'.PHP_EOL; echo '
'.PHP_EOL; echo '
'.PHP_EOL; echo '
'.PHP_EOL; } ?>

Successful thin client projects

Successful projects using thin client technologies such as Citrix XenApp and VDI technologies like Citrix XenDesktop. All need a high degree of testing to ensure success.


A project is only a success if it delivers what it promised to deliver, which in the Citrix world is usability.

It doesn't matter how much bleeding edge technology has been used, if the users can't use the systems effectively, then there is little point of having the system in its current state.

However, by using some form of testing to determine what the root cause of the problems are, usability could be improved.

In the section, Citrix Testing, I look at various options available to ensure the delivery of success.

Functional Testing

In Functional Testing I look at compatibility and coexistence, two important areas of functional testing which need to be addressed before any other type of testing is initiated.

Non Functional testing

The next stage is Non Functional Testing where performance, load and stress testing are done to ensure systems are ready to cope with expected user behaviours.

Acceptance testing

The last stage of testing looks at Acceptance Testing where the systems are checked to see if they are ready to go into a productive 'live' state and start serving users.

Combining user acceptance with production and operational acceptance is highly recommended.

Test tools

I've also included Citrix Test Tools section to provide further information on testing Citrix environments.


Without well planned phases it can become difficult to deliver projects as originally required and this can lead to unwanted downtime, pushing projects costs higher.

Thin Client Solutions

Thin client solutions can provide impressive cost savings in comparision to using the standard thick (fat) client approach but only if these solutions are designed, tested and deployed properly.

Otherwise what seemed like a good idea for cutting costs, could in turn actually start haemorraghing money and turn rapidly into a nightmare scenario.


Design is the first important stage and is split into a logical (high level) design and later into a physical (low level) design element. Actually the requirements gathering and analysis are the most important stages but for the purposes of this website, it is assumed requirements have been gathered and analysed accordingly.

The logical design looks at the services and components used in developing the solution. If the logical design is not done accurately then this can have a knock on effect on other project stages, from the development of the low level design to the testing and deployments of the solution.

The physical design breaks the logical services and components into physical elements such as individual servers, including naming, addressing conventions and resilience configurations.


Deployment is made easier with an appropriate physical design, which can be taken further by including build documentation.

This ensures uniformity in the deployment ensuring components utilised are identically configured, which will further reduce the likelihood of any problems which could have resulted from differing standards and builds.

Successful thin client project

A successful thinclient project can only be achieved by using a structured approach in the design, testing and deployment stages, otherwise the success of a thin client project can be severely jeopardised.