Mapped Drive problem (again)

[linder]

Yes, absolutely no problem. Different users have different user settings, like printers, mapped network drives and so on. So if there are different accounts on one machine (JoeUser, BillyIdol, etc.) then they all have completely different user settings. If JoeUser has mapped a drive (non-elevated) then it's not visible in the BillyIdol account. But if a drive was mapped elevated then an elevated running application can "see" that drive mapping from all current and future accounts.

Your customers only have to launch, say, the command prompt elevated ("run as administrator") and then enter something like:

net use H: \\server\share /persistent:yes

This will then map the drive in an elevated context.

Friedrich

[Chris]

Thank you so much Friedrich,

And.. (sorry): just to be certain:

When you say "No problem",
do you mean "Yes this will work, and will solve the problem" ?

[linder]

Hi Chris,

sorry for the confusion. Yes, your users can map the drive non-elevated and elevated.

For example, on Windows 7, they click the Start button and in the "Search programs and files" field they enter 'command prompt'. Search will bring up the "Command Prompt" program. Your users right-click the Command Prompt item and select "Run as administrator".

The following will then create a mapped H: drive letter:

net use H: \\server\share /persistent:yes

As a result, non-elevated running applications can see and use all drives that have been mapped in a non-elevated context and elevated running apps (e.g. setup.exe or your own application started with administrator execution level privileges) can see and use the drives that have been mapped in an elevated context.

Friedrich

[Chris]

Perfect. Thank you.

[linder]

Friedrich