I have a Group Policy logoff vbs script that runs successfully when users log off of the network. The vbs script deletes all user and system temporary files, folders and internet temporary files when they log off of the network daily. My plan is to add to vbs script to also remove user's desktop files and local profile files when users logoff the network.
What i'm trying to figure out is .... do group policy logoff scripts execute before or after a copy of the local profile is written back up to the server. What is the normal order? If i'm going to modify the vbs script as mentioned above I would like to ensure that the local profile is written back up to the server first before the group policy executes the logoff script. My internet research so far has not provided me a decent answer.
Thanks for your feedback but I think you misunderstood my question. I don't have a problem with the vbs script as it works successfully from the Group Policy. I'm just trying to get an answer on if local profiles get saved up to the network before a group policy script is ran during logoff.
Thanks. So now that I know that logoff scripts run before profile data is copied... there is no way to reverse that? allow profile data to be copied and then delete it? If not then i'll have to think about my other options with this.
Not that I am aware of. That's baked into AD. Not interested in the local cache disable GPO?
Jerome Slaughter
ASKER
I just did a quick read on your disable local cache via the GPO suggestion above and that will handle what i'm trying to do. Thanks again for your assistance and knowledge.