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.

Select the language of your choice and click Next

Click Install Now

Check I accept the license terms and click Next

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

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

Click New

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

Click OK at the message below.

Click Next

The installation will now run.

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.

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

Select the update policy that is appropriate for your environment.

Select to appropriate time and date settings.

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

Let Setup complete.

The thin client is now installed.

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.

Comments

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.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog