Skip to main content

Installing Windows Thin Client

Windows Thin Client allows you to take legacy hardware and continue to utilize it using modern operating systems.  This is done through the usage of Remote Desktop Services in Windows Server 2008 R2.

When booting the ISO file for Windows Thin Client, you will get the usual imagery.

image

Select the language of your choice and click Next

image

 

Click Install Now

image

 

Check I accept the license terms and click Next

image

 

Select the drive that you want to install Windows Thin Client on.

If this is an unformatted drive, click Drive options (advanced).

image

 

Click New

image

 

Determine how much of the hard drive that you want to format and click Apply.

image

 

Click OK at the message below.

image

 

Click Next

image

 

The installation will now run.

image

Provide a name for the first account on this system and a name for this PC.  Remember, this is a local administrator for this client.

image

 

Provide and confirm a password for this account.   Also provide a hint for this password.  Click Next when completed.

image

 

Select the update policy that is appropriate for your environment.

image

 

Select to appropriate time and date settings.

image

 

Configure the appropriate firewall policy for the connection this thin client is on.

 

image

 

Let Setup complete.

image

 

The thin client is now installed.

image

 

This installation of Windows Thin Client consumed only 2.98 GB.  Below is a snap shot of the thin clients memory without any applications running.

image

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.