2

Small parts of my application require admin rights (activation of the software needs to go to HKLM). For this, I draw shield icons on the buttons whose action require admin rights and when clicking, I restart the application with an appropriate parameter again using "runas" verb.

This works very good! However, now it happens that users execute the application from a network share. If they click on the "admin rights button" now, they get an error message because the network drive is not mapped for the administrator, therefore the executeable can't be found :-(

What's the best way around this?

divB
  • 896
  • 1
  • 11
  • 28

1 Answers1

4

Mapped drives are stored with each logon session, so you don't have them after elevation.

You can extract the admin interface to another executable and mark it as requireAdministrator in the manifested. Then launch the admin executable via ShellExecute. Windows Explorer will copy the drive mapping in this case (undocumented behavior, though).

Sheng Jiang 蒋晟
  • 15,125
  • 2
  • 28
  • 46
  • Another alternative is to stop using mapped drives. Use full UNC paths instead. Mapped drives only existed as a compatibility hack back when DOS 3.3 added networking support, and applications would choke on a filename that start with `[letter]:` – Ian Boyd Jan 01 '14 at 18:49