Windows Aero is the graphical user interface and the default theme in most editions of Windows Vista and Windows 7
operating systems released by Microsoft. This user interface is very resource intensive, change the desktop theme to the 10ZiG Technology theme which does not use Windows Aero.
Right click on the desktop and go to personalize - set the theme to 10ZiG Technology.
Please refer to this article but multiple monitors is only supported when you connect to the OS Windows Ultimate or Enterprise 7.
Windows professional or home will not support multiple monitors. This is the operating system you are connecting to not the thin client.
This temp profile issue can cause missing ICONS on the desktop and loss of Windows 7 customized settings. Restarting or logging off and back on to Windows 7 does not resolve the issue.
This temp profile issue rises because of a registry key problem.
To fix the Temporary Profile in Windows 7 Issue follow the steps below:
Log in with temp profile.
Start registry editor by typing regedit in find box in Windows 7.
Navigate the following location in Windows 7.
You will see similar keys under profile list with .bak difference, as shown below.
The correct profile key is marked as bak. Currently your Windows 7 computer logged in with fresh profile with same key.
So, rename the new profile key ( without extension .bak) and remove .bak from correct profile key. See below.
Log off and back on with user name and password. You should get your icons and profile settings back in Windows 7.
By default the 10ZiG Win 7 thin clients come with the RemoteFX USB redirection feature enabled.
To turn off RemoteFX redirection, the RemoteFX USB redirection feature must be disabled.
Select Start - Run - gpedit.msc and select OK. In Group Policy, navigate to Computer
Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Connection Client\RemoteFX USB Device Redirection,
and edit “Allow RDP redirection of other supported RemoteFX USB devices from this computer.” Disable the policy. Select OK and reboot the thin client.
Using the RemoteFX USB redirection feature:
On the client, open Remote Desktop Connection. If the tabs are not listed, click Options to expand the dialog box.
On the Local Resources tab, click More to display the Local devices and resources dialog box. If at least one supported RemoteFX USB device is connected,
it should be listed in the device tree under Other supported RemoteFX USB devices.
Note: The heading “Other supported RemoteFX USB devices” will only appear if the RemoteFX USB redirection feature is enabled on the client
and at least one supported RemoteFX USB device is connected and available for redirection.
Yes it will work. The problem that still exists is that when you do a warm boot (restart) the fourth monitor does not come up, however if you power down completely
and then do a cold boot or a normal power up the fourth monitor will initialize.
There are a couple of issues with Touch Screens in WES 7
If the touch screen requires a driver and does not take advantage of the native dll’s in Windows 7’s tablet pc support then it will work.
For example the DT Tablet 312 & 362 use the Penmount driver which works in WES 7.
If the touch screen does not require a driver, it will not work in our build of WES 7 even if the touch screen works in Windows 7.
There is a component called Tablet PC support in Windows 7 and one of its functions is to provide touch screen support. This component cannot be put into the 10ZiG Technology WES 7 image because
it requires a higher license.
ELO Touch Screens will not work in 10ZiG Technology WES 7 builds. We are checking with ELO to see if all models require this component and if they do, ELO will only work in XPe.
Once we have a better understanding as to which Touch Screens will work with WES 7 we will provide a list of recommended touch screens.
The reason why this occurs is that domain and PC exchange a secret key behind the scenes and the default time limit on this exchange is 30 days.
When EWF is enabled and the PC gets rebooted and the change that has occurred is not saved in the registry. The work around for this is:
Go to key