Group Policy and Scripts

FAscratch · 06-12-2009, 01:48 PM

We have a logoff script or command that runs cleaning out a temp working directory on our terminal servers. This was set up years agon and old employees are gone. It still runs on the old TS but not our new TS's. I am guessing that it is a local script or GP but I have looked everywhere and can't find how it is it running.

Scheduled tasks - no
gpedit.mmc(local server) - Computer configuration>Windows Settings>scripts>logon and logoff

and

User Configuration>Windows Settings>scripts>logon and logoff

I have even double checked my GP and logon script....nothing there that shows the cleanup.cmd or delete.bat running.

So far cleanup.cmd and delete.bat are the only things I find that could clean these files out.

Any suggestions where else to look??

HussainU · 07-06-2009, 04:55 AM

is there no Default Domain policy with the script there?
did you check logon scripts on local machine gpedit or on the AD server?

06-12-2009, 01:48 PM	#1 (permalink)
FAscratch Registered User Join Date: Jun 2009 Posts: 1 OS: Win Xp Sp3, Server 2003	Group Policy and Scripts We have a logoff script or command that runs cleaning out a temp working directory on our terminal servers. This was set up years agon and old employees are gone. It still runs on the old TS but not our new TS's. I am guessing that it is a local script or GP but I have looked everywhere and can't find how it is it running. Scheduled tasks - no gpedit.mmc(local server) - Computer configuration>Windows Settings>scripts>logon and logoff and User Configuration>Windows Settings>scripts>logon and logoff I have even double checked my GP and logon script....nothing there that shows the cleanup.cmd or delete.bat running. So far cleanup.cmd and delete.bat are the only things I find that could clean these files out. Any suggestions where else to look??

07-06-2009, 04:55 AM	#2 (permalink)
HussainU Registered User Join Date: Dec 2008 Posts: 62 OS: Xp	Re: Group Policy and Scripts is there no Default Domain policy with the script there? did you check logon scripts on local machine gpedit or on the AD server?