I don't see the connection with JT. Are you saying maybe JT would be better than what you've got? With regard to ADMIN$ share, wouldn't JT also require it?
If you want to put in place the structure Jens uses for other pushes, and then take advantage of it to roll out KiX, that's fine, but it is more effort to push the JT than to push KiX.
The place where the WaitFor concept differs from Jens' JT is in the timing. Jens has an (async) LA attitude of "when I get around to it" which he can do because he has a well controlled small shop with wake-on-LAN capability. I prefer to hold the user in the logon (sync) where I know that apps will not be opened when I don't want to allow them.
Me, I'm lazy. Like water, I take the path of least resistance. WaitFor is just a concept. I push KiX from my logon.bat and log failures. No big deal. If it fails, run KiX from NetLogon. I then parse the exception log and remote push through ADMIN$. If the're powered off, I'll get 'em next time. For the really big stuff like M$ Office, I have SMS.
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
