halFILE on Terminal Services

1
Session V

• halFILE on Terminal Services

2
Installation

• If hfw20.exe resides on remote server then must
  use UNC path for setup.exe as well as install
  folder.
• Single install point recommended
• Install for all users

3
Installation

• Requires administrator account with domain and
  local server privileges
• Citrix
• Change user admin
• Microsoft Terminal Server / Terminal Services
• Add/Remove Programs

4
halFILE Printer Installation

• halprn32.exe config
• Install for each user
• UserName is network login
• Allow user access to their unique printer only
• All Users Startup launch halprn32.exe

5
INI Settings

• Setup .ini settings, etc. and place in All Users
• Settings will flow to a user as long as they have
  not logged into halFILE and created the .ini
• To flow new settings you must do manually or
  delete the file from each user

6
Known Issues

• Windows 2000 SP3
• Must run halFILE from UNC path or ip printing
  will fail
• This issue is true of other applications
  including Microsoft Office
• Screen display issue if entire session is
  minimized and later restored
• Upgrade to 2.2

7
Licensing

• Users must logoff their session or exit halFILE
  completely
• Disconnected users with hfw20.exe minimized will
  still count as a halFILE license
• Requires terminal services license purchased from
  hal Systems

8
Windows Server 2003

• No longer offer client license for same OS level
  (XP does not give you a license)
• Supports both user and device licensing
• Supports shadowing like Citrix
• Network load balancing
• Windows Anywhere
• Remote the console
• Client resource redirection

9

• Questions?