![]() The problem is that GPO-based login scripts are being executed in the Administrator context – not the ordinary user context. As you’ll probably have noticed, network drives connected in one context are not visible in the other. This running context is completely separate from the context you get when you right-click Command Prompt and launch as an administrator. When you’re a member of the Administrators group and you log in, your account is busted down to a non-privileged user by UAC. ![]() This is in fact by design, and it’s caused by the way UAC works. Run it again manually and everything’s fine. The script completes successfully and no error condition is encountered, but no drive mappings. You may have noticed that Windows 7 and Vista fail to connect network drives defined in the login script if the user is a local admin and UAC is enabled. ![]() Most Windows sysadmins use a Group Policy object to launch their login script. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |