Sorry I didn't make it there today as planned.  I'm putting Wadsworth first tomorrow -- can you identify that recalcitrant computer in 221 by number or description, or will Townsend know which you mean?  

Normally we say to take the computer off of all domains (join a made-up workgroup), then from there [maybe with a reboot] join INSTR.  But if it wasn't giving you Properties from MyComputer it sounds like a tougher nut to crack.

You may remember we talked about why the printer script seems to give a lot of errors at login time, but then runs without error when you select it manually a little later.  I'm speculating that it just takes some time to estabish the network connection, which isn't ready when the script tries to run.  So it might help to put a pause into the script.  Iooked up the command today, and it's a component of the WScript object called WScript.sleep; it takes a numerical argument which gives the sleep time in milliseconds.  So I hopetobe able to try out a modified script like this:

WScript.Echo "Before sleep"                                                                                                        
WScript.Sleep 15000                                                                                                                 
WScript.Echo "After sleep"                                                                                                         
Set WSHNetwork = WScript.CreateObject("WScript.Network")                                                                           
                WSHnetwork.AddWindowsPrinterConnection "\I6300W43818143U221hplj4000"                                             
                WSHnetwork.SetDefaultPrinter "\I6300W43818143U221hplj4000"

(Well, the Echo lines are just temporary.)  If the pause improves things we can try to add it where the script is already installed and gives alerts.