Glenn,

You are right on the money with what's going on. Kix script, calling to CMD's that are trying to provide simple status messages and are completely hidden from the user.

I am one of the "crazys" who is not using kix as a login script at this point. And in this scripts case, it may end up being called during login, but I want it to execute the same whether called from login vs pushed via a deployment solution.

Just prior to seeing your post, I was able to resolve my problem with the use of Psexec.

Code added into the called CMD files:

 Code:
Pushd "\\networkserver\networkshare"
psexec /accepteula -i -s msg.exe /TIME:60 * "Office 2010 is being installed to your computer, this can take a while to complete. Your computer will reboot once the upgrade is finished." 
popd


Psexec defaults to executing on the local system, when flagged with -i (interactive session) and -s (system account session), it displays the MSG's I want.

I am tempted to potentially take this a step further and have psexec call to a kix script instead so that I can utilize the much more customizable messagebox features.

\:\)

BTW - ty very very much for the suggestions and insight.

/peace

lan