We have a domain setup, with multiple machines and everyone logging in via Remote Desktop to servers. All users use the same logon script, pointed to in Active Directory under the profile tab. The login script (a .cmd) is in the netlogon folder, and the login script entry in AD doesn't have any path, just the filename. This has been working for years.
Suddenly, in the last few weeks, it stopped working for many users. In particular, this script maps drive letters, and may of the users started saying that their drive letters weren't there. When I logged in as that user, it didn't run the script. But, if I manually ran the script, from that user context, it worked fine (ie, no security problems).
Temporarily, I have gotten around the problem by mapping the drive letters via GPO, but that isn't really what I want to do. Is Windows moving away from setting things in AD? It started for me with the session limits for Remote Desktop not being enforced. Now it seems like logon scripts aren't being enforced. Did I miss an announcement or something?
If this is supposed to still work, anyone have an idea of why it just stopped working?
BTW, when I say most users, I haven't personally tested them all, but I'm not aware of any of them where it works. I put a Pause statement in, and didn't see the message or the window.
Thank you.
Jeremy Heymann Market Mentor Online