I was called by a user regarding a “Browse for Folder” prompt, similar to the one shown below:
The issue was this: They were trying to navigate to a network drive on the above prompt within an enterprise application, yet it wasn’t appearing in the Browse for Folder window. Neither restarting the application nor the machine resolved the issue – and no others users were experiencing the same problem.
This particular network drive is loaded automatically via login script for users on the domain – it was being loaded properly, and the network drive was appearing in the File Explorer with full accessibility; so it wasn’t a matter of not being able to connect.
I suspected it had something to do with the administrative status of the linked drive not passing through the application for some reason – and I was basically right. A Google search yielded this from someone else who had the same problem with another application:
We had a very similar problem with Oracles Pimavera software when printing to PDF. This is the support response they gave us:
Ticket closed: Problem resolved through Oracle support:
Mapped Network Drives Not Available When Creating PDF Files From Primavera. [ID 1122045.1]
Modified 21-JUL-2010 Type PROBLEM Status PUBLISHED
Primavera P6 Enterprise Project Portfolio Management – Version: 7.0 and later [Release: 7.0 and later ]
Information in this document applies to any platform.
Mapped network drives are not visible when creating PDF files from Primavera on Windows Vista and Windows 7 when the User Account Control (UAC) is enabled.
This problem occurs because UAC treats members of the Administrators group as standard users. Therefore, network shares that are mapped by logon scripts are shared with the standard user access token instead of with the full administrator access token.
Configure the EnableLinkedConnections registry value, which allows Windows to share network connections between the filtered access token and the full administrator access token for a member of the Administrators group.
This rang true to me. So I set up the aforementioned registry value in accordance with this process:
- Access the Registry Editor – can be found by typing regedit into Start menu search and selecting the result.
- Location the following subkey in the registry:
- Right click on the subkey and select New >> DWORD value.
- Name the entry EnableLinkedConnections and hit OK.
- Right-click EnableLinkedConnections and select Modify.
- In the Value data box, enter 1 and hit OK.
7. Exit regedit and reboot, then test. The folder should now appear successfully in the Browse for Folder window.
I completed step 7, and presto – the network was there in the Folder browser! Creating the registry entry did the trick.
As to why this happens, Microsoft explains it this way:
When UAC is enabled, the system creates two logon sessions at user logon. Both logon sessions are linked to one another. One session represents the user during an elevated session, and the other session where you run under least user rights.
When drive mappings are created, the system creates symbolic link objects (“DosDevices”) that associate the drive letters to the UNC paths. These objects are specific for a logon session and are not shared between logon sessions.
Note The EnableLinkedConnections registry entry forces the symbolic links to be written to both linked logon sessions that are created, when UAC is enabled.
When the UAC policy is configured to Prompt for credentials, a new logon session is created in addition to the existing two linked logon sessions. Previously created symbolic links that represent the drive mappings will be unavailable in the new logon session.