I am having a weird issue and maybe there is a fix to make a Windows 7 machine clear out login scripts that were previously set by a group policy? There was a group policy I disabled and eventually completely removed from the directory that another admin put in place. It was annoying because it would do a msgbox window 2 or three times while mapping printers / drives and I wanted to get rid of it. So I removed the group policy from the OU that the user accounts were in but the script continues to run even after waiting for an extensive amount of time running gpupdate /force multiple times etc. There is no scripts specified on the users profile tab. The Windows 7 machine still runs the vbscript every time I logon... is there a setting or cache on Windows 7 somewhere that might be holding onto this script and still executing it even though all possible precautions and changes have been made to Active Directory to prevent this script from executing at logon? Any suggestions would be helpful and thanks in advance!

1. What is resulting policy in W 7? 2. There is a dirty way: Create new OU with required GPO and move there workstations. Regards Milos

Hi, Meanwhile, I would like to suggest you use the autoruns tool to see if you could delete the logon script: Autoruns for Windows v11.31 http://technet.microsoft.com/en-us/sysinternals/bb963902 Alex Zhao TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Alex Zhao TechNet Community Support

Thanks guys. It actually worked itself out. It just took forever. I find it really strange the Windows XP machines grab group policy almost immediately where the Windows 7 machines take much longer. (Multiple reboots and multiple gpupdate /force commands) Anyone know why that is? I thought Windows 7 was supposed to be far superior when it comes down to group policy compliance. Thanks for the link and the info I'll review both options. Just scratching my head over Windows 7. Most of my scripts I am executing in the GPO objects are VBScript. I noticed some of the systems were caching old scripts applied by previous policies and executing them. I just gave them a good amount of time and it stopped. Some "Want-it-now!" end-users weren't too happy about it so in one or two circumstances I went as far as to create a shortcut to the vbscript in the startup folder. Not a good thing since I need to go through later to remove that. My presumption is the policy will catch up with the 7 boxes by then though.