The script is not a 'keep alive' script in the traditional sense as I have disabled the 'Shutdown worker process when idle for' setting and forcibly refresh the app pool every night. The script was intended to to prepopulate the cache after the refresh, but it doesn't seem to be doing that as the users still have a long wait fot the first request (compile time I assume).
I've checked and IE is definitly the default browser on the server.
The only reason I can think of the script not working is because the owner of the iexplore.exe process is the SQL service account and not a standard domain or local computer account. I don't know if this has an effect on the actual operation of the request for a page that I included in my script. I can't see why it would, but i'm clutching at straws trying to figure out why the cache is apparently empty after the script is run. I'm fairly convinced that the script was doing the job when I ran the command file on the server, i.e. ran it from the same account I was logged in as.
Do you know of any way I can test the cache to see what it contains, or at least if it contains anything?
Mike