Monday, February 11, 2008

When Windows Update Takes A Dive...

Danger Danger!!!

Windows Update is not perfect and can become unable to install updates!

What??? You are not surprised? No revelations here to you?

OK. This is not news. If anything, it is a reason to start drinking.

Maybe I can save you from the unrelenting desire to find a fifth of Jack Daniels. That is if your error in the Windows Update log is "FATAL: Error: 0x80004002".

First things first. Lets cover some steps for locating and correcting the 0x80004002 error.

  1. Identify the symptoms.
    In the case of the 0x80004002 error that I ran into, the updates would download, but fail as soon as you attempted to install them. This was the same behavior whether you started the Windows Update process from Internet Explorer or approved the updates that Windows had downloaded by itself. If Windows Update 3.1 or Geniue Advantage was attempting to install, they would also fail.

  2. Look in the Windows Update Log.
    This log is in the Windows directory and is named "windowsupdate.txt". The latest entries are at the bottom of the log. Look there for "FATAL: Error: 0x80004002" error. If you find it, then perhaps the solution that follows will correct your issue.

  3. Reregister the Windows Update dlls.
    I located these commandline entries on this Microsoft Forum link. Make a batch file from these entries and run the batch file. At least in my case, I was able to install the updates without further incident.

    net stop wuauserv
    regsvr32 wuweb.dll
    regsvr32 wups2.dll
    regsvr32 wups.dll
    regsvr32 wucltui.dll
    regsvr32 wuaueng1.dll
    regsvr32 wuaueng.dll
    regsvr32 wuapi.dll
    regsvr32 wups.dll
    regsvr32 wuaueng.dll
    regsvr32 wucltui.dll
    regsvr32 wuweb.dll
    regsvr32 msxml.dll
    regsvr32 msxml2.dll
    regsvr32 msxml3.dll
    regsvr32 urlmon.dll
    regsvr32 softpub.dll
    regsvr32 initpki.dll
    regsvr32 mssip32.dll
    regsvr32 wintrust.dll
    regsvr32 dssenh.dll
    regsvr32 rsaenh.dll
    regsvr32 gpkcsp.dll
    regsvr32 sccbase.dll
    regsvr32 slbcsp.dll
    regsvr32 cryptdlg.dll
    regsvr32 jscript.dll
    net start wuauserv

You don't have to become a drunk over Windows Update issues.

Saturday, January 26, 2008

Think Your Day Is Going A Little Rough?

Whether Vendors, Clients, the dog next door, the bozo driving next to you... you just feel beatup...

Friday, January 25, 2008

Straddling Multiple Networks safely using Virtual PC

Oh Man!!! Let a virus attempt to pass that Firewall!

If you need the functionality of 2 computers accessing two different networks on the same monitor and keyboard while using one physical machine, listen up!

I have a client that was subcontracting some work for another company. The other company moved in to an ajoining suite, so physical connection of the networks was possible. Some of my client's employees needed access to the LOB of both companies. That originally meant purchasing second computers for these employees and placing them on kvm switches. Cost was limiting how many employees could be setup this way.

What if we load virtual machines on the existing workstations? We can install a second network adapter in each computer to allow the virtual machine to connect to the second network. Tinker, install, load OS, expand memory... 2 hours later, it works! Duplicate virtual machine to additional computers. Client saves a bunch of money. IT consultant looks like he knows what he is talking about. Employees do not have to switch between 2 computers. Power utility sells less power. All positives!

Well... There were a couple of snags along the way.

SEPARATE THE NETWORKS : To make the networks not intermingle, attach the second adapter to the virtual machine. Then, uncheck all services on the second adapter inside the host OS except Virtual Machine services. Just run "ipconfig" on the host OS to verify that the second adapter does not appear. That way, neither the host nor the virtual can access both networks.

ERASE THE MAC ADDRESS : Open the vmc file for the virtual machine and erase the mac address. Don't worry. A dynamic mac address will be generated the next time the machine is started. If you don't do this, every copy of the virtual machine will have the same mac address and will pull the same ip address from DHCP. You will see some strange thing happen on your network then!

Hopefully this will encourage you to think of offbeat ways to use Virtual PC...