Windows 2000 post SP4 fixes etc
There are many issues with Microsoft Service Pack 4 and Terminal Services in Application mode and it's getting more worse with Citrix MetaFrame. Make sure you have check out this site BEFORE you apply Service Pack 4!
Also the mainstream support for Windows 2000 has ended in 2005, that means you have to pay for Windows 2000 HotFixes if you don't have an extended HotFixes support or other contract with Microsoft.
| | Main links regarding Service Pack 4 issues:
- Unable to Connect with ICA After Installing Microsoft Rollup 1 for Windows 2000
- Citrix MetaFrame XP or Citrix MetaFrame Presentation Server 3.0 do not work as expected after you install Update Rollup 1 on a Windows 2000 SP4-based server
Here the regfile Sp4rufix.reg for the workaround if you don't need SmartCard funtions.
Terminal Services and / or Citrix related:
- Windows Terminal Server Client Cannot Connect to the Terminal Server
- Terminal services and remote desktop session events are not logged in Windows 2000 Server
- An event that is logged in the Security log does not in include the IP address or the computer name of the Terminal Services client
- Several orphaned Csrss.exe processes cause performance issues on your Windows 2000-based terminal server
- You may receive an error in the Userinit.exe component when you log on to a Windows Server 2003-based or a Windows 2000-based Terminal Services session
- The Print Spooler service stops frequently, Dr. Watson logs an error message, and Event ID 7031 is logged in Windows 2000 Server or Windows Server 2003.
- A Terminal Services session to a Windows 2000-based computer stops responding if a user logs off after the user quits a 16-bit Windows program
- The Terminal Services desktop is blank when you log on to a remote Windows 2000-based computer.
- You cannot establish a remote session to a Windows 2000 Server-based computer that is running Terminal Services.
- Folder names do not update when you run Explorer.exe as a published application in a Citrix Metaframe XP session on a Windows 2000-based Terminal server
- You may receive a "Stop 0x0000001E (0xc0000005)" Stop error message when the Rdpdd.dll function in Windows 2000 Terminal Services receives a null value
- Stop Error Code 0x1E Occurs If Your Server Has Terminal Server Enabled
- Intermittent "Stop 0x1E" Error Message
- You cannot establish new Terminal server sessions and Windows 2000 slowly stops responding.
- The screen saver does not start in a Windows 2000 Terminal Services console session
- The CPU (%) column in Task Manager is not updated during a Windows 2000 Terminal Services client session
- You cannot reconnect to a disconnected Windows 2000 Terminal Services client session when the user password contains more than 14 characters
- Non-Admin Windows 2000 Users Cannot Create Global Objects by Using Terminal Services
- The HOMEDRIVE, HOMEPATH, and HOMESHARE environment variables may not function as you intend if you modify them in Windows 2000
- Roaming profiles are not saved when a user logs off a Microsoft Windows 2000-based computer or a Microsoft Windows XP-based computer
- HP Color LaserJet printer prints only in grayscale or in black-and-white on your Windows 2000 SP4-based computer
- You receive a "Stop 0x0000001E" error message when you log off from a Windows 2000 Server terminal server
- STOP: 0x0000001E" error message on a Windows 2000-based computer that is running Terminal Services
- You cannot connect to a Windows 2000 Terminal server if your Windows Server 2003 Terminal Services license is expired
- High processor usage from the spooler occurs when a user logs off from a session on a terminal server that is running Windows Server 2003 or Windows 2000
- Windows 2000 Terminal Server stops responding after you experience access violations in a Terminal Server session
- Obtain the Dskcache.exe Tool to Configure the "Power Protected" Write Cache Option
- Error Message Occurs When You Try to Connect to a Server by Using a Remote Access Connection
- You receive an "0x0000001E (KMODE_EXCEPTION_NOT_HANDLED)" error message on a Windows 2000 Server that is running Terminal Services
- Because of a Security Error, the Client Could Not Connect to the Terminal Server
- Windows Installer package does not install correctly on a Windows 2000-based server that is running Terminal Services in Application Server mode
- Clients cannot connect to a Terminal server when Csrss.exe and Termsrv.exe spike at 100 percent CPU usage
- Thread in the Csrss.exe process consistently uses 25 percent of the CPU on your Windows 2000 Server.
- The Terminal server does not automatically shut down when the TSShutdn.exe command is invoked in Windows 2000
Some Windows 2000 Hotfixes May Cause a Conflict with Service Pack 4 for Windows 2000
- You receive a "stop 0x00000050 (page fault in nonpaged area)" error message when you reconnect to a terminal server that is now using a different color depth
- Windows 2000 may take a long time to start up and Terminal Services may be in an incorrect state
- You receive an error message when you try to print to a shared network printer in a terminal server session
- Error 161 occurs when you access Service Control Manager from Terminal Services.
- "STOP 0x000000C2" Error Message When Running Terminal Services
- Windows Explorer Repeatedly Quits and Then Restarts with Access Violation Errors in Terminal Services
- You Experience Performance and Logon Problems When You Use Terminal Services
- "Windows Cannot Unload Your Registry Class File" Error Message When You Log Off Terminal Service
- It takes longer than you expect to log off from a Terminal Services session in Windows 2000
- Documents from Terminal Server Users Who Map LPT1 to Different Printers Appear on the Same Printer
- "Not Enough Memory" Error Message When You Search for Clips in an Office XP Document During a Terminal Services Session
- Stop 0x1E Error in Mup.sys After You Apply Windows 2000 SP4
- Very Long Logon Time When You Try to Connect to Citrix MetaFrame or Citrix 1.8
- Roaming Profiles Are Not Unloaded on a Computer That Is Running Terminal Services When GPOs Are Applied (IE 5.5 SP1)
- Roaming Profiles Are Not Unloaded on a Computer That Is Running Terminal Services (IE6)
- Windows 2000 Terminal Server Stops Responding and a Black Screen Appears
- Windows Sends Your Old Password to a Third-Party Network Provider When You Change Your Password While You Log On
- Spooler Failure Causes High CPU Usage in the Winlogon.exe and Spoolsv.exe Processes on a Windows 2000 Terminal Server
- A Windows 2000 Terminal Server That Is Configured with Citrix Metaframe Software Can Become Slow and Unresponsive
- Citrix Terminal Server Sessions Are Not Disconnected and Cause the Server to Stop Responding
- Errors Occur When You Use a .NET Framework 1.0-Based Program on a Windows 2000 Service Pack 4-Based Terminal Server
- A Computer May Lose Network Connectivity Under High Stress
- Problems When More Than One User Accesses the Same File Through Terminal Services
- Terminal Server and Connected Terminal Services Clients Pause When a Terminal Services Client Logs On or Logs Off
- You Cannot Save Printing Preferences
- Terminal Services Licensing Denies Your Connection to Your Terminal Server from Your WBT Device
- Terminal Services Stops Responding
- Dr. Watson Error Occurs When You Run a Program That Uses Utildll.dll
Last Updated ( Tuesday, 28 February 2006 )