OpenKiosk 2.0 client for Windows

Intended audience:

System and Network administrators for a Windows-based local area network.

Summary

OpenKiosk client for Windows is the client software of the OpenKiosk system that is designed to operate on Microsoft Windows Operating Systems. The OpenKiosk client for Windows needs to connect to the OpenKiosk server, NodeView for authentication and loading system configurations. The location of NodeView is specified during the setup process. On Windows NT, 2000, and XP, it can be modified while logged in as an administrator on the client machine. To prevent from being disabled by malicious users, the client software depends heavily on the security features of the underlying operating system. Due to its built in secure features, NT-based machines, such as Windows 2000 and XP are the recommended platforms of the OpenKiosk client for Windows.

Requirements:

Installation

Windows NT, 2000,XP:

  1. While logged as an administrator you need to create a user account for the OpenKiosk client. This will be the default account in which your customers will be accessing the controlled computing environment provided by the OpenKiosk client for Windows. The account should not be a member of the administrator group. Preferably, you should set it up as a restricted or standard user account. Click start menu --> settings --> control panel --> Accounts / users.
  2. Double click the installation file opwinclient.exe to begin installation. Follow the instructions on the screen carefully.
  3. When you reach the setup page where the installer asks you to configure the location of the NodeView server, fill the following values correctly:

          NodeView server:       The host or IP address of your local NodeView server.
          Port:                  The port of your local NodeView server. It is set to 10018 by 
                                 default. You change this if you have modified the settings on 
                                 the server.
          Station:               A unique case-sensitive name that matches the station name you 
                                 specified for this particular workstation on NodeView. NodeView 
                                 needs this information to uniquely identify each kiosk from the 
                                 rest of the stations in the network. You have to name each 
                                 workstation properly to prevent conflicts.
    
          Example:
    
          NodeView is running from 192.168.0.1 and is listening on port 10018. This client is 
          listed as Station name: pc04 with IP address: 192.168.0.24 in the workstations 
          configuration in NodeView. These are the correct values for this page:
    
          NodeView server value: 192.168.0.1
          Port:                  10018
          Station:               pc04
    

  4. The next page will be the client information page. It will prompt you about the account information you created in step 1. Enter these values correctly. The OpenKiosk client needs this information for the auto-login feature in Windows. Auto-login bypasses the standard Windows login dialog and drops the user straight to the OpenKiosk client dialog running in the account created in step 1.
  5. Some establishments may choose access numbers to authenticate the clients while others may prefer membership accounts. Or you could enable both methods for authentication. A library may choose the name "barcode" or "library ID" for the access number. In this page, the OpenKiosk client login dialog can be customized to match the setup of your establishment. The login and password labels can be changed to whatever names you may call the login/password combination. To force your users to use anonymous access numbers or you do not want membership accounts you may chose to disable the password field by un-checking "Enable password."
  6. Click Install and reboot the machine if the installer instructs you to do so.

Windows XP SP 2 caveats

Windows XP service pack 2 comes with some security enhancements to disable malicious programs from connecting across the network. As with other unsigned but legitimate programs that need to access the network, this feature affects the OpenKiosk client. Make sure to enable or unblock the OpenKiosk client for Windows when prompted if access to the network is allowed.

Windows 95, 98, ME:

The same process is followed as the installation steps above for NT-based Windows operating system, except that Windows 95, 98 and ME doesn't have the concept of security and therefore has no administrator or user-based accounts. You should be careful that the values you entered in the OpenKiosk setup page are correct or the client machine where you are installing the OpenKiosk client will be impossible to unlock. If this happens, reboot into safe mode and uninstall the program from there or use a previous registry backup.

Administration

Hold down the shift key while the client computer is booting up or when it is logging off from the OpenKiosk client user account to access the administrator account. Enter the Windows administrator account password and username on the Windows login dialog. If authenticated, the OpenKiosk client should present you with an administration tool to setup the options of the OpenKiosk client. The tool has the same configuration options on the installer software. Please refer to the installation sections 3 - 5 above for details.

Customer Usage

The login interface should be self-explanatory. The login dialog accepts standard access numbers that are generated by NodeView and username-password combination for member accounts. Access numbers are entered on the username field. Both membership accounts and access numbers can only be accessed on one kiosk at a time. To transfer to another station, users must log-off first from their current session.

When the client is unlocked, the customer can view their remaining time on the timer-box located just slightly above the system clock on the taskbar. Right clicking the OpenKiosk system tray icon, which is shaped like an hourglass, brings up the OpenKiosk menu. To hide/unhide the timer box click hide/unhide timer box. To log-off from their OpenKiosk accounts, users either use the standard Windows log-off on the start menu or use the log-off menu from the OpenKiosk system tray icon.

client tray menu

Both OpenKiosk member accounts balance and access numbers credits are reloaded on values from new access numbers.

To reload or extend the prepaid credit of the currently in-use access number, users must select Reload/extend account on the OpenKiosk system tray icon while there is still remaining time on the current access number. Users will not be able to reload access numbers if the time remaining is consumed to zero and will have to obtain another access number to use the workstation. Users must then enter a new access number on the access number entry dialog. The balance on the entered access number will be transferred entirely to the currently in-use access number.

To reload or extend the stored balance of the currently in-use member account, users must select Reload/extend account on the OpenKiosk system tray icon while there is still remaining time on the current member account. Users must then enter a new access number on the access number entry dialog. The balance on the entered access number will be transferred entirely to the current member account. If the member account is consumed to zero, an Operator can extend the prepaid credit on the NodeView controller by accessing the member account details on NodeView configuration.

If a member account is configured with bonus incentive, and the auto-add feature is enabled, the specified balance will be automatically added to the member account if the bonus condition is met.

For member accounts, selecting Change my Password on the OpenKiosk system tray icon changes the member password.