Quantcast
Channel: Windows 7 Miscellaneous forum
Viewing all articles
Browse latest Browse all 11372

Psexec Explorer.exe doesn't work properly when target is a network drive

$
0
0

Hello,

I have an application running on a server that allows a user from his PC to select a directory on a server and launch on his PC an explorer pointing directly to the selected directory.

The command is "PSEXEC \\<User's PC> -i -d explorer.exe /e,/n,\\<target server>\<share>\<1st level dir>\<2nd level dir>\<and so on>.

It has been working for years on XP PCs (and is still working on a few old timers), but on Win 7 PCs it will just open the explorer in "My documents" directory. Plus it takes at least 30 seconds to display the new window. 

I also tried (on user's PC) "Net Use Z: \\<target server>\<share>", and then from server PSEXEC \\<User's PC> -i -d explorer.exe /e,/n,Z:\<tree>, it doesn't work either.

Whereas PSEXEC \\<User's PC> -i -d explorer.exe /e,/n,D:\<tree> works fine, D being a local disk. (and the window opens instantly)

I doubt it might be caused by access rights, since the Psexec process on the server is run by a domain admin who is also a PC local admin, and I tested it on my PC using a domain admin.

After some research on explorer's evolution I also tried the new win 7 syntax, "psexec \\<PC> -i -d explorer.exe /n,/e,/root,\\<Server> /select,\\<server>\<tree>", doesn't work either.

The server on which the Psexec command is run is a 2008, the server on which the target directory resides is a 2012.

And of course I checked that the command " explorer.exe /e,/n,\\<target server>\<share>\<and so on>" worked properly on the user's PC, and it does.

Any idea please ?

Thank you




Viewing all articles
Browse latest Browse all 11372

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>