In our previous article, we discussed the deployment types within IT which tend to fall under two modes, known as Bimodal IT (read part one here) in this post we will discuss how these can be adopted from the perspective of the end user and how we can facilitate the transition from Mode 1 to Mode 2 applications and solutions. The challenge of Mode 2 is its shear rate of change which can have quite an impact to the end users of the solution, plus provide an administrative overhead to IT staff whom now have to manage two modes of release cycles to their end users. It is often timed too that this change in development and deployment comes a the same time other transformation projects are also underway. So now is the best time to evaluate which direction you need to take your end user services. We have all seen the change from main frame computing, to distributed computing, to VDI (or mainframe in colour) to now the adoption of Cloud / SaaS based applications. However the difference now being – unlike previous generations of IT – that all of these exist at the same time, of which the endpoint device has to fully support. With the administrative overheads, complexity and costs all increasing, businesses are faced with a challenge – do we adopt Mode 2 and innovate (taking on the risks discussed) or continue with the lower risk Mode 1 in the fear that the business is left behind the curve. Its not all doom and gloom, there are options available to easily support these modes. I am not a usual fan of product placement, however I felt this one did the subject matter justice – iGEL – but how can a thin client manufacturer facilitate Bimodal IT?
iGEL & Bimodal IT
iGEL has been supplying high quality thin client technologies for quite some time, mainly when businesses want to save money on endpoint devices as they moved to Server Based Computing (SBC) or Virtual Desktop Infrastructure (VDI) – however, given the flexibility of an iGEL thin client – and the options of devices available – these offer a viable alternative to full desktops in multiple scenarios. Where a business is still operating at Mode 1 and requires SBC or VDI, iGEL delivers a high quality end user experience at the fraction of the cost in CapEx and OpEx of its traditional desktop counterpart. However when it comes to Mode 2 (and the transition from Mode 1 to Mode 2), this is where iGEL comes into its own.
Within the iGEL ecosystem is a highly available management system known as the Universal Management System (UMS). This provides a centralised management portal for all types of iGEL devices (including their Universal Desktop Converter tool or UDC). It enables fine grain policy and configuration of the endpoints in near real-time, allowing rapid changes to be made across the end user estate. Mode 1 is delivered to the endpoints via SBC or VDI, whereas Mode 2 can utilise the built in browsers etc. (and properly configured, this can appear seamless to the end user.
Managing Transition between Mode 1 and Mode 2
At some point, businesses adopting Mode 2 will face a transition period where the same endpoint device needs to support both Mode 1 and Mode 2 operations. In fact in many cases, businesses will continue adopting both models as required. Having the ability to support both operations from the same device facilitates both business and end user transformation. In offices that adopt hot desks, this is even more important for any endpoint to support any use case. This is where the iGEL range offers the flexibility to support the task worker, all the way up to the high end developer. There is however another use case that often gets overlooked when endpoints are converted to Thin Clients, and that’s the mobility worker. This is where iGEL extended infrastructure can support these use cases too (including mobility and home based workers).
Manage Anytime, Anywhere
iGEL Cloud Gateway extends the management capabilities of the on-premises UMS out to the cloud and beyond to any endpoint with a network connection. Via a secure SSL connection, any endpoint can connect to the centralised management system and receive the same updates and configurations as though they are in the office. As home working or “coffice” based workers (people whom use coffee shops as their office) are becoming more common place, supporting these workers becomes more challenging, however by providing the extended management, their devices are now able to roam. This is not just limited to remote workers, other great use cases for adopting this model are: Retail (provide the endpoints without requiring the management infrastructure) and Healthcare (adjust thousands of devices all at once regardless of their location / status). As both of these move towards Mode 2 of IT, having the ability to make rapid changes across the estate facilitates the roll-out of the applications and solutions. As a final point, have you ever been concerned about the amount of devices you provide to end users, or how you would provide a DR solution to your office based users? Devices are no longer bulky and difficult to manage, imagine if every user could carry their own DR endpoint device in their pocket, more importantly attach this to their most important asset (usually their keys), well take a look at this: video regarding the UD pocket – an amazingly small device that fits onto a key ring, with the power of a full thin client: www.youtube.com/watch?v=5Xt8WsI84bM