How to successfully implement thin clients.

Transcription

1 How to successfully implement thin clients. The platform for successful thin client rollout is solid planning, thorough evaluation under real-world test conditions, and well designed pilot projects.

2 Generally, planning errors do not become evident until actual operation begins. This applies just as much to the rollout of thin client infrastructures as to any migration project, particularly if implementation extends across departmental and location boundaries. To avoid blunders that can destroy budgets and wreck schedules during product rollout, companies need to follow a few basic rules. Step 1: Defi ne requirements It is essential to clarify exact requirements before implementing a thin client solution. Identifi cation of goals with clear deadlines makes it easy to check whether rollout has been successful. Some key aspects to consider are: Sessions, administration, security First, it is necessary to clarify the type and number of sessions planned run on the thin clients. This determines, among other things, which communications protocols are used. For example, Microsoft RDP, Citrix ICA or the X11R6 protocol, or the NoMachine NX protocol for UNIX/Linux environments. It will be helpful to clarify if terminal emulation is required for access to host applications. Terminal emulation solutions permit consolidation of several terminal devices such as workstation PCs and host terminals. Central administration has a major impact on administration costs and on savings that can be made. Here are examples of questions that administrators can use to plan the implementation: How effi cient and operator-friendly is the supplied administration software? What s the price/ performance ratio? Should an existing, alternative third-party solution be used for reasons of synergy Altiris, for example? Customers can leverage some of the IGEL implementation tools to help speed up rollout. Functions such as Buddy Update or Partial Update for thin clients running Windows XP Embedded reduce administrative overhead. When compared to Windows CE or Linux, the tools help update more extensive Windows XP Embedded fi rmware faster with sparing use of network bandwidth. Administrators also need to specify the required security level. For example, special security functions such as support for PKI or Smartcards may be needed. Infrastructure, software and peripherals Key specifi cations for thin client selection also depend on the network infrastructure. Some examples of questions relating to infrastructure include - if a VPN is operated, are DSL connections required? - is a wireless LAN needed? - is there a need to support special technologies such as Token Ring? It is also necessary to determine the available/required bandwidth and how to best use it. For example, the packet sizes of the MTU (Maximum Transmission Unit) must be taken into consideration in VPN networks. If the specifi ed packet size is marginally exceeded, a second packet is generated and, in extreme situations, this can lead to a doubling of the required bandwidth. Customers must consider the number of existing or required servers, their hardware characteristics, and special user requirements. Which standard applications and, more importantly, which vertical or specialized applications are to be made available subsequently via thin clients? Are these applications already available in a terminal server compatible version, or is costly porting required? Clarifi cation of project goals and the thin client operating environment Issues relating to basic requirements:: 1. Sessions: number and type 2. Central management 3. Security level 4. Network infrastructure 5. Available/required servers 6. User requirements 7. Required peripherals 8. Special requirements (logos, colors, etc.) 2/5

3 Table 1: Digital services according to category Category Communications protocols and add-ons Security Virtualization Host access SAP access Application delivery Print services Firmware-internal applications (bandwidth optimization) Firmware-internal applications / plug-ins (bandwidth optimization) Multimedia IP telephony Example Citrix ICA, Microsoft RDP, X11R6, NoMachine NX, XDMCP, Thin- Linc, Sun Secure Global Desktop (Tarantella) Cisco VPN Client (Virtual Private Network), supported by PPTP (VPN), Smartcard, Aladdin etoken, Kobil myidentity VDI Client (e.g. from Leostream for accessing VMware visualization solutions), ICA 10 (access to Citrix Desktop Server) Terminal emulations SAP GUI Citrix Program Neighborhood Agent Thin Client as print server, ThinPrint Client (bandwidth-optimized printing) Browsers: Internet Explorer, Mozilla Firefox, Opera, etc. Java Runtime Environment, Acrobat Reader,.NET Runtime Environment Microsoft Media Player, MPlayer, Real Player, Flash Player, Macromedia Shockwave VoIP (SIP Client) It is also necessary to check which digital services, need to be integrated into the fi rmware of the thin clients (see Table 1). The term digital services covers, for example, additional functions such as media streaming, IP telephony via VoIP and headset, print server functionality, SAP GUI or terminal emulations for direct host access, as well as frequently involved programs such as browsers or plug-ins. Customers are also relying on digital services for access to desktop virtualization solutions (e.g. VDI Client for VMware or ICA 10 and higher for Citrix Desktop Server). All peripherals (and their interfaces) to be addressed by the thin clients must also be taken into account. Examples of these are keyboards and mice with a PS/2 or USB port, printers with a USB or parallel port, monitors with a VGA or DVI interface, etc. Customers can also consider additional requirements such as multi-display or multi-user scenarios. Examples from the realm of CI are logos or corporate colors for cabinets, boot process, screen saver, or desktop background. Step 2: Realistic model evaluation Once all requirements have been determined, they must be matched to the features of the thin clients. An initial test setup with several selected models generally identifi es one, two or three favorites. A decision matrix helps evaluate the devices. A realistic test environment will ensure a smooth rollout. Business-critical applications should be subjected to the most stringent tests. Laboratory testing can be followed by a further test phase. By involving end-users, companies can cater to all requirements and expectations and ensure that the system is tuned. If possible, users should work with the new devices for several days. This should reveal potential faults and problems. The entire test phase benefi ts greatly from all-round assistance by the vendor upon request, the vendor should also carry out customer-specifi c modifi cations to fi rmware, such as integrating certain device drivers or software clients. 3/5

