Conferences & Events
Events for all Levels and InterestsStay
Jump Start Your Career GrowthStay
Get on the Higher Ed IT MapStay
Uncommon Thinking for the Common Good™Stay
Windows 7 Labs in AD
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
We are in the process of moving our Windows lab machines to Microsoft's AD environment and have run into some bumps. Our current environment is eDir, which consists of a Novell client running on Windows 7, where a user logs in with their network credentials for network resources ( network drives, printer access - iPrint). We are using Autoadminlogon to redirect all logins to a local account with the user profile configured for the various applications installed on the lab image. However, now that these machines are joining Microsoft AD, we are running into a problem where users are not being prompted for their network credentials if Autoadminlogon is enabled.
We would like our windows 7 computers that are joined to a domain have domain users login with their credentials but instead of creating a new local account that matches that domain account we want it to login to a pre-configured local account. We have Deep Freeze installed on these computers meaning newly created profiles get wiped out at reboot resulting in long logins every time.
How is your institution handling computer labs joined to a domain and user profiles?
Associate Director of Technology Services
Eastern Mennonite University