Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
Hello,
As a follow on...using the same user account, I was able to successfully uninstall N360 and then reinstall the product. Upon completion of the installation, I'm able to manage all settings within N360. However, after I reboot my system, I'm no longer recognized as an administrator by N360. When I view the processes, no user name is assigned to the Symantec processes (ie. SYSTEM, LOCAL SERVICE, or my user name).
For what its worth, the user account I'm using is a domain account for our local network and the user is included in the local Administrators group as well as the domain administrators group.
This is quite frustrating as the other two installs I performed with this product are working fine. Please let me know if I can provide any further information to help resolve this issue.
Thank you
The exact same thing happened on my work computer.
Apparently the problem presents itself when the computer is member of a Domain.
I had a Symantec tecnician connected to my computer for a whole day, he tried changing permissions on folders, registry entries, disabling UAC, but nothing fixed the problem. In the end I had to reformat my computer because all the changes this guy made broke half the software I had installed.
I never had this problems with 360 v.1.0
Thanks draiken for your reply. That's what I needed to hear. I also allowed Symantec to access my system to confirm what I was telling them. It was all I could do not to flame the tech when he presented me with a technote that suggested I log on with an Administrators account. When the tech suggested that we create a new user account with Admin priviledges I had to put my foot down. In the end, it didn't matter. The tech suggested that I use the Symantec SymNRA tool to debug my issue and email it back to them for further analysis. I thought about doing it, but then draiken came to my rescue!
It's a bug with N360 v2.3.0.9 that I really hope Symantec will address. Or, at least say N360 does not support domain logon accounts with administrator priviledges. But again, it doesn't matter. If you have this problem the solution follows.
If you installed N360 with a Domain based user account that is a member of your local administrators group on your laptop or desktop, you will be unable to manage any settings in N360 after your first reboot. Why? N360, for whatever technical reason, doesn't recognize the domain user account as a local system administrator account. To correct this problem, create a local user account on your laptop or desktop with the same name and password as your domain account and put it in the Administrators local group. N360 administration is resolved. You shouldn't have to restart or logon again, the problem will immediately clear.
I hope this helps someone else with this same problem.
David