Jase's Place

Have you ever wanted to put the "truth" in a Shutdown Event Tracker comment box?


I've had to deal with my fair share of terrible applications/services, that the "Business Unit" has decided to use, but were less than, shall I say "Stellar".

I figured I'd post this, as I thought it was funny to see what it looked like when I followed the spirit of George Washington, in the fact that "I cannot tell a lie."

Thanks,
Jase

Labels: Windows

Well, it may not be supported, but ESX 3.5 does install on an IBM x440.

This isn't the first time VMware ESX has not been certified on an IBM x440.

When ESX 3.0.0 came out, there was a small outcry on the VMTN forums (by those of us that have them) about these boxes being supported, as they were close to End-Of-Life, but still represented significant investments.

I spoke with my VMware SE many times about it needing to be supported. He said that it "Should" run on it, despite the fact that it wasn't officially supported.

Several months after the initial uproar, VMware certified ESX 3.0.0 to run on an IBM x440.

Well here we are again, 3.5 just came out on 12/10/07, and yet again, the x440 was left off the hardware compatibility list.

A coworker bought a quad proc (1.4GHz Xeon) x440, for personal use, and we fired it up.

Low and behold, ESX 3.5 does install, and the VMkernel loads.

Even though the HCL recommends a minimum 1.5GHz cpu speed, the installation didn't seem to care that this box was a wee 100MHz shy of the minimum recommended cpu requirements.

He hasn't loaded any VM's on it yet, as it was late in the day, and we didn't get around to it. From initial indications, it looks like ESX 3.5 may just run on an IBM x440.

I'll post more when I get more info, as to how well this runs...

Labels: VMware

Not sure if you've every had an issue where you have to move printers from one print server to another... I have had this come up a couple times...

Here's a little vbs that can be executed from a logon script, that will look at a mapped printer's connection (which server it is on), remove it, and then map it to another system.

Keep in mind, all the printers on NEWSERVER must have the same share names as the OLDSERVER.

Basically this script enumerates each printer, looks for the server it is mapped from, deletes the printer, and then adds the new printer, which happens to be the same printer, but mapped on a different server.

Here is the code:

On Error Resume Next
Dim strComputer
Dim objWMIService
Dim colItems
Dim WshNetwork

Set WshNetwork = WScript.CreateObject("WScript.Network")

strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from Win32_Printer",,48)
For Each objItem in colItems
If objItem.ServerName = "\\OLDSERVER" then
WshNetwork.RemovePrinterConnection objItem.ServerName & "\" & objItem.ShareName, true, true
WshNetwork.AddWindowsPrinterConnection "\\NEWSERVER\" & objItem.Sharename
End If
Next

If you want to download it, you can find it here.

As always, you are welcome to use the script, but I will not be held liable if any issues arise.

Labels: VBS Windows