Kbase 18341: Metaframe and Terminal Server Installation Notes
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/11/2009 |
|
Status: Verified
GOAL:
How to install Progress on Citrix MetaFrame and Microsoft Windows Terminal Server
GOAL:
Installation Notes for Windows NT Terminal Server Edition with Citrix MetaFrame 1.x
FACT(s) (Environment):
Progress 8.x
Progress 9.x
Citrix MetaFrame 1.0
Citrix MetaFrame 1.8
FIX:
To prepare the ini-mapper for an installation, a command prompt should be opened (and stay open during the installation). Type the following:
C:\CHANGE USER /INSTALL
then run the installation program for the Progress version that should be installed. When this has finished type, at the same command prompt:
CHANGE USER /EXECUTE
This sets the system to execute mode, and the ini-mapper stops it's recording of changes done to the registry.
Windows Client tuning (prowin32.exe):
Some applications constantly look for keyboard input even while they appear to be doing nothing, thereby consuming system CPU usage. MetaFrame has built-in logic to detect this behavior.
When the type of behavior is detected, the application's execution is suspended in order to allow other applications to use the CPU.
In order to avoid having Progress applications suspended and to allow them to use more of the CPU resources, you must change the compatibility bits.
For WinFrame the compatibility bits are stored in:
/HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\Applications\ prowin32
For MetaFrame they are stored in:
/HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\
TerminalServer\Compatibility\Applications\prowin32
NOTE: After you install Progress, there are no such entries in this Registry key. You must manually create them if you want to perform tuning. A copy of these values is in the .\Compatibility\Applications\SETUP key. With the SETUP subkey highlighted:
1) Select Save Key from the Registry menu.
2) Create a subkey for PROWIN32. The extension (.exe) is not used.
3) Highlight the Application subkey.
4) Choose Add Key on the Edit menu.
5) To copy the values from the SETUP subkey, select your new subkey PROWIN32 and choose Restore from the Registry menu.
6) Choose the filename you created.
The following are descriptions of the Registry entry components:
- FirstCountMsgQPeeksSleepBadApp
The number of times the application monitors the message queue before it decides that it is ill-behaved. Decreasing this value puts the application to sleep more often so it uses less CPU time.
- MsgQBadAppSleepTimeInMillisec
The number of milliseconds the application is put to sleep once it is determined that it is ill-behaved. Increasing this value causes the application to use less CPU time.
- NthCountMsgQPeeksSleepBadApp
The number of times the application monitors the message queue after it is determined that it is an ill-behaved application for it to be put to sleep again. Decreasing this value causes the application to use less CPU time.
- Flags
Control the type of application to which the bad application flags apply.
0x8 for 32-bit applications only
0x4 for 16-bit applications only
0xC for both 16- and 32-bit applications
- Settings
If MsgQBadAppSleepTimeInMillisec value is zero, polling detection is disabled. Set this value to zero and the Flags to 0x8 to get better performance. Do this for all executables. Currently the most used executables are:
PROWIN32
_MPROSRV
_PROGRES
PRORE32
PRORB32
_PROAPSV
PROCTRL
But in theory, each .exe file could be registered because it most likely improves performance.
**These Registry entries are not used with Windows 2000 Terminal Server.
This completes the installation and after a reboot everything should work.