/build/static/layout/Breadcrumb_cap_w.png

Use in a non-admin account

Hi, I have the secure browser installed and it does work (most of the time - see comment below) well from my Admin account, however if I try to use from a non-admin account it fails to launch properly and Firefox is shown as using approx 50% of the CPU resource.
I also have PCTools installed and that showed several hundred identical broken entries in the registry.

As per the note above, this 50% CPU usage has been seen in the Admin account on one occasion and on closing Firefox (which seemed to close normally) the CPU was seen to remain at 50% and Firefox was listed in the Task Manager as the culprit!

Have you any experience or advice on this?

0 Comments   [ + ] Show comments

Answers (3)

Posted by: DaveA 11 years ago
Yellow Belt
0
I have had the same experience. Any ideas? Anyone?
Posted by: Nivek 11 years ago
Senior Yellow Belt
0
Anyone know how to fix this?
Posted by: bkelly 11 years ago
Red Belt
0
We have had some success reproducing this and are looking deeper into it now. As to the broken registry link messages your tool is reporting, I expect this is becuase Firefox is installed as a virtual application and its registry entries (and files) are not where the system would normally expect to see them. From outside the Secure Browser itself, the virtual instance of Firefox included with the Secure Browser will not appear installed at all.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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