Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 272707 - Last Review: December 3, 2007 - Revision: 4.8
Visual Studio products are not supported on Windows NT 4.0 Terminal Server
This article was previously published under Q272707
SUMMARY
Visual Studio and the products that are contained in Visual
Studio have not been tested and are not officially supported when you run them
in a Terminal Server client session using Terminal Server on Windows NT
4.0.
Visual Studio .NET and Visual Studio 2005 products are not supported on WinNT 4.0
Terminal Server. They are supported on NT 4.0 with Service Pack Pack 6a and
Windows 2000 Terminal Server or later.
Visual Studio 6.0 is supported
on Microsoft Windows 2000 Terminal Services.
The system requirements
for Visual Studio 6.0 are:
- Microsoft Windows 95 or later -or-
- Windows NT Workstation 4.0 (Service Pack 3 recommended) or
later -or-
- Windows 2000
The system requirements for Visual Studio 97 are:
- Windows 95 or later -or-
- Windows NT Workstation 4.0 (Service Pack 2 recommended) or
later -or-
- Windows NT Workstation 3.51 with Service Pack 5
MORE INFORMATION
Terminal Server is available on Windows NT 4.0 Terminal
Server Edition. Windows Terminal Services are also on Windows 2000 Server and
Advanced Server. Terminal Server/Terminal Services allows a Windows Server to
act as a terminal server for multiple, simultaneous client sessions. Although
you can successfully install and run Visual Studio on a terminal client, the
behavior of Visual Studio in this environment is not guaranteed on Windows NT
4.0 Terminal Server Edition.
Various problems have been reported in
this environment. For example, after you install Visual Studio 6.0 on Terminal
Server, you cannot open the Help system. If you press the F1 key to access Help
in a Visual Studio product, such as Visual C++, a Help System dialog box
appears with the following error message:
Attempting to
use an invalid help file
These issues are moot if you are using Windows Terminal Services,
which are available on Windows 2000 Server and Advanced Server.
During the installation of Visual Studio .NET or Visual Studio 2005, the Windows
Component Update may prompt you to update Windows NT 4.0 Terminal Server to
Service Pack 6a, even though Service Pack 6a does not exist.
Visual
Studio .NET and Visual Studio 2005 are not supported on Windows NT 4.0 Terminal Server, only on Windows
2000 Terminal Server or higher.
REFERENCES
For additional information, please see the following
articles in the Microsoft Knowledge Base:
Visual Studio
195878Â
(http://kbalertz.com/Feedback.aspx?kbNumber=195878/EN-US/
)
PRB: MSDN Help Cannot Find msdn*.col File on Terminal Server
240302Â
(http://kbalertz.com/Feedback.aspx?kbNumber=240302/EN-US/
)
PRB: MSDN Library Setup Fails on Terminal Server in Execute Mode
240301Â
(http://kbalertz.com/Feedback.aspx?kbNumber=240301/EN-US/
)
HOWTO: Use the MSDN Library Successfully with Terminal Server
232060Â
(http://kbalertz.com/Feedback.aspx?kbNumber=232060/EN-US/
)
HOWTO: MDAC Setup Troubleshooting Guide
Visual Basic Specific
196201Â
(http://kbalertz.com/Feedback.aspx?kbNumber=196201/EN-US/
)
INFO: Visual Basic Is Not Supported on Terminal Server 4.0
194776Â
(http://kbalertz.com/Feedback.aspx?kbNumber=194776/EN-US/
)
HOWTO: Install a Visual Basic Application on Terminal Server
Visual C++ Specific
272755Â
(http://kbalertz.com/Feedback.aspx?kbNumber=272755/EN-US/
)
INFO: Visual C++ Is Not Supported on Terminal Server 4.0
200983Â
(http://kbalertz.com/Feedback.aspx?kbNumber=200983/EN-US/
)
HOWTO: How to Install Visual C++ on Terminal Server
Visual FoxPro
272756Â
(http://kbalertz.com/Feedback.aspx?kbNumber=272756/EN-US/
)
INFO: Visual FoxPro Is Not Supported on Terminal Server 4.0
219956Â
(http://kbalertz.com/Feedback.aspx?kbNumber=219956/EN-US/
)
PRB: Too Many Files Open Running VFP on Windows Terminal Server
258537Â
(http://kbalertz.com/Feedback.aspx?kbNumber=258537/EN-US/
)
FIX: CONFIG.FPW Setting for Terminal Server Environment
268558Â
(http://kbalertz.com/Feedback.aspx?kbNumber=268558/EN-US/
)
Visual FoxPro on Terminal Services Cannot Start Two Wizards
249716Â
(http://kbalertz.com/Feedback.aspx?kbNumber=249716/EN-US/
)
HOWTO: Use NetRemoteTOD to Obtain Date/Time Info from a Server
Visual InterDev
272758Â
(http://kbalertz.com/Feedback.aspx?kbNumber=272758/EN-US/
)
INFO: Visual InterDev Is Not Supported on Terminal Server 4.0
256197Â
(http://kbalertz.com/Feedback.aspx?kbNumber=256197/EN-US/
)
PRB: Visual InterDev 6.0 Debugging Fails Under Terminal Server
APPLIES TO
- Microsoft Visual C# .NET 2003 Standard Edition
- Microsoft Visual C++ .NET 2003 Standard Edition
- Microsoft Visual Basic .NET 2003 Standard Edition
- Microsoft .NET Framework 1.1
- Microsoft .NET Framework Software Development Kit 1.0 Service Pack 2
- Microsoft Visual Studio .NET 2003 Enterprise Architect
- Microsoft Visual Studio .NET 2003 Enterprise Developer
- Microsoft Visual Studio .NET 2003 Professional Edition
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft .NET Framework 1.0
- Microsoft Visual Studio 6.0 Enterprise Edition
- Microsoft Visual Studio 97 Service Pack 3
- Microsoft Visual Basic 5.0 Learning Edition
- Microsoft Visual Basic 6.0 Learning Edition
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
- Microsoft Visual Basic .NET 2002 Standard Edition
- Microsoft Visual C# .NET 2002 Standard Edition
- Microsoft Visual C++ 5.0 Enterprise Edition
- Microsoft Visual C++ 6.0 Enterprise Edition
- Microsoft Visual C++ 5.0 Professional Edition
- Microsoft Visual C++ 6.0 Professional Edition
- Microsoft Visual C++ .NET 2002 Standard Edition
- Microsoft Visual FoxPro 5.0 Standard Edition
- Microsoft Visual Studio .NET 2003 Academic Edition
- Microsoft Visual FoxPro 6.0 Professional Edition
- Microsoft Visual FoxPro 7.0 Professional Edition
- Microsoft Visual J++ 1.0 Standard Edition
- Microsoft Visual J++ 6.0 Standard Edition
- Microsoft Visual InterDev 1.0 Standard Edition
- Microsoft Visual InterDev 6.0 Standard Edition
- Microsoft Visual Studio .NET 2002 Enterprise Architect
- Microsoft Visual Studio .NET 2002 Enterprise Developer
- Microsoft Visual Studio .NET 2002 Professional Edition
- Microsoft Visual Studio .NET 2002 Academic Edition
- Microsoft Visual SourceSafe 6.0C
- Microsoft Visual FoxPro 3.0 Professional Edition
- Microsoft Visual J# .NET 2003 Standard Edition
- Microsoft Visual Studio 2005 Professional Edition
- Microsoft Visual Studio 2005 Standard Edition
- Microsoft Visual C++ 2005 Express Edition
- Microsoft Visual C# 2005
- Microsoft .NET Framework 2.0
| kbvs2005applies kbvs2005swept kbhowto kbconfig kbinfo kbserver kbsetup kbsyssettings KB272707 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please