For security reasons, we modified this behavior beginning with Windows 2000 SP2. Prior to Windows 2000 SP2, device names remained globally visible until explicitly removed or the system restarted. This convenience feature makes it easier to run into issues with mapped network drives. We then detect that you have UAC enabled, we log in a second time, and end up with a new (highly restricted) token, which we use to launch the shell. To simplify things, let's assume you are running as an administrator with UAC enabled (although, to be more secure, it is better to run as a standard user). Mapped Network Drives with UAC on Windows VistaĮdit: relevant bits from the blog entry (emphasis mine): The reason for having to recreate the shares is explained on this MSDN blog entry: a Windows Explorer launched with "Run as administrator") and recreate all network shares, that should do the trick. Try launching an elevated Windows Explorer (i.e. Since almost all users used an administrator account in XP (as most programmers didn't bother to make their programs work with limited accounts), Microsoft made a "limited version" of administrator accounts starting with Vista, an in some situations the two "versions" counts as different users (since they are separate sessions). Note that an user can have more that one session. ![]() ![]() different users may have a different set of network shares). Network shares being associated with sessions (i.e.Probably that is not a problem of file permissions but it's related with:
0 Comments
Leave a Reply. |