Well I haven't gotten there yet, but I'm hoping to run silent scripts with WKIX32.EXE and I want to probably sleep the script for maybe a couple minutes after logon before it starts to really do anything.

At that point as long as you are not stealing all the CPU cycles and bandwidth of the client, you should be able to do similar things like MS SMS does and do background processing.

I am currently re-writing my entire logon script (thus all the recent posts about repairing scripts and UDFs to support the NoVarInStrings)

Nice posting by Howard about the SetOptions. Seems some things are not a clear as one would initially think.

I'm assuming that this will be the best practice for my new script.

DIM $Set1,$Set2