Mapped Network Drives on Windows 10

[jbrandim]

Hi,

We are just now getting Windows 10 in our lab.  We are running Diadem 2015 SP 2 (32-bit).

We notice that none of our mapped network drives are visible to file open dialogs.  We have several network drives that are used to share data sets, scripts, and report template.  Now, we can't navigate to them from inside Diadem.

Is there a setting we are missing?

Thanks.

[brandonj]

Hello,

I am able to see any mapped network drives in the datafinder and in file dialogs in DIAdem 2015 SP 32 bit on Windows 10, and I believe I have the default settings. How are your drives mapped? Can you send screenshots?

[jbrandim]

We map them with the normal File Explorer "Map Netword Drive".  "W" shows here as "Network Location".

It doesn't show up in the File Open dialog.  I also tried clicking the "Network" button in the dialog. That lists other PC hostnames, but not the mapped drive.

[StefanR]

Do you see the mapped drives in a "File open"-dialog when using other products, for instance a Microsoft Office product?

[jbrandim]

Yes, other applications behave as expected.  Even LabView open file dialogs see the network drives.  Only Diadem. 

It's not just in the data portal.  If I go to scripting and click File->Open, that doesn't see the network drives either.  Very strange.

[RJF]

I have the exact same problem.

Windows 10

DIAdem 2017 SP1

Was there a resolution to this issue?

[jbrandim]

We traced this to our company's internal Group Policy Preference (GPP).  Our GPP settings prevent Diadem from launching unless we select "Run as administrator".

Our GPP settings also prevent mapped drives from being seen by the administrator session.

See this link for an explanation: https://support.microsoft.com/en-us/help/3035277/mapped-drives-are-not-available-from-an-elevated-pr...

We use "Method 2" and re-map the drives using a .bat file that must also be "Run as administrator".  Annoying, but it does work.