/build/static/layout/Breadcrumb_cap_w.png

Nokia PC Suite - Connection Manager needs local admin rights

I made a msi for Nokia PC Suite 6.3.1 (i know there's a 6.3.2. out there).

I install my packages with SMS. PC Suite looks to be working just fine as an administrator, but when i use the package as a normal user the Connection Manager can't find any connections (the connections field stays empty). I scanned with regmon and filemon to see if there were any rights conflicts but couldn't find any.

i compared the filemon and regmon logfiles with two different scenarios. Normal user and normal user with administrator rights. But no juicy bits were found.

Does anyone have suggestions? I don't want to give my users local administrator rights, just like that....

0 Comments   [ + ] Show comments

Answers (5)

Posted by: oofemioo 20 years ago
Blue Belt
0
I suggest you run your application under the User account using SMS Installer to capture what is happening. Also try the same method when running the app. under the admin account and compare your IPF files.

Also you should try launching the app. immediately after the install b4 launching with the ADMIN account to see whether the setup capture was complete.
Posted by: mickman 20 years ago
Orange Belt
0
I found out that the problem lies in the product itself. Nokia PC Suite's Connection Manager requires Local Admin rights. (but for what)

Too bad Nokia couldn't give any advise to avoid giving local admin rights to normal users. The Nokia department i spoke to (customer support) had the product installed but they were all administrators. Great work system designer! :')

If only i could find that piece of the puzzle on which i can give rights.[X(]
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
Unless the executable has specific needs to be a local admin then you might be able to permission the keys required to give authenticated users the rights to those keys.

Log in as a user and run regmon as an admin with runas and see how it is
Posted by: mickman 20 years ago
Orange Belt
0
Well, i found a solution:

I distributed the application per-system instead of per-user. That did the trick.
Posted by: mickman 20 years ago
Orange Belt
0
If you'd read my post carefully you'd know i did that.
[8|]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