see this thread
see this thread
I use loopback policies to help use vanilla clients on a CC3 network, as your using Ranger I'm guessing your trying to have users logon to these PCs without the usual restrictions applying to the user accounts.
My advice would be to create three different GPOs, each with loopback enabled. The first one called "student user settings via loopback", second one called "teacher user settings via loopback" third called "ICT staff user settings via loopback".
Then deny the all students security group read and apply rights to the teacher and ICT staff's policies.
We want it so who ever logs onto that computer will be only allowed to use certain machines with ranger.Quote:
Originally Posted by Jose
Just to let you know I implemented it today and it works perfectly.
So now with Ranger/Netsupport, when a teacher logs into the control machine in the library they can only connect to the library computers.
Plus with the other group policies the horrible student bar has gone.
Thanks a lot for your help guys!
Yeh with AB Tutor you just give them that room layout and no other.
Never used Ranger.
OK, I know this thread is a few years old, but I wanted to add a loopback story. I don't remember why we set loopback for our student OU (Server 2008) but somewhere along the line we forgot that it was done. Students logging on have no access to the control panel, can't right click on the desktop, and can't adjust other settings. Well, with loopback enabled, everyone, including administrators, who logged onto a workstation in this OU had these settings applied. It was making us nuts as it took us a bit to figure out why it was doing that. Once we disabled loopback, the restrictions were once again just applied to the student accounts in the OU.
Wow, this thread was started on my son's 1st birthday, and now he's halfway through Pre-K. Windows issues are just so ... timeless!