ThinManager Introduction

What kinds of content can ThinManger deliver?

ThinManager is a robust content delivery system, capable a delivering a wide variety of content from various sources. This distinction between content and sources is simple, but important. Sources act as one endpoint of a ThinManager content pipeline. You can think of them as ‘content generators’, as they create the content you ultimately deliver. For example, here are some of the possible ThinManager sources:

  • Remote Desktop Servers
  • Virtual Servers
  • Workstations
  • IP Cameras

Content, on the other hand, is the actual data you want in the hands of your users. For instance, a Remote Desktop source might generate a Windows application for a user — or a you might want to deliver the video feed from an IP Camera to some other location.

An important part of ThinManager, however, is that is doesn’t simply blindly deliver content. Instead, access to content can be controlled per device, user, and location. By combining these access controls, it becomes possible to precisely manage content access.

The final piece of the ThinManager content pipeline is the endpoint device itself. These endpoints can be as simple as an Android, iOS, or Windows device running a ThinManager application. However, the real power of ThinManager lies with enabled thin clients.

What are Thin Clients?

Put simply, a thin client is a terminal without a hard drive that connects to a server. Thin clients offer a number of a advantages of a typical client:

No installation, no configuration.

A thin client does not require software installation, configuration, or updating. After all, it doesn’t even have a hard drive to store the software. Instead, all connected clients will use the same application installation.

Lower cost, less maintenance

Another advantage of thin clients is the money saved by not purchasing storage. It also avoids the need to maintain that storage. Operating systems and storage drives are common failure points; maintaining a few servers is much simpler than hundreds of distributed systems.

Automatic failover, and more

Thin clients are capable of connecting to multiple terminal servers. If a server fails, the client will simple switch over to another designated server. It’s even possible for a client to run two sessions from two servers simultaneously; in the event of failure, it will instantly switch to the other session.

To see what else is possible with a thin client, check out this brief, and then take a look at some of OnLogic’s ThinManager Ready Thin Clients.

To learn more about ThinManager and get training on the details, you can visit https://thinmanager.com/training/

Updated on June 23, 2020

Was this article helpful?

Need Additional Support?
Can’t find the answer you’re looking for? Don’t worry, we’re here to help!
Contact Support