Business Environment how to go wireless?

[tvoice]

I've just installed half a dozen 650's at my business. We gave the users Local Admin rights for the install and everything went smoothly. The wireless PDA sync'd wirelessly great until we removed the Local Admin rights (as is our company policy). Now the redirector (Verizon) gives a pop-up asking for a Local Admin or original user who installed app. to login. But that was the original user, they just had different rights. Anyone get the Verizon wireless (or any other) redirector to work without giving them Local Admin rights?

[tvoice]

I've just installed half a dozen 650's at my business. We gave the users Local Admin rights for the install and everything went smoothly. The wireless PDA sync'd wirelessly great until we removed the Local Admin rights (as is our company policy). Now the redirector (Verizon) gives a pop-up asking for a Local Admin or original user who installed app. to login. But that was the original user, they just had different rights. Anyone get the Verizon wireless (or any other) redirector to work without giving them Local Admin rights?

No one else has had this problem? So far Verizon hasn't been too much help. They say that local Admin rights are required.

[Kreth]

No one else has had this problem? So far Verizon hasn't been too much help. They say that local Admin rights are required.

I'm not a Verizon customer, just a computer geek. If the Verizon software on the desktop runs as a service, you could always setup the service to run under a local admin account.

[bigshadow]

I'm not a Verizon customer, just a computer geek. If the Verizon software on the desktop runs as a service, you could always setup the service to run under a local admin account.

Even if it doesn't run as a service, depending on the OS, they can run the app under another account other than the locally logged in account (impersonation). I believe 2000 and XP has this ability.

Although, I think it will still violate their company policy. The bottom line might be they have to break their policy rules or change companies. I don't have Verizon, but I have a great deal of experience as network engineer and admin.

[Kreth]

The only way I know of to run an app as another user is to use runas. This would have to be done each time the app was run. A service, on the other hand, can be configured to use a specific account every time it runs. This could be configured by IT and wouldn't require giving the user local admin rights. Of course, this only works if the Verizon solution does run as a service.

[bigshadow]

The only way I know of to run an app as another user is to use runas. This would have to be done each time the app was run. A service, on the other hand, can be configured to use a specific account every time it runs. This could be configured by IT and wouldn't require giving the user local admin rights. Of course, this only works if the Verizon solution does run as a service.

Right-O! RunAs is what I was thinking of, I couldn't think of the term at that time. It is sort of like impersonation for developers.

Several years ago, there was a shim utility application (by Microsoft) we used to turn an app into a service, however, the app cannot have a UI that pops up. UIs cause all sorts of nasty problems for services. Maybe they can use it.

I swear, I cannot remember the name of that shim utility.

[meangene01]

I agree with using runas for a good workaround but I don't remember if you can automate passing the credentials to Windows. From a security stand point there is a chance that a user could attach other programs to the hotsync app and "steal" higher priveleges.

Here's a link for more info on runas
http://www.microsoft.com/resources/d...-us/runas.mspx