RE: runas vs network connections etc etc....

For Network Connections, another alternative is to add the non-admin to
the "Network Configuration Operators" group. Then you don't need runas
since the logged in user now has the minimal permissions necessary for
modifying network configuration settings.
 

> -----Original Message-----
> From: Murad Talukdar [mailto:talukdar_m@subway.com] 
> Sent: Monday, September 12, 2005 1:42 AM
> To: focus-ms@securityfocus.com
> Subject: runas vs network connections etc etc....
>
> Hi all,
> I have been trying to work out how to runas admin for several 
> different special folders eg network connections and printers 
> and faxes etc and following the advice about opening separate 
> processes given here; 
> http://blogs.msdn.com/aaron_margosis/archive/2004/07/07/175488.aspx
> have found it a workaround.
> Is this ideal? As far as I can see it works. 
> What do others do to get privileges when needed for these 
> essentials? This can be a real problem when it comes to 
> troubleshooting users machines and this is the best 'fix' I 
> have come across.
>
> Kind Regards
> Murad Talukdar
>
>
>
>
> --------------------------------------------------------------
> -------------
> --------------------------------------------------------------
> -------------

---------------------------------------------------------------------------
---------------------------------------------------------------------------