STFU && RTFM

This error message has had me running around for a while now. Some of my users are part of the salesforce, running SAP Mobile Sales on Windows XP computers with Microsoft SQL Server. It’s a big and complicated setup, but it has been running stably for years now. The problem only occurred with users running recently set up computers, and only on a specific model.
 
Naturally, this had me thinking the problem was hardware. I even went so far as to upgrade a user from a lower spec model computer to a higher spec model. That actually solved the problem, though it wasn’t the solution. Seeing more users report the same error, I concluded that the problem was unlikely to be a problem with a specific model, as most of them had different model computers.
 
Using most support tech’s best friend, Google, I browsed for the error message (easier said than done, as the computers are set up with a Norwegian edition of Windows XP), and finally found the solution I was after. It was contained in an official Windows XP knowledgebase article; number 909095.
 
Like most enigma, once a solution has been found, the story rather fizzles out. So, luckily, too with this one. The knowledge base article referred me to a specific update, and having installed that update, the problem disappeared.

Note: The comment-function for this post has been disabled due to 200+ spam comments over the last 24 hours Lately, I’ve been annoyed that a few of the computers I’ve set up have had NumLock on after each and every boot. The problem lies somewhere in the installation scripts, I’m sure, but as I have no power over those scripts, all I can do, is fix the problem whenever I spot it.
 

1. Open the “run” dialog box, enter regedit, and click ok
2. Find the following key: HKEY_USERS\.DEFAULT\Control Panel\Keyboard\InitialKeyboardIndicators
3. Set the value of the key in accordance with the following table

I had a user call in, complaining that her “Show Desktop” icon had disappeared from the Quick Launch bar. She was unable to find it again, and was really distressed as she used it a lot.
 
As it turns out, Show Desktop is not a regular program, but rather an OS command, known as an SCF-file, which according to FileInfo.com is a

Command used by Windows Explorer; for example, to move up or down a directory or show the Desktop; run via Internet Explorer.

 
The solution was simple enough, even though I would recommend that you implement it yourself rather than have a non-technical user implement it. Solving the problem goes as follows:
 

1. Open notepad
2. Enter the following in notepad:
   [Shell]
Command=2
IconFile=explorer.exe,3
[Taskbar]
Command=ToggleDesktop

Save the file as “Show Desktop.scf” in the folder C:\Documents and Settings\username\Application Data\ Microsoft\Internet Explorer\Quick Launch

As previously reported, Windows XP with Service Pack 3 has a nasty tendency to cause people to be unable to uninstall software such as Internet Explorer 7 and Internet Explorer 8.
 
What I didn’t know, was that it doesn’t confine itself to blocking uninstall of these programs, but that it also blocks the uninstall of, for example, Lotus Notes.
 
I even got an error message; this one, to be exact: “The Windows Installer Service Could Not Be Accessed”
 
It would seem that Service Pack 3 actually blocks software from accessing the Windows Installer Service. The solution, then, is to uninstall Service Pack 3. After I did that, I could uninstall Lotus Notes.

The next version of Microsofts Internet Explorer is currently in public beta. Many of the beta testers are reporting that they are unable to uninstall the beta. The reason? They are running Windows XP SP3.
 
Now, you can still uninstall IE8, it just takes a little more time, and effort. The first step to doing so is uninstalling SP3, which in turn should allow you to uninstall IE8.

I love using command line tools, especially for troubleshooting networking. There are two simple commands you need to know; ipconfig and ping. Here’s a simple guide to finding where the problem :
 

1. Open the command line by opening the “run” dialog box, entering cmd and clicking OK
2. Ensure that the TCP/IP service is running by pinging the loopback address like so: ping 128.0.0.1
3. Run the ipconfig command, which should give you information something like this:

IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

4. If your address is not an APIPA address, ping your IP-address.
5. Ping the default gateway
6. Ping www.iana.org
7. Ping the website or server you are trying to reach

 
If any of the above tests fail, you’ve found where the problem is.

I’m sure you know the problem: you’ve used someone elses computer, and want to remove your traces. One of the easiest ways of doing that is to use the DiskCleanup utility, however locating it isn’t exactly the easiest thing.
 
Luckily, it’s pretty simple to initiate the utility from the Run dialog; simply enter the program name, cleanmgr.exe and hit “OK”, and there you go.

One of my favorite features in Windows Vista is the very usable breadcrumb address bar as seen below. What I love about it is that it simplifies navigation back to a folder higher in the hierarchy. In addition it visualises the path to the folder really well.
 

 
I wanted to get this in Windows XP as well, and, as it turns out, there’s an app called QT Address Bar that does this for you. It’s a shell extension that gives you the same functionality in Windows XP. There’s a little bit of post-config involved, but don’t worry, here’s how to do it:
 

1. First off, download QT Address Bar
2. Unzip it, and run the installation
3. Log off Windows, and then back on
4. Open the explorer, then go to View > Toolbars
5. Activate QT Breadcrumbs Address bar
6. Deactivate the toolbar lock and the regular address bar
7. Move the QT Address bar so that it is where you want it

 
Next, what you’ll want to do is have it displayed no matter what folder you open. Here’s how:
 

1. In the folder that you enabled QT Address bar, go to Tools > Folder Options
2. Go to the View tab
3. Click the “Apply to All Folders” button



4. Acknowledge the prompt

 
That’s it, you’re done. Here’s what it looks like:
 

I rarely write posts off the cuff, but this warrants it. Microsoft has released Security Bulletin MS08-059, along with a hotfix for the problem detailed. There are already exploits in the wild to take advantage of the hotfix.
 
What I ask is simply this: Update your computer. Run Windows Update, and update your computer.
 
Here’s the bulletin from Microsoft:
Bulletin Identifier – Microsoft Security Bulletin MS08-059
Bulletin Title – Vulnerability in Host Integration Server RPC Service Could Allow Remote Code Execution (956695)
Executive Summary – This security update resolves a privately reported vulnerability in Microsoft Host Integration Server. The vulnerability could allow remote code execution if an attacker sent a specially crafted Remote Procedure Call (RPC) request to an affected system. Customers who follow best practices and configure the SNA RPC service account to have fewer user rights on the system could be less impacted than customers who configure the SNA RPC service account to have administrative user rights.
Maximum Severity Rating – Critical
Impact of Vulnerability – Remote Code Execution
Detection – Microsoft Baseline Security Analyzer can detect whether your computer system requires this update. The update may require a restart.

I was called out to help with a problem that had stumped a few of our more experienced techs. The problem was that a user was unable to use her Mobile Broadband USB device.
 
The specific device we use is supplied by one of the major norwegian telecoms, Telenor. It is a Globetrotter HSDPA USB dongle. The nifty thing about it is that it is totally plug and play. It installs itself, with drivers and connection software, when plugged in.
 
The problem occurs when the install goes wrong. By default, the dongle installs itself set to use the first two consecutive COM ports available for uplink and downlink respectively. The solution to my clients problem was simply to change what ports the dongle used, followed by a restart.
 
Here’s how you implement the solution:
 

1. Open Computer Management
2. Go to Device Management, then go to Ports (COM and LPT)
3. Open the properties for the Port, then go to the Port Settings tab
4. Click Advanced
5. Change the port number
6. Save your settings, then reboot