|
I work with Gargoyle (one of the desktop guys that think it's caching the scripts locally). It's not actually caching the scripts locally, but it's caching (in the profile) that I need to run the scripts. I have verified this on my laptop when I logged in using cached credentials at home. Currently we're doing a deployment via a computer startup script so the max time to run scripts is set to 45min.
That means when I log in using cached credentials, it takes almost 45min to logoff the laptop. Because it is caching the fact that it needs to run the logon/logoff scripts in the profile. But not actually caching the scripts themselves. Then, because your offline it can't find the scripts. So you have to wait for it to timeout. Which like I said above, is set to 45min.
Not very cool.
|