HP tc4400 and Windows 7 Boot Failure

I've been using an HP tc4400 Tablet PC with Windows Vista for quite some time now and thought it was about time I started using Windows 7 for work and not just home.

Don't get me wrong, I do like Vista (I think I may be only one of eight people), but as an IT professional I should be using the latest operating system.

So I got started with swapping out the hard drive to start with a fresh install (always the best way to go), and tossed in the install DVD. The install went flawlessly and I followed with Windows Update, as one always should. Upon rebooting the system, it failed to start.

What followed was a large pain in the posterior: After attempting to do a System Restore (it failed, of course), I reinstalled. This time during Windows Update, I deselected some of the likely updates that may have caused the boot failure issue, same result. This process went on five times before I found the (in)correct update:Intel Corp - Display - Mobile Intel(R) 945 Express Chipset Family 16.6MB. Not surprising that it's a video driver, since those are typically the drivers that will hose a Windows system most often (rather embarrassed it took five tries to find out the obvious). Anyway, the update was released in September, 2009 and is one version behind what is available on the Intel website.

Once I skipped the Windows Update version of the driver and installed latest display driver from Intel, I was in business, actually Windows 7 Professional (can't MS marketing decide on a consistent nomenclature?).

Free PowerShell Editor

Yesterday I began to really dive into a new user script (which uses Exchange Management Shell) to bring it up to date and include more fields and features. As the script complexity grew, Notepad was no longer cutting the mustard.

I thought I'd be using Notepad++ or TextPad, both fine in their own right, but instead found PowerGUI. This PowerShell editor which finds syntax errors, includes definitions and much more; all for the low, low price of free. This seems to be a community supported by Quest Software who has a bunch of fine (not so free) tools for SysAdmins.

I'm now able to work on, and run, the script off network (read: at home). It's a helluva deal for the price, try PowerGUI for your next PowerShell outing.

Vista - Configuring Updates Step 3 of 3 -- 0% Complete

Last Friday I came upon a frustrating problem with a Windows Vista system that had applied updates during shutdown, but could not finish the process. This resulted in many reboots and an unusable computer; too bad it held the company's only copy of QuickBooks.

Typically the simplest fix is to boot from the Vista install media and choose Repair, then System Restore. The trouble with this system was that System Restore was turned off and there weren't any checkpoints to go back to.

Enter the endless search online. More IT troubleshooting by Bing and Google. I'm not exactly sure which search engine got me there, but one forum listed the answer (albeit two hundered or so, lines down the page).
Boot from a Vista or Windows 7 disk and choose Repair, then Recovery Console. Once you have a command line to work with, cd to C:\windows\winsxs and del pending.xml, exit to reboot again and you'll see the "Configuring Updates..." message once more, but it will continue to the Windows login screen allowing for celebrations all around.

This was the fix that worked for me, hopefully you'll have the same luck.

Network Printer Offline

Yesterday I was at a client site where everyone prints directly to the printers, rather than sharing via a print server. One of the PCs kept showing a printer as offline, even though everyone else was printing to it. From the PC you could ping the printer and even browse to the builtin web server to see that it was low on cyan.

After chewing on this for quite a while, I found the issue: a checkbox on the Ports tab "SNMP Status Enabled", which when checked (along with SNMP turned off on the print device) will result in the printer being listed as Offline. Once the box was unchecked, it was back online and the customer was back to printing once again.

God Mode in Windows Vista or 7

Following Paul Thurrott's blog such as I do, today's post listed a way to see a hidden GUI. There is quite a list, some of which are not normally exposed but via the Registry.

This is really a pretty simple hack:

Create a New Folder, rename it GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}

You can actually name it whatever you want before the dot, i.e. LinusMode, Dave, Matrix, etc. The icon will change to the one used for the Control Panel, and when opened it will list a plethora of settings.

Have fun, and be careful.

Omnibook BIOS Reset

A good friend gave me an old HP Omnibook of his, which was used by a former employee and he hadn't used it in well over a year. It turned out to have a BIOS password, which he didn't know.

I thought I was in for some laptop disassembly to remove the CMOS battery or change a jumper; perhaps even worse, to send it back to a repair depot for reset; but it was amazingly easy. 

All that had to be done was hold down the insert key while the system was booting to reset the BIOS back to default. Okay, I had to do this three times before it worked, but it worked.

Although I was relieved to be done with this in just a minute or two, making it this easy to do a reset completely invalidates the security afforded by having a BIOS password in the first place.

Anyhow, it is now happily running Fedora 11; which BTW required 515 updates for 1.6GB (and people complain about Windows updates).

Deploying Your Own Root CA via Group Policy

Although it took some searching, this nugget was quite simple.

One of my clients has a Linux Certificate Authority and none of the Windows systems would give an invalid or unknown certificate authority error when visiting a company website that used a cert created by the CA.

Get your root certificate ready, then fire up the Group Policy Management Console (or gpmc.msc). Either create a new group policy or use the Default Domain Policy to deploy it to every system.

Right-click the policy of your chosing and select Edit... go to Computer Configuration > (Policies, if you are using Windows 2008 ) > Windows Settings > Security Settings > Public Key Policies > Trusted Root Certification Authorities, right-click and choose Import... and using the import wizard browse over to your root certificate and you are done.

Within a few days most computers on the domain should have the certificate, aside from the stragglers who never seem to be on the network.