Posted 10 November 2010 - 05:28 PM
Let me start by explaining what led to my problem.
I work for an electric utility, and we issue Panasonic Toughbook laptops to our linemen containing our mobile mapping and AVL (Automatic Vehicle Locating) software. They are all running Windows XP Professional SP3. Our AVL software requires an internet and VPN connection to our AVL server at the office (we currently use Verizon Air Cards and the Cisco VPN client to achieve this). Since implementing this, we have found that Cisco VPN and the Verizon Air Cards do not work well when the wifi network adapters are turned on (or enabled). When they are turned off (disabled) everything works nicely. We can't just disable the wifi NIC's and call it good either because our user's need the faster wifi connections to perform database syncs in the mornings (via hotspots inside each garage bay). Once they are all synced up and out of range of our wireless network, the wifi NIC's are no longer needed. Since the wifi NIC's and Air Cards don't get along, we have been having our users turn the NIC's off using a hardware switch on the Toughbooks cassis. However, some of our older models (CF-29's to be exact) do not have these hardware switches. Our solution was to create two batch files and place them on the users' desktops; one that turns the wifi NIC on, and one that turns it off.
This brings you up to my current problem...
Our userís logon to a non-admin account and because of this, they do not have the ability to disable/enable a network adapter. However, this was easily fixed by modifying our Group Policy settings. This policy change allowed them to go into network connections and right-click on the wifi connection, and then enable or disable it. However, we were hoping to make it even simpler by adding the two batch files (mentioned above) to the desktop, which when ran, disables/enables the wifi NIC from the command line using DevCon.
The batch file command to disable (vice versa for enable) the NIC is simply:
devcon disable *<device ID here>*
When ran from the Admin account, these two batch files work well and do exactly what we want them to do.
However, when we run them from a non-admin account, they fail, and an error message pops up that says:
"Unable to open the driver specific registry key for this device"
I tracked down the registry key in question and gave full access to the non-admin userís profile, but all this did was prevent the error message from popping up; the batch files still failed to enable/disable the wireless NIC.
At this point I am at the end of my rope; I have no idea where to go from here. My guess is that it is a permissions problem with DevCon, but I don't know for sure.
Does anyone else have experience with enabling/disabling devices with DevCon on non-admin accounts?
Or perhaps, does anyone know of another way I could write these batch files (besides using DevCon)?
Any help would be much appreciated!
United Power, Inc.
"Everything is funny as long as it is happening to somebody else."