What is old may actually be new – Part III

Thin ClientIt has been a very busy traveling month and haven’t had time to share more thoughts on this topic so I apologize in advance.

I saw this article today on the topic and I realized it will save me a lot of time explaining how I set up the Thin Clients in my network.  It is a good "How To" and even includes a Real Estate example. I will new focus on the differences in the CRT work.  

First, we used CentOS instead of Debian as an operating system.  In the context to LTSP this is not a big change and the article covers setup well. 

Another difference is that our setup uses OpenLDAP for authentication.  This existing infrastructure allows us to manage authentication centrally for all of our services like administration, e-mail, etc.  Because our client machines need to support either Linux or Windows applications, we needed a way to authenticate to Windows.  We used pGina , and excellent Open Source plug-in for Windows authentication. From the pGina website:

However, Microsoft does allow for customization of its client access and authentication methods through the interface specifications and details of their GINA (Graphical Identification aNd Authentication) dynamic link library. This library “… is a replaceable DLL component that is loaded by the Winlogon executable. The GINA implements the authentication policy of the interactive logon model and is expected to perform all identification and authentication user interactions.” (MSDN)

A third difference in setups has to do with sound.  We wanted to create VOIP enabled workstations.  This requires audio to be supported on either the Linux or Windows servers, and redirecting audio back to the thin client. In the next installment, I will talk about what we did to be network sound running.  

Comments
  1. Hey I love your post ! Good information !

ADD YOUR COMMENT