As I posted earlier, I tried working around some limitations in Microsoft’s Active Directory by teaching the script some intelligence.
But, since we recently started using Thin Clients, all the stuff I did with the fancy vbs was just a waste-of-time. Turns out, Windows XP Embedded doesn’t work quite the same as a “normal” Windows XP (that’s where I tested the script on), and it simply dies when running the WMI Query. Bollocks.
So I switched back, utilizing a shortcut in Startup, but pointing to the shortened vbs (see below) instead of the ugly batch file someone wrote.
|
1 2 3 4 5 |
Set WshNetwork = CreateObject("WScript.Network") WshNetwork.AddWindowsPrinterConnection "\nas.barfoo.orgKyocera FS-9100DN KX" ' Set the default printer to something useful WshNetwork.SetDefaultPrinter "\nas.barfoo.orgKyocera FS-9120DN KX" |
But even that doesn’t work all the time, I still have to figure out why.
You can add WMI support to the HP t5000 series Thinclients. I wouldn’t be surprised if you couldn’t add it to whatever model you are using.
(HP t5000 series are XPe based)