Thank you for the suggestions.
We had originally considered a GPO (and ultimately may
have to go back that direction) but had dismissed the idea due (in large part)
to the socio-political structure we have (who would have believed a university
could be so political, I know I didn't). Each OU represents a separate
college or major organization which enjoys a kind of autonomy. They
manage the GPO's and computer activities within their OU, users are
centrally managed. In order to implement a GPO that might affect an OU, we
end up needing to get their permission (odd, I know, but it was a compromise
worked out over several years worth of negotiations (which, by the
way, are still on going) with the different colleges, unions, and
organizations involved in an effort to unify services and provide platform
independent IdM (Identity Management) and single sign-on for the staff,
faculty, and students across the campus). I was hoping for something less
invasive, which is why I had tried the "Log On To" method.
Come to think of it, I need to check when they (and who
"they" are that) added politician to my job description, but that's a different
issue for another time.
Thank you again for the suggestions, they are
appreciated.
David Aragon
|
- [ActiveDir] Limiting User Logon to Specific Machines David Aragon
- Re: [ActiveDir] Limiting User Logon to Specific Machin... ASB
- Re: [ActiveDir] Limiting User Logon to Specific Ma... Za Vue
- RE: [ActiveDir] Limiting User Logon to Specifi... David Aragon
- RE: [ActiveDir] Limiting User Logon to Specific Machin... Steve Rochford
- RE: [ActiveDir] Limiting User Logon to Specific Machin... Steve Rochford