need non-admins to run repair

  • Thread starter Thread starter KenK
  • Start date Start date
K

KenK

How can an average user, XP Pro SP3, be given the right to run a repair on
the Windows wireless utility. I have 80+ laptops on the network and need to
find a registry tweek or work around so the users have the option to run a
repair when the laptop fails to get an IP Address.
 
How can an average user, XP Pro SP3, be given the right to run a repair on
the Windows wireless utility. I have 80+ laptops on the network and need to
find a registry tweek or work around so the users have the option to run a
repair when the laptop fails to get an IP Address.

Ken,

Wouldn't it make sense to figure out why the network is damaged, and a repair is
needed? "Run a repair" is simple enough (given admin access), but if it's an
ongoing need, maybe there's a problem.

Windows XP, in general, is pretty stable, and I can count on a couple fingers
the number of times that I have had to repair a connection using the "Repair"
button. If you find that your users are needing to do this routinely, maybe you
ought to look at why they have to do this.
 
Chuck said:
Ken,

Wouldn't it make sense to figure out why the network is damaged, and a repair is
needed? "Run a repair" is simple enough (given admin access), but if it's an
ongoing need, maybe there's a problem.

Windows XP, in general, is pretty stable, and I can count on a couple fingers
the number of times that I have had to repair a connection using the "Repair"
button. If you find that your users are needing to do this routinely, maybe you
ought to look at why they have to do this.
All the laptops are using an updated driver. The wireless network is a
Trapeze managed network. The issue happens a couple of times a day, that the
device thinks it is connected to the network, but is not, and a repair fixes
the problem. Yes, the deep issue is probably in the Trapeze controllers
software, but the initial question is "how can a wireless network REPAIR be
run by a non-admin user?".
 
All the laptops are using an updated driver. The wireless network is a
Trapeze managed network. The issue happens a couple of times a day, that the
device thinks it is connected to the network, but is not, and a repair fixes
the problem. Yes, the deep issue is probably in the Trapeze controllers
software, but the initial question is "how can a wireless network REPAIR be
run by a non-admin user?".

Ken,

I spent some time looking thru the Local Security Policy for a setting that will
enable this, and so far no luck.

http://networking.nitecruzr.net/2005/07/local-security-policy-editor.html

You're welcome to do this yourself. Generally, though, network repairs are left
to qualified individuals, not the end user. In a professional organisation, you
would be advised to involve the provider of the updated driver (Trapeze?), and
fix the problem.

Maybe you can use a DHCP reset script.

http://networking.nitecruzr.net/2005/06/does-your-computer-lose-network.html
 
Back
Top