Microsoft

Are you having printer server problems lately with HP drivers installed?

A Windows print server has multiple HPBPRO processes running simultaneously or the HPBPRO process contributes to crashing or hanging a print server.

Some examples of what the enterprise customer may see are as follows:

CPU utilization on Print Server will go to 100% or everything looks fine but blank pages are printing out on printers. During this time if the administrator goes to Task Manager they may see there are multiple instances of HPBPRO running on the server as a process.

A customer has multiple print servers running in their network environment. Various servers are seeing HPBPRO randomly become active for no apparent reason and causing performance problems on the server. Closing or killing the HPBPRO processes or rebooting the server solves the issue for the time being.

This problem occurs when following conditions are met:

The HP Toolbox is installed through a HP Printer CD on client machine.
The Print Server has one or more EAC based Printers shared to clients.
Client machine has one to more printer connections (Point and Print) through the Print Server.

Read more about it here and download updated HP drivers to prevent any further problems.

Mostly of interest for enterprises using a disjointed namespace (DNS suffix of the node's FQDN differs from the domain name) - this fixes an error in the Clustering code.

Read more about it and download it from here.

Go here for the fix if you are experiencing this issue.

I have experienced this problem on my little Thinkpad 240 laptop that I use as a poor man's EVDO router. Believe it or not, it makes for an extremely portable "Internet hot-spot on the go".

Sometimes when the Novatel NDIS adapter 'falls asleep' on the receive side, I have to reset the connection. This only happens rarely, but before this fix was installed, DNS resolution of the ICS clients would fail unless I hard-coded external DNS servers on the client systems.

Of course, the hard drive on the Thinkpad has an expired warranty and is an IBM DeathStar with bad sectors, so it is only a matter of time I have a massive hard drive failure. I have a system image backup for when that day comes. I've been saying that for the past 2 years.

Now that I've mentioned it on here, I am sure it will fail within a week.

When that day comes, I can roll out a beta of the Forefront Threat Management Gateway for our house.

Another handy hotfix to keep around for your System Center Operations Manager 2007 install if you are running Server 2008 or Vista. If your Health Explorer is crashing, you will want to install this OS update here.

It looks as though it isn't an error in SCOM, but an error in ComCtl32.dll.

Go here for an update for Windows Vista SP1 and Windows 2008's RDP (Terminal Services) technology. It plugs a non-paged pool memory leak (my favorite to plug). On a good note, Vista and Server 2008 allocate non-paged pool dynamically instead of statically at boot time, so it will take a lot longer (typically) for this type of memory leak to take down your system.

In the past, before Vista, non-paged pool was a fixed amount, which can cause all sorts of problems if you have a leaky driver or application, like Symantec's Corporate Anti-Virus v10.