Article ID: 214500 - View products that this article applies to.
This article was previously published under Q214500
This article has been archived. It is offered "as is" and will no longer be updated.
Normally, an administrator can use the registry to set compatibility flags for specific applications being run on Windows Terminal Clients. For example, adding the following registry key and value to HKEY_LOCAL_MACHINE on the Terminal Server will force the application, in this case NTVDM, to use the Terminal Server's Windows System folder, instead of the user's Windows folder:
Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\ KEY: NTVDM VALUE: Flags reg_dword 0x400
This setting can be used to force all applications running within NTVDM to use the _Default.pif file on the server for custom settings, rather than requiring the administrator to copy the _Default.pif file to the Windows folder of each user.
After you add the Application Compatibility Flag to the registry, the application does not respond to the flag.
For additional information, see the following article or articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/186499/EN-US/ )Terminal Server Registry Settings for Applications
The system does not correctly retrieve the application name. Therefore, the application compatibility flag in the registry is not found.
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Contact us for more help