Saturday, August 28, 2010

Confusing Error Messages – Ntoskrnl.exe missing

It can be confusing when an error message does not clearly describe a problem. We’ve seen this with all types of software, not just Microsoft or Apple products. Here’s an example we came across recently:

Windows could not start because the following file is missing or corrupt:


Please reinstall a copy of the above file.

This is usually the result of a missing or corrupt boot.ini file. The Ntoskrnl.exe file is most likely on the disk, however the system can’t see it because it can’t find the hard disk during the boot up process.

The fix is to boot the PC into the Recovery Console and do the following:

  • Type bootcfg/rebuild (enter)
  • When asked “Add installation to boot list? (yes/no/all), type y
  • When asked to “Enter Load Identifier:”, enter the name of the OS, such as Windows XP Professional
  • When asked to “Enter OS Load options:”, press enter and restart the computer.

Saturday, August 21, 2010

The Terminal Service Gateway may randomly disconnect machines

This MS knowledge base article was brought to our attention by Susan Bradley's excellent blog. If you're experiencing this issue, you may want to try the tweaks recommended in the post.

Saturday, August 14, 2010

Not Enough Memory Available Message When Opening Outlook PST

After successfully repairing a large PST file, we saw this message appear in Outlook 2007. The folks at Microsoft PSS helped us troubleshoot this with the following suggestions:

- Check the permissions of the PST file; ensure the user has full permission of the file

- Configure the antivirus software not to scan PST files

- Check the amount of available disk space on the computer

- Check the file on another client PC; if the file opens properly, rerun scanpst.exe on the PST file

We found the amount of disk space was extremely low, preventing Windows from creating the virtual memory needed to proceed. Once we freed up disk space, we were able to open the PST file again.

Saturday, August 7, 2010

Remote Desktop Client Changes Default Printer in Terminal Server and Remote Desktop Server

The Remote Desktop Client redirects the local printers by default. This is done so the user can send a print job from the Remote Desktop Server or Terminal Services Server to a printer connected to their PC. When the user logs in, the default printer is automatically changed so the user’s redirected printer is now the default.

In certain instances, you may want not want the redirected printer as the default. To change this behavior, enable the Group Policy “Do not set default client printer to be default printer in a session” under Computer Configuration – Policies – Administrative Templates – Windows Components – Terminal Services – Terminal Server – Printer Redirection.