4 Thorough testing and pilot operation pay off by generating savings! Step 3: Pilot phase and rollout Larger rollouts should be preceded by pilot operation following on from the test phase. A pilot operation is justifi ed for a customer with more than 50 devices, or those with distributed locations. Qualifi ed employees are crucial to the success of the pilot phase and rollout. Internal and external members of the project team must have appropriate training and be able to resolve standard problems quickly. It is also advisable to keep a few devices in reserve. A guide fi gure is fi ve to ten percent of the number of devices to be installed. This ensures that faulty devices (damaged in transport, for example) can be replaced. If fewer replacement devices than expected are needed during rollout, they can be installed at the end of rollout. Servers and the network infrastructure should be functioning perfectly before fi nal move is made to production operation. Otherwise, there is a risk in terms of employee acceptance. Provision of a feedback loop If the pilot phase gives rise to new requirements, it is advisable to include them in a repeat evaluation instead of delaying the rollout schedule. Any new requirements must fi rst be evaluated. In a further evaluation phase, it is then necessary to decide on the best form of implementation and to select appropriate devices. As a rule, vendors offer a variety of performance classes with different equipment levels. If the change to the requirements profi le affects only some workplaces, these can be equipped with devices of a higher performance class. Faster is better If rollout speed is a key criterion in thin client selection, a preconfi guration option should be available. In other words, device confi guration is planned and defi ned before the devices are installed. This can be done using profi le-based management tools. Workplaces are then immediately available for use once the pre-confi gured devices have been set up and connected. This substantially reduces the costs and time needed for rollout--a benefi t to companies who want to expand quickly or for those who need to be fl exible in terms of location. Figure: Recommended project workflow 4/5

5 Good planning is half the roll out The cleaner the roll out plan and the better the support from the vendor, the less problematic the roll out will be. Whoever has done his homework, has practical know-how in the background, and has tested as realistically as possible, will enjoy a problem-free thin client implementation. Good planning is half the implementation battle Smooth rollout calls for detailed planning and all-round assistance by the vendor or systems house. Further aspects that ensure trouble-free migration are near real-world testing and professional support. Example: IGEL Remote Management IGEL Technology thin clients can be configured in advance using the free IGEL Remote Management Suite administration software, and then put into service within a matter of minutes. Customers can also save time by importing the device parameters into the Remote Management software by means of CSV lists containing the MAC addresses of the thin clients. Germany (HQ) United Kingdom United States Singapore Hong Kong IGEL Technology GmbH Schlachte 39/ Bremen Germany Tel +49 (0) Fax +49 (0) IGEL Technology Ltd 1210 Parkview Arlington Business Park Theale Reading Berkshire RG7 4TY UK Tel +44 (0) Fax +44 (0) IGEL Technology Inc NW 35th Avenue Fort Lauderdale FL USA Tel Fax Toll Free (US only): GET IGEL IGEL Technology Care of: C. Melchers GmbH & Co. Singapore Branch 101 Thomson Road # 24-01/05 United Square Singapore Tel (65) Fax (65) IGEL Technology Care of: Melchers (H.K.) Ltd Shun Tak Centre West Tower Connaught Road C. Hong Kong Tel Fax IGEL Technology A member of the Melchers group. info@igel.com FEB-08 US