yossefheskiel
asked on
Login Script cached?
We recently modified a login script to call and application that will merge a registry key for a piece of software deployed in the company.
The first version of the app being called generated an error on login. After the app was modified and fixed some users still experience the error even though if the login script is run manually or another user logs in to the same box it does not occur.
Is there a place that the scripts are being cached or the app itself? any way to clear this out?
The first version of the app being called generated an error on login. After the app was modified and fixed some users still experience the error even though if the login script is run manually or another user logs in to the same box it does not occur.
Is there a place that the scripts are being cached or the app itself? any way to clear this out?
to clarify, when I said "on the one", this means of course "on the PC"...!
ASKER
The Login script has been replicated already to all DC's. This is a case where if you run the script from any DC manually it runs no problem. Also if it runs on login for most users from any DC it runs no problem. Only a few users are having the problem on login.
I had already checked their logonserver and run the script from it manually and it worked, and also set the logon server to a different DC and it still got the error belonging to the old app.
I had already checked their logonserver and run the script from it manually and it worked, and also set the logon server to a different DC and it still got the error belonging to the old app.
I'm having this same issue, and I think there has to be some kind of cacheing of the login script. We recently separated off into our own domain, and some users are still running the old login script.
Yosssef - is it the same users every time for you? On mine, it's random people getting the wrong script on random days. Though some users never seem to get it. I tried SET LOGONSERVER as suggested above, and it reports the correct server, which has the correct version of the script.
I'll post here if I find a solution, and keep checking to see if someone here solves it first!
Yosssef - is it the same users every time for you? On mine, it's random people getting the wrong script on random days. Though some users never seem to get it. I tried SET LOGONSERVER as suggested above, and it reports the correct server, which has the correct version of the script.
I'll post here if I find a solution, and keep checking to see if someone here solves it first!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
on the one that shows the out of date scripts, drop to a command prompt and do
SET LOGONSERVER
and it will tell you which server authenticated that login.
After you change a script, you'll need to wait for replication before all servers pick it up - can take up to an hour.
hth, Danny