Setup Checklist

Tips for a Smooth Rollout

 

Build a terminal server whose operating system is either:

* Microsoft Windows 2000 Server with Terminal Services enabled.
* Microsoft Windows 2003 Server with Terminal Services enabled.
* Microsoft Windows 2008 Server with Terminal Services enabled.

 

Create a Licensing Server and add a TS CAL (Terminal Server Client Access License) for each thin client.

 

Install ACP ThinManager software onto a computer to create a ThinManager Server.

The ThinManager Server can be a terminal server, but doesn't have to be. It can be a Windows NT 4.0 Workstation, SP5 or better. The clients will connect to the ThinManager Server and download the firmware and configuration.

 

Install an ACP License for in each ThinManager Ready thin client.

 

Select a Client-Communication protocol.

* The default RDP Client-Communication Protocol installs with Terminal Services.
* The optional ICA protocol, if used, is purchased and licensed separately from Citrix.

 

Create a Microsoft user profile for each user on the terminal server.

 

Apply appropriate security to each user profile using the standard Microsoft techniques.

 

Establish the IP addressing scheme for the ThinManager Ready thin clients, Static IP or DHCP

If using DHCP, Configure Option 066 to list the IP address of the ThinManager Server and configure 067 to list "firmware.acp" as the bootfile name.

 

Attach the ThinManager Ready thin clients to ThinManager by either:

* Turning on the terminal and selecting the "Create New Terminal" option when the offline terminals are listed.
* Pre-creating the terminals in ThinManager and selecting the proper terminal name when the terminal is turned on and offline terminals are listed.

Top

Tips for a smooth rollout

DHCP Options: ACP Enabled thin clients that use DHCP to receive an IP address require that the DHCP server have Option 066 configured to list the IP address of the ThinManager Server and Option 067 configure to list "firmware.acp" as the bootfile name. See DHCP for details.

RDP and Auto-Login: Windows 2000 is set by default to prevent the auto-login of terminals. See Windows Configuration Tips for details.

Be careful with license numbers: The leading cause of licensing problems is typing the wrong number during license activation. Double check your numbers while licensing.

Correct refresh rate: Some monitors have limited refresh rates. If a screen goes black or fuzzy when the terminal logs into Windows, change the refresh rate on the Video tab of the Terminal Properties and reboot the terminal.

Top

(Updated 11/10/2008)