|
||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||
ABSTRACT
The University of New Hampshire has a history of using centralized Unix accounts to authenticate user access to computers in the public Student Computing Clusters. The advent of Windows 2000 meant that changes would be necessary to support the Active Directory architecture underlying Windows 2000 authentication and authorization. Given limited resources, manually maintaining Active Directory accounts for over 12000 students is an impossibility. A new system was needed to automatically generate an Active Directory account for each and every Unix user and to synchronize password and other account information with as little system administrator intervention as possible. Using a combination of technology from Microsoft and various scripts developed within the UNH Computing and Information Services group, we have created just such a system. For every newly created Unix account, an Active Directory account with an identical user name is generated. Password changes on the Unix systems pass the corresponding password update to the Active Directory domain controllers to assure that the accounts remain synchronized. This system has functioned for a full academic year with only minimal issues. With this infrastructure in place, we hope to be able to leverage it in other fashions. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
General Terms:
Keywords:
Peer to Peer - Readers of this Article have also read:
|
||||||||||||||||||||||||||||||||||