Software first run must be admin
Hello
I have a utility that will allows users to install an application with an administrator account. We r planning to distribute this application cd with VZAccess manager to staff in the field who do not connect to our network. My problem is that the VZAccess Manager software does not allow the client (with no administrative rights) to connect to the National BroadBand. After running the wizard, it sees the device (BlackBerry8703e) but the National BRoadBand never pops up. If an administrator logs on and runs the wizard it will connect to National BroadBand and then when the client logs after the admin, they can connect to National BroadBand.
Can anybody help me with maybe a workaround this issue.
I have a utility that will allows users to install an application with an administrator account. We r planning to distribute this application cd with VZAccess manager to staff in the field who do not connect to our network. My problem is that the VZAccess Manager software does not allow the client (with no administrative rights) to connect to the National BroadBand. After running the wizard, it sees the device (BlackBerry8703e) but the National BRoadBand never pops up. If an administrator logs on and runs the wizard it will connect to National BroadBand and then when the client logs after the admin, they can connect to National BroadBand.
Can anybody help me with maybe a workaround this issue.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
deploy.no
17 years ago
Not knowing what app this is or really understanding whats happening, it seems like you are having a problem with either missing settings of some kind (as the installer might install required settings only to the admin account) and/or access rights.
This wizard you are talking about are probably storing the results of its run in a way that aren't accessible from the client account.
To solve this you need someone with good debugging skills and Windows knowledge. That someone would probably fire up Process Monitor or something similar and try to investigate what happens.
Don't want to sound harsh but I think without more specifics its going to be hard to help you any more.
This wizard you are talking about are probably storing the results of its run in a way that aren't accessible from the client account.
To solve this you need someone with good debugging skills and Windows knowledge. That someone would probably fire up Process Monitor or something similar and try to investigate what happens.
Don't want to sound harsh but I think without more specifics its going to be hard to help you any more.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
