We have five user accounts on our family PC. 1 is the Administrator, two are children, two are adults. Using the online minding service I set up my two children's user account settings. I was browsing(adult) and I was blocked from a networking site. I was logged on as myself(adult account of Darren) and the minder used my son's settings to stop my access to a website.
1. Why did the minder use my son's settings for me?
2. Do I have to set up a profile for myself even if I am an adult?
The service seems to get confused as to what user is active.
We have five user accounts on our family PC. 1 is the Administrator, two are children, two are adults. Using the online minding service I set up my two children's user account settings. I was browsing(adult) and I was blocked from a networking site. I was logged on as myself(adult account of Darren) and the minder used my son's settings to stop my access to a website.
1. Why did the minder use my son's settings for me?
2. Do I have to set up a profile for myself even if I am an adult?
The service seems to get confused as to what user is active.
Since your reply was from earlier this year, I assume that this fix has already been posted.
Unfortunately, I have run into this issue on occasion more than once. I am the administrator of our home computer and have three kids set up as well.
While browsing my email, I was clicking links to LinkedIn discussion areas in my email. After reading a few, one click blocked me. I closed the browser and clicked again in my email. That time it went through. I went to OnlineFamily.Norton to see how it had reported the blocked web site and noticed it put it under one of my son's listing. Then I also noticed several web site that I had visited that showed up as having been blocked for him. I know I had visited these sites (ReadFlagDeals.com, LinkedIn.com, etc) and I know these sites are areas he'd never go to. None of them were ever blocked for me, except the one instance.
Is this still a known issue? Are others experiencing the same thing?
Thanks for the additional information. Yes, we have corrected this issue and it will be included in the next update, which should be out very soon. In the meantime, it will correct this issue if you reboot your PC.
I assume when you said "since your reply was from earlier this year", you meant to say "from earlier this week". We are in the process of testing it and getting ready to release it.