Map the Required Drives Again in the Elevated Session
One of the useful tools that Windows offers is the ability to assign drive messages to the network locations. You can use the Map Network Bulldoze control of Windows Explorer or AB Commander to create the network drives. Later on a network drive has been created, y'all can use it just like any other bulldoze: browse its contents, re-create file to or from it, so on.
A problem may occur, withal, if you use Windows Vista or Windows seven and demand to access the network drive from an application that runs elevated (a.thousand.a. as administrator). For case, when y'all run AB Commander as usual, it runs as the standard user, and displays any network bulldoze that y'all might have created, for example:
enlarge the image
Withal, dissimilar Windows Explorer that always runs as a standard user, AB Commander offers you an option to run information technology as administrator. (You can do it by using the Restart as Administrator command on the Tools menu.) If you restart AB Commander equally administrator, you might be surprised to see no network drive in its window:
enlarge the image
(You can recognize that AB Commander is running as administrator by the presence of the Ambassador label in its title bar).
To understand why the network drive is non visible to the programs running equally administrator, we have to consider how Windows handles the standard and ambassador user access internally. In simple terms, when UAC (User Account Control) is enabled, Windows creates a separate personality for your user account: ane with the standard user's access rights to do the the regular tasks, and another ane with the full administrative access to the system. When you log in to the reckoner, Windows tries hard to create the impression that these two personalities are the same: they share the login name and countersign, the desktop and documents, settings and preferences, and so on. However, when information technology comes to mapping the network drives, Windows prefers to treat them as separate accounts (for security reasons). That's why the network drives created when you wear the lid of the standard user do not automatically become available when you put the administrator's hat on. This Microsoft article explains it all in detail.
Such behavior is rather counter-productive: afterwards all, the ambassador account is supposed to have more access to the system, information technology's supposed to exist able to see and do all things that are available to the standard user, plus some more. In this case, notwithstanding, the network bulldoze created past the standard user remains out of achieve of the ambassador.
In any example, there is a way to force Windows to make the network drives available to both the standard and administrator accounts automatically. All you need to practice is run Registry Editor (regedit.exe), locate the following key:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Policies/System
and create a new DWORD entry with the name EnableLinkedConnections and value 1:
overstate the image
Caution: If yous are not very experienced with Registry Editor, please be extra conscientious: it's a powerful tool that tin do a lot of impairment to your system if used carelessly.
After you've added the EnableLinkedConnections value to the Registry, restart the calculator, and afterward that the network drives you create should become available to the elevated applications, too.
Happy networking!
Update for Windows viii
Information technology appears that the EnableLinkedConnections setting is non always working correctly on Windows eight: if a standard user has created a mapped network bulldoze pointing to a subfolder of a shared binder (for case, bulldoze Z: continued to //server/share/subfolder), then the elevated user will see the drive Z:, merely it volition be pointing to the root share, //server/share/, non to the subfolder. (It sure looks similar a bug in Windows 8.)
If this mistake creates a trouble for you, then it's amend non to utilise the EnableLinkedConnections registry set up at all. Instead, just create the mapped network drive twice: first fourth dimension using a standard user's business relationship, and the second time using an administrator account. Sure, it'due south twice the piece of work, but it should work correctly in all situations.
Skilful luck!
Another update for Windows 8
It looks like Microsoft released a hotfix KB 2878604 that corrects this problem for Windows viii.
If yous want to link to this article, you tin employ this HTML code: <a href="http://www.winability.com/how-to-brand-elevated-programs-recognize-network-drives/">How to make elevated programs recognize network drives</a>
More information
- What people are saying virtually AB Commander…
- A FREE 30-solar day license is included
- What's new in the new version
- AB Commander printing release
- End User License Understanding (EULA)
- Infinite Investigator
- Using DiffMerge as the external tool of AB Commander
- Is "Wipe the content" the aforementioned as "Secure Delete"?
- How to start programs elevated from a batch file
- How to brand elevated programs recognize network drives
- How to disable hibernation with AB Commander
- How to prepare upwards Notepad++ as the external text editor for AB Commander
- Integrating AB Commander with Universal Viewer
- How to repair Windows desktop icons with AB Commander
- How to evidence drive letters commencement in AB Commander and Windows Explorer
- Organize your photo library with the Rename tool of AB Commander
- How to movement images from an Android device to PC
- How to synchronize images betwixt a PC and an Android device
- Using junction points to alter the iTunes fill-in folder location
- Ever have a backup of your of import files
Source: https://www.winability.com/how-to-make-elevated-programs-recognize-network-drives/
0 Response to "Map the Required Drives Again in the Elevated Session"
Post a Comment