advertisement
Documentation Area
Windows Embedded User Guide
This document is exclusive property of Praim Srl.
Permission is granted to print and copy this document for noncommercial distribution.
Author:
Date:
URL:
Documentation
07-Nov-2013 08:34 http://wiki.praim.com/display/WE212
Page of 49
Windows Embedded User Guide
Table of Contents
1 Getting Started ___________________________________________________________________________ 4
1.1 Default User _________________________________________________________________________ 5
1.2 Default Network Configuration _______________________________________________________ 7
1.3 Installed Software and Connection Clients ___________________________________________ 10
1.4 How to Log Off, Shut Down and Restart _____________________________________________ 13
2 Praim Utilities and Settings ______________________________________________________________ 15
2.1 Accessing the Praim Manager _______________________________________________________ 16
2.2 Configuring the ThinMan Server Address ____________________________________________ 19
2.3 Configuring the ThinMan Remote Assistance ________________________________________ 20
2.3.1 Tray Bar Icon _________________________________________________________________ 21
2.4 Using the Write Filter _______________________________________________________________ 23
2.4.1 Enhanced Write Filter (EWF) __________________________________________________ 24
2.4.2 File Based Write Filter (FBWF) _________________________________________________ 25
2.5 Configuring the PRAIM USB Redirection _____________________________________________ 30
2.6 Connection Manager ________________________________________________________________ 34
2.6.1 Managing generic connection _________________________________________________ 34
2.6.2 Managing Microsoft RDP Connection __________________________________________ 37
2.6.3 Managing VMware Horizon View Connection __________________________________ 39
2.6.4 Managing URL/Link Connection _______________________________________________ 40
2.6.5 Managing Citrix Receiver Connection _________________________________________ 41
3 Device Administration ___________________________________________________________________ 43
3.1 Installing Praim Service Pack and Hotfix _____________________________________________ 44
3.2 Backup, Restore and Device Cloning ________________________________________________ 45
3.3 Using ThinMan to Remote Assistance a thin client ___________________________________ 47
4 How To __________________________________________________________________________________ 48
4.1 How to enable execution of *.ps1 file (Powershell) on the thin client _________________ 49
PRAIM Windows Embedded Standard Thin Client
Page of 49
Windows Embedded 2.1.2 Guide
PRAIM Windows Embedded Standard Thin Client
User Guide
Version: 2.1.2
Revision: 1
Date: 07 November 2013
This document has been produced by Praim.
This guide, the software and the firmware are protected under international copyright laws, with all rights reserved. It's forbidden to reproduce, adapt or translate this guide into any language in any form or by any means, except documentation kept by the purchaser for backup purposes, without explicit written permission of Praim Srl.
The information in this document is subject to change without notice. Praim Srl makes no representations or warranties with respect to the contents hereof and specifically disclaim any implied warranties of merchantability or fitness for any particular purpose. Further, Praim Srl reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Praim Srl to notify any person of such revision or changes.
Unless otherwise specified, all references to company names, addresses and data appearing in this guide or in screenshots and examples are fictitious and is only meant to illustrate the use of the Praim product and are used only for identification or explanation and to the owner’s benefit. All products and/or company names mentioned herein are trademarks or copyrights of their respective owners.
Page of 49
Windows Embedded User Guide
1 Getting Started
This chapter provides information to get started with the Praim Windows Embedded thin client
(WES7 and XPe). It describes basic thin client features and gives you instructions on setup the thin client environments.
Screen-shots are grabbed from a WES7 environment but concept can be also applied on XPe environment.
NOTE
The Praim Windows Embedded thin client are comparable, in terms of functionalities and configuration, to a normal computer running a Microsoft Windows operating system (WES7 are comparable to Windows 7 O.S, XPe are comparable to XP O.S.).
Most of the operations that perform on a personal computer can be also performed on a thin client with Windows Embedded operating system.
NOTE
Please notice that every configuration or every modification on the thin client is not saved permanently on it. The default behaviour is NOT to save changes on the Disk On
Module (DOM) but only on the RAM memory. All these changes will be lost on thin client reboot (Write Filter). To save permanently modified configuration and changes on the Praim thin client please read the chapter
Using the Write Filter (see page 23)
.
Page of 49
Windows Embedded 2.1.2 Guide
1.1 Default User
Praim thin client is initially conifgured, as default, with only one user in the Windows Embedded
O.S.. The username is "Admin", the account type is "Administrator" and the password is not set.
Accessing a Praim thin client for the first time will shown the desktop for this user.
You can quickly change the settings for this user or create new users using the Windows standard "User Accounts" icon inside the "Control Panel" window.
Page of 49
Windows Embedded User Guide
To save changes remember to commit them on the DOM (see more information on
Using the Write Filter (see page 23) ).
Page of 49
Windows Embedded 2.1.2 Guide
1.2 Default Network Configuration
The network configuration is initially set in this way:
IP Address is obtained via DHCP
DNS Server is obtained via DHCP
IPv4 enabled
IPv6 enabled
You can change this basic configuration by accessing the "Network Settings" into the "Control
Panel" window.
Page of 49
Windows Embedded User Guide
List of services enabled in the Local Area Connection by default.
Page of 49
Windows Embedded 2.1.2 Guide
You may be requested to identify the Network Location where the thin client has been deployed and powered on. Just select the network location as on a normal Windows PC.
To save changes remember to commit them on the DOM (see more information on
Using the Write Filter (see page 23) ).
Page of 49
Windows Embedded User Guide
1.3 Installed Software and Connection Clients
On the Praim thin client the most important connection clients are already installed.
RDP Client, Citrix Receiver and VMware View Client are at user disposal
They had to be configured in order to allows a connection to the specific farm.
For more informations on clients configuration refer to the specific documentation on vendor website.
Page 10 of 49
Windows Embedded 2.1.2 Guide
Connection clients can be also uninstalled, like any other applications, clicking on the
"Programs and Features" icon in the "Control Panel" window.
E.g. a list of installed software in a Praim Thin Client
Page 11 of 49
Windows Embedded User Guide
E.g. a list of installed software in a Praim Thin Client
Depending on the free space on the DOM you may also install new software like in a normal PC.
Launch the installation file and follow the instructions. Remember that if a reboot is required, do not allow the software to do it but execute a commit on the DOM (see more information on
Using the Write Filter (see page 23) ) and this operation will automatically reboot the terminal
saving changes on the DOM.
To save changes remember to commit them on the DOM (see more information on
Using the Write Filter (see page 23) ).
Page 12 of 49
Windows Embedded 2.1.2 Guide
1.4 How to Log Off, Shut Down and Restart
Use the Shut Down menu to log off, shut down, restart, or place the thin client in stand by.
All the options are available to use by clicking menu "Start" -> "Shut Down".
Page 13 of 49
Windows Embedded User Guide
All the operations can be also invoked on the thin client using the Windows Security window
(opened by using CTRL+ALT+DEL hotkey combination).
Page 14 of 49
Windows Embedded 2.1.2 Guide
2 Praim Utilities and Settings
This chapter provides detailed information about the utilities and settings available from the
Praim Manager applet placed in the control panel.
It includes:
Accessing the Praim Manager (see page 16)
Configuring the ThinMan Server Address (see page 19)
Configuring the ThinMan Remote Assistance (see page 20)
Using the Write Filter (see page 23)
Configuring the PRAIM USB Redirection (see page 30)
Connection Manager (see page 34)
Page 15 of 49
Windows Embedded User Guide
2.1 Accessing the Praim Manager
The "Praim Manager" is an item of the Windows Control Panel.
To access the Control Panel click on the Start Menu icon on the bottom left corner and select
"Control Panel".
Page 16 of 49
Windows Embedded 2.1.2 Guide
If it is not already selected change the "View by:" option to "Large icons" or "Small icons".
Locate the "Praim Manager" item and click it.
Depending on "User Account Control" setting you may be asked to give permission to make changes to the computer. Click on the shield icon on the task bar.
Page 17 of 49
Windows Embedded User Guide
Click "Yes" to the request dialog. This will allow the Praim Manager to be executed.
The Praim Manager windows is now visible with different options available to the user.
Page 18 of 49
Windows Embedded 2.1.2 Guide
2.2 Configuring the ThinMan Server Address
From the "Praim Manager" window (for more informations see
) you click on "ThinMan Agent" icon to configure the ThinMan Server referenced by the thin clients.
When configured, the thin client will use HTTPS Protocol instead of TCP/UDP (reliable device status) sending ThinMan more information on device itself (Serial Number, IP Subnet…).
Values that may be entered are:
DHCP Option
: is the number of DHCP Option configured on the DHCP Server to set
ThinMan Address. Default value is 163.
ThinMan Address
: whether the DHCP Option is not configured the thin client will use this address to communicate with ThinMan. Default value is PRAIM_THINMAN.
Click "Test Connection" to try the information entered.
Note
Providing the ThinMan Server address via network parameters (DHCP Option 163 or
PRAIM_THINMAN resolution name) can be really useful; it avoids local changes on thin client configurations and brand new (out-of-the-box) device will automatically notify to
ThinMan Server.
Page 19 of 49
Windows Embedded User Guide
2.3 Configuring the ThinMan Remote
Assistance
It enables the VNC service on the Thin Client. Once enabled it allows the "Remote Assistance" from the ThinMan Console.
Default values are those provided in the above screenshot.
Enable Remote Controls Connections
: it enables the VNC service. When it is enabled others parameters are modifiable. When not enabled the "Remote Assistance" menu in
ThinMan Console is not available.
Section "Accept Remote Control"
Accept Always
: the VNC server will always accept remote VNC control requests.
Accept/Reject
: a dialog box will be displayed on the thin client when someone attempts to take remote control of the terminal over the network. The dialog box allows the thin client user to either accept or reject the remote control request.
Auto Accept after
: it automatically accepts remote control requests after a specific time interval (in seconds).
Section "Protected Logon"
Password and Confirm
: a password is required when taking remote control of the client.
Page 20 of 49
Windows Embedded 2.1.2 Guide
Password and Confirm
: a password is required when taking remote control of the client.
Do not Show Wallpaper
: if enabled, the thin client wallpaper is not displayed in the remote assistance session.
Show Tray Bar Icon
: if enabled the remote connection icon will be shown in the tray bar.
2.3.1 Tray Bar Icon
The icon is red when a remote connection is running (by hovering over the icon the IP address of the remote user will be shown).
The icon is instead blue if there is no remote connection to the thin client.
If you right-click the tray icon a contextual menu is shown:
"Remote Assistance Settings..." will display the current settings for the remote assistance
Page 21 of 49
Windows Embedded User Guide
"Remote Assistance Settings..." will display the current settings for the remote assistance feature,
"Disconnect from <IP Address>" will disconnect the remote assistance session
Page 22 of 49
Windows Embedded 2.1.2 Guide
2.4 Using the Write Filter
The Operating System, the installed software and all files needed by the thin client are saved on a flash memory (DOM, Disk On Module).
To protect this space from undesired writings and to avoid not necessary flash activitiesWindows Embedded use a write filter. The filter diverts I/O requests, coming from processes, to temporary savings into the RAM memory. Data temporary stored on RAM memory are accessible to users as long as the thin client is powered on. This explains why when a thin client reboots, it starts from the previously saved configuration and no savings were made in the flash memory during the running phase of the thin client.
The write filter is also a benefit that helps to extend the life of the flash memory.
To store permanently the savings made in the RAM memory, onto the flash memory a
"commit" operation has to be executed. In such a way, all savings made up to that moment will permanently be stored in the flash memory.
Tip for software installation
When you are installing new software on the thin client be sure to execute the commit operation at the end of the installation. Do not allow the installation software to reboot the thin client because in this way all changes will be lost.
Tip for maintaining a clean installation
Whether you plan to install new software or modify the file system of the thin client be sure to do that in fresh rebooted thin client. In this way you will start from a "clean" thin client and commit operation will save only changes you know. Committing changes on a thin client powered for hour or days could save unwanted data.
The write filter can be disabled, in this case all the writings will be executed immediately on the flash memory.
Tip for installation of mutiple software
If you plan to install different software (with many rebooting) you can previously disable the write filter: in this case any change will be immediately saved on the flash memory. When you finish to install the software remember to activate the write filter again.
Praim Windows Embedded thin client support two different type of write filter:
Page 23 of 49
Windows Embedded User Guide
Enhanced Write Filter (EWF): it protect all the flash memory from changes.
File Based Write Filter (FBWF): can be based on file and/or directory changes and allows more granularity protection. Available only on WES7 thin client.
2.4.1 Enhanced Write Filter (EWF)
The Enhanced Write Filter (EWF) protects the flash memory from changes.
EWF is enabled by default on Praim Windows Embedded thin client. When disabled the flash memory can be written without protection.
To modify EWF access the Praim Manager (see
Accessing the Praim Manager (see page 16)
) and then click on the "Enhanced Write Filter Manager" icon.
Page 24 of 49
Windows Embedded 2.1.2 Guide
The four buttons allows to:
Enable
: it enables the EWF Service. This operation requires a reboot of the thin client.
Disable
: it disables the EWF Service. Pay attention because this operation will commit all the changes made on the thin client until the reboot process. Once disabled the thin client will reboot every time with the filter off. The operation can be cleared by clicking on "Clear" before the thin client is rebooted.
If you have to disable the EWF do it after a thin client rebooting and then reboot the thin client again.
Commit
: will "commit" the writings saved in the RAM onto the flash memory. This operation doesn't commit changes immediately, but advise the device to permanently save data on flash during next power off. This reserved operation can be cleared by clicking on "Clear" before the thin client is powered-off.
Clear
: will clear the previously reserved commit or disable filter operation.
2.4.2 File Based Write Filter (FBWF)
The File Based Write Filter (FBWF) can be configured to protect/unprotect files or directories. In order to activate the FBWF you have to disable first the EWF. To modify FBWF access the Praim
Manager (see
Accessing the Praim Manager (see page 16)
) and then click on the "Enhanced
Write Filter Manager" icon.
Page 25 of 49
Windows Embedded User Guide
The three buttons allows to:
Enable
: enables the FBWF Service. The operation can be cleared clicking on "Disable" before the thin client is rebooted. This operation requires a reboot of the thin client.
Disable
: disables the FBWF Service. The operation can be cleared clicking on "Enable" before the thin client is rebooted. This operation requires a reboot of the thin client.
Config
: run the configuration window for the FBWF (see below for more informations).
The operation is available only when the FBWF is enabled.
Configuring FBWF
To configure the File Based Write Filter click on "Config" at the bottom of the EWF Manager window.
Page 26 of 49
Windows Embedded 2.1.2 Guide
On the "Configuration" tab you can configure these options:
"
Filter state enabled
": it will enable or disable the write filter. Use the "Praim Manager" to enable/disable the filter instead of this option.
"
Cache compression enabled
": enable the compression of the content in the cache.
This affects directly performances of the unit as the compression requires more CPU.
Default is disabled.
"
Cache pre-allocation enabled
": pre-allocate the cache space. Default is disabled.
"
Cache threshold
": configure the maximum amount of RAM memory to be used
Page 27 of 49
Windows Embedded User Guide
On the "Configuration" tab you can configure which directory path are excluded from the write filter (these paths will be writeable from any process).
"
Volume name
": change the disk volume
"
Add path
": will add a new exclusion pathname into the selected volume
More detailed informations on the FBWF can be found on the Microsoft page http://msdn.microsoft.com/en-us/library/ff794219%28v=winembedded.60%29.aspx
How to use and configure the FBWF on the thin client in few steps
Suppose you want to use the thin client using the FBWF with a directory that can be written by processes and that maintains its data despite a thin client reboot.
This configuration can be simply achieved following these steps: disable any write filter and reboot the thin client create the folder or the file that has to be writeable (e.g. create "Writeable Folder" in the
"C:\" directory) enable the File Based Write Filter and reboot the thin client inside the FBWF configuration window add the path of the directory to the exclusion list
(e.g. insert "\Writeable Folder" in the "Add path" field and click on "+") and close the
FBWF configuration window reboot the thin client
From this moment every writings in the configured directory will be saved on the Disk On
Page 28 of 49
Windows Embedded 2.1.2 Guide
From this moment every writings in the configured directory will be saved on the Disk On
Module (DOM) memory of the thin client and its content will be preserved from the thin client reboot.
Page 29 of 49
Windows Embedded User Guide
2.5 Configuring the PRAIM USB Redirection
Praim USB Redirection is a feature available on WES7 thin client that allows to redirect USB devices from the thin client to the Virtual Desktop.
The protocol use a TCP connection (port 15801) and does not support tunneling feature (Citrix or VMware).
Depending on the virtualization infrastructure and on connection protocol it can be better to use the USB Redirection provided by the infrastructure solution (e.g. HDX USB Redirection for
Citrix or VMware USB Redirection).
To correctly use the Praim USB Redirection the TCe-VDA software has to be installed in the virtual desktop, whereas the Praim USB Redirection feature has to be enabled on the thin client. To activate the Praim USB Redirection on the thin client you will require ThinMan management software (see more information on http://wiki.praim.com/display/ThinMan or search the wiki for "Activate Praim USB Redirection").
To enable the USB Redirection capability access the Praim Manager window.
On the window double click "Praim USB Redirect Client".
Page 30 of 49
Windows Embedded 2.1.2 Guide
When the USB Redirection is not enabled you will be given possibility to use this feature in demo mode for 7 days. Click on "Start" to enable it.
The USB Redirection window is shown. After the USB Redirection is enabled users can define which device categories are to be shared or not (e.g. devices such as mouse or USB keyboard are not to be shared because the "Human Interface devices" class is not enabled). Clicking on
"Exception list" shown the user which devices are to be shared or not independently from its category.
Page 31 of 49
Windows Embedded User Guide
The window will show the exception device list and the currently connected device list. Users can also add exceptions selecting the connected device and clicking on "Add to Ex list".
Select if the device has to be always or never exported via the PRAIM USB Redirection feature.
Page 32 of 49
Windows Embedded 2.1.2 Guide
The device is added to the exception list and depending on the rule will be always or never exported.
Page 33 of 49
Windows Embedded User Guide
2.6 Connection Manager
The Connection Manager allows to create, delete and modify connections on the thin client.
Once the connections are created it is possible to read them from ThinMan. This operation allows to create a Device Profile into the ThinMan Server, after this it is possible to push the profile into other WES7 thin client using the ThinMan Profile Manager (for more information read the ThinMan User Guide at the section "ThinMan Profile Manager").
Manageable connections are:
Microsoft RDP Client
VMware Horizon View Client
Citrix Receiver Client
URL or Pathname
2.6.1 Managing generic connection
A generic connection can be added, deleted, modified or started using the buttons in the lower part of the user interface. The command will apply to all the types of connection that can be defined on the thin client. Specific information on single connection are available in the next chapters.
Once you have created the connections needed, clicking on "OK" will save the connections on the thin client and create links on the desktop. These links can be used to execute the connection without the need to access the connection manager (these links will be available to all users defined on the thin client, also on user that do not have Administrator privileges).
Page 34 of 49
Windows Embedded 2.1.2 Guide
Best Practice Tip to distribute configuration to many thin client
Create the needed connections on a single thin client and save them on the thin client
(remember to commit the changes in order to save them on the disk; see
Write Filter (see page 23) for more information).
Use ThinMan Server to read the configuration created on this thin client and save it as a template.
From the saved template create a Configuration Profile and associate it to a Policy.
The Policy allows to distribute the original configuration (based on connections for
WSE7 devices) to many other device (you can associate the Policy to multiple devices, groups of devices, via the Classifier or define it a Default Policy).
See ThinMan User Guide for more information (read in particular "Profile Manager" chapter).
Add a connection
To add a connection enter its name in the field "Connection name" and then click on "Add".
The configuration window for the specific connection will be opened so you can enter the parameters for that connection.
Closing the configuration window will save the connection on the thin client.
The connection is also shown (with most important configuration attributes) in the list.
Clicking on "OK" on the Connection Manager window will create, on the desktop, the icons that
Page 35 of 49
Windows Embedded User Guide
Clicking on "OK" on the Connection Manager window will create, on the desktop, the icons that can be used to execute the connections on the thin client. These icons will be visible to (and can be executed from) all users defined on the thin client, regardless they have Administrator or Normal User rights.
Delete a connection
Select, from the list, the connection to be deleted and then click on "Delete".
Confirm to remove the connection from the Connection Manager.
Edit a connection
Select, from the list, the connection to be modified and then click on "Edit".
The configuration window for the specific connection is opened so you can modify the parameters for that connection.
Start a connection
Page 36 of 49
Windows Embedded 2.1.2 Guide
Select, from the list, the connection to be started and then click on "Connect".
The connection is started executing the specific client with the configured parameters for that connection.
A connection can be also executed by double clicking its icon on the desktop (remember that the connections icons on the desktop can be executed from all users defined on the thin client, regardless they have Administrator or Normal User rights).
It is also possible to define a connection in auto-start mode by placing a tick in the attribute
"AutoRun". All the connections defined in this way will be automatically executed at the thin client start-up without any intervention of the user.
2.6.2 Managing Microsoft RDP Connection
From the "Connection Manager" window select the "RDP" tab.
Page 37 of 49
Windows Embedded User Guide
When a Microsoft RDP connection is created the standard window for Microsoft Terminal Server
Client installed on the thin client is launched (mstsc.exe).
Through the different tabs it allows to define all the parameters needed to connect via RDP protocol to a server or to a workstation (physical or virtual does not matter).
To save the configuration after changes click on "Save" in the "General" tab. To close the window click on the red "X" in the upper-right corner of the window.
Best Practice Tips
To avoid the annoying windows that warn on identity and certificates when the client starts (if the server does not owns appropriate certificates) select in the "Advanced" tab the "Connect and don't warn me" option (the default option is "Warn me") from the
"Server authentication" drop-down menu.
Execute the connection for the first time ticking the option to remember the choice from the successive windows.
Execute a "commit" on the thin client to save the environment (see
Filter (see page 23) chapter).
For more information refer to Microsoft documentation.
Page 38 of 49
Windows Embedded 2.1.2 Guide
For more information refer to Microsoft documentation.
2.6.3 Managing VMware Horizon View Connection
From the "Connection Manager" window select the "VMware" tab.
When a VMware Horizion View connection is created the window above is opened. It allows to insert:
Connection Server
: the Horizon View connection server to which connect the client when launched (if it is specified cannot be changed afterwards by the user)
Use RDP
: set RDP as default protocol to connect to the virtual desktops otherwise PCoIP protocol is used (cannot be changed afterwards by the user)
Domain Name
: the domain of the server (used to check the user credential) (if it is specified cannot be changed afterwards by the user)
Desktop Name
: the desktop name to which to connect (if it is not present on the desktop pool, the connection will produce an error and then exit)
Desktop Layout
: set the screen size for the connection window (cannot be changed afterwards by the user)
Kiosk Mode
: allows the using of VMware Kiosk Mode that has to be defined on the server side (see VMware documentation for more information)
Connect USB on startup
: when flagged allows the virtual desktop to automatically mount USB device already inserted at the virtual desktop startup (if not flagged the mount has to be executed explicitly)
Connect USB on insert
: when flagged allows the virtual desktop to automatically mount USB device at the insertion time (if not flagged the mount has to be executed explicitly)
Log in as domain user
: in a thin client joined to a domain will use the domain
Page 39 of 49
Windows Embedded User Guide
Log in as domain user
: in a thin client joined to a domain will use the domain credential to connect to Horizon View server
User name
: use the inserted user name to start the connection (if it is specified cannot be changed afterwards by the user)
From the "Connection Manager" under "VMware" tab it is possible to configure the behaviour when connecting using SSL protocol. Near the "Connect" button click on "Configure SSL" sting.
The certificate checking mode can be selected from:
"Never connect to untrusted servers" and "Warn before connecting to untrusted servers" will not accept to connect to server not trusted by certificates,
"Do not verify server identity certificates" will accept to connect to untrusted servers.
When the connection is executed it launch the VMware Horizon View client with the parameters specified in the configuration window.
2.6.4 Managing URL/Link Connection
From the "Connection Manager" window select the "URL/Link" tab.
An URL/Link connection allows to define an URL Address or a directory pathname that will be opened when the connection starts.
When a URL/Link connection is created the window above is opened.
In the field you can insert the URL (e.g. as above "http://www.praim.com") or also a pathname
Page 40 of 49
Windows Embedded 2.1.2 Guide
In the field you can insert the URL (e.g. as above "http://www.praim.com") or also a pathname to a directory (e.g. "C:\data").
Clicking on "Test your URL" will open the default internet browser pointing to the URL or the
Windows explorer pointing to the directory so it is possible to verify the URL/Link inserted in the connection.
When the connection is launched it will open the default internet browser or the Windows explorer pointing to the URL/Pathname specified. With the "Auto-Run" parameter flagged it can be useful to launch automatically an internet browser which link to a specific page when the thin client is powered on.
2.6.5 Managing Citrix Receiver Connection
The Citrix connection is different from other connections. It need that you configure server and options using the Citrix Receiver user interface. Refer to Citrix documentation on how to configure Citrix Receiver.
After the Citrix Receiver is properly configured open the "Connection Manager" window and select the "Citrix" tab.
Flag the "Deliver Citrix Receiver settings" option to manage the current Citrix Receiver configuration inside the Praim Connection Manager. This operation copy the current Citrix
Receiver configuration into the Connection Manager configuration. The time-stamp of the operation is shown on the "Settings date".
Whether the Citrix receiver configuration is changed you have to click on "Import Citrix
Page 41 of 49
Windows Embedded User Guide
Whether the Citrix receiver configuration is changed you have to click on "Import Citrix settings" to reload the changed parameters into the Praim Connection Manager configuration.
In this case remember to re-load the configuration from the ThinMan Server.
Page 42 of 49
Windows Embedded 2.1.2 Guide
3 Device Administration
This chapter provides detailed information about the device administration that can be made via ThinMan Console.
It discusses:
Installing Praim Service Pack and Hotfix (see page 44)
Backup, Restore and Device Cloning (see page 45)
Using ThinMan to Remote Assistance a thin client (see page 47)
Page 43 of 49
Windows Embedded User Guide
3.1 Installing Praim Service Pack and Hotfix
A Praim thin client can be updated using two different type of file:
Service Pack
Hotfix
Note
To download a Praim Service Pack or Hotfix register yourself on the http://www.praim.com
site.
A Service Pack is a software that allows to upgrade the thin client firmware from a specific version to the next available version (e.g. "PraimServicePackWE7_1.3.0(1.2.1).exe" will upgrade the thin client firmware from version 1.2.1 to version 1.3.0). If a Service Pack is executed on the wrong firmware it will not produce any effects and the firmware will remain untouched.
A Hotfix is a part of a Service Pack. A Hotfix installed on a specific version will leave the version number unchanged. Hotfix may be suggested from Praim Support people to fix a specific feature on the thin client.
The software upgrade (Service Pack or Hotfix) can be installed in two different ways: manually on the thin client (using or copying the installation file from a USB Mass Storage key/disk or from a shared directory on the network) using the features offered by the ThinMan (see ThinMan Guide for the latest available documentation, in this case the installation file has to be available on the ThinMan
Server)
In both cases pay attention that at the end of the installation a commit will be executed on the thin client. This operation will save all the changes done until that moment, not only the changes done to the installation file, but also all the changes made from the last reboot. A good practice to avoid this and to maintain a clean installation is to reboot the thin client and execute the upgrade accordingly.
Depending on the ThinMan Server license you will be able to perform the upgrading process in different ways: manually one device at a time manually on multiple device automatically and scheduled at specific time automatically and depending on thin client event (e.g. upgrade on thin client startup)
Refer to the ThinMan Guide for specific instructions.
Page 44 of 49
Windows Embedded 2.1.2 Guide
3.2 Backup, Restore and Device Cloning
You can save a backup copy of a Windows Embedded (WES7 or XPe) device in order to restore the same device. Another option is to save a copy in order to clone the device firmware and its configuration on other devices. You can also use a factory firmware image to restore the thin client as it were out-of-the-box.
ThinMan allows to execute these operations over the network using the PXE Boot. Consult the
ThinMan Guide under the "Object Contextual Menu" paragraph in order to backup, restore or clone a device. This operation is possible only when the network gives DHCP address to the thin clients.
TIP
Because this operation is based on broadcast messages be sure that all network infrastructure support broadcast messages. It these prerequisites are not met (e.g.
typically in WAN environment) it is better to use the Praim Toolkit software to generate
USB Mass Storgae key for recovery (see below).
Another tool that allow to execute the same operations using a USB Mass Storage key is the
Praim Toolkit software. Consult the Praim Toolkit Guide for detailed instructions on how to create a USB Key. When ready the USB Key inserted in the thin client will rewrite down the entire DOM (Disk on Module) with a new firmware.
Pay Attention
Using a backup copy to execute a cloning will produce unwanted results. In this case the new thin client is an exact copy of the first one (it means, the same hostname, same ip address (if static), etc.) and this will conduct to possible problems in network.
Use a copy for backup only to restore the same thin client.
Page 45 of 49
Windows Embedded User Guide
Restore a device with cloning backup only after it has contacted the ThinMan
Server
If you plan to clone a device to a new one, let the new thin client contact ThinMan for al least one time. Doing so the ThinMan will save the Microsoft license of the thin client and, after the thin client is restored, it will give back the correct license to the thin client. If the ThinMan did not save the license you are requested to provide a correct license on the thin client startup (in this case you have to contact the Praim Support team).
This suggestion is really important especially if you are restoring a device using a USB
Mass Storage key created by Praim Toolkit software.
All these operations (backup, restore and cloning) will involve a lot of data. The DOM (Disk on
Module) mounted on the device may vary from 1 GB to 8 GB of data. All these data need to be transferred using the LAN, whether you are using ThinMan, or using the USB Key. Pay attention to which procedure you will use because the duration will depend on how much data you are transferring and can be very long, especially in networks with low bandwidth availability.
Depending on this factors you may decide, for example, that is convenient to prepare and configure a single thin client and then copy all its DOM to others to have all the thin client aligned. Other possible options is, instead, to prepare a single installation file and then to propagate it to all the thin clients using the ThinMan feature "Third party software installation".
It depend on many parameters like network speed, possibility of physical access to the thin client, number of devices to update, complexity of the installation files and so on.
Page 46 of 49
Windows Embedded 2.1.2 Guide
3.3 Using ThinMan to Remote Assistance a thin client
From ThinMan Console it is possible to shadow the thin client desktop via the Remote
Assistance menu.
See ThinMan Guide in the "Object Contextual menu" paragraph for more detailed information on how to start the Remote Assistance connection.
You can change the thin client configuration for the ThinMan Assistance, see
ThinMan Remote Assistance (see page 20)
for detailed instructions.
This feature uses a VNC protocol on port 5900 of the thin client. Be sure that network allows this port and protocol.
Page 47 of 49
Windows Embedded User Guide
4 How To
How to enable execution of *.ps1 file (Powershell) on the thin client (see page 49)
Page 48 of 49
Windows Embedded 2.1.2 Guide
4.1 How to enable execution of *.ps1 file
(Powershell) on the thin client
Execute Powershell using "Run as Administrator" option in right click menu.
Type "Set-ExecutionPolicy unrestricted" in the window and press "Enter".
It will ask to confirm the operation, type "y" to confirm.
The thin client is ready to execute powershell scripts.
Page 49 of 49
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project