UNITED STATES

1. UNITED STATES

2. Understanding NDS forDirectory-Enabled Solutions David Condrey, LAN Systems Manager davidc@clemson.edu Clemson University Jeremy Campbell, Information Resource Consultant jerm@clemson.edu Clemson University

3. CLEMSON Novell Directory Services (NDS) and the Computing Infrastructure U N I V E R S I T Y A real world example: Division of Computing and Information Technology

4. Background on Clemson information systems Mission and support structure Userid management Network design Server and network access Public access labs Printing Electronic mail Intranet Authentication server Futures Agenda

5. Background onClemson Information Systems

6. Background • Large systems background • Strong development shop • Mainframe and open systems expertise • Departmental LANs ruled 90’s until Novell Directory Services (NDS) • NDS populated in Summer 1995 (36,000) • Departmental LANs gone—more centralized management of the network • NDS is centerpiece of security and authentication

7. Mission and Support Structure

8. Mission • Provide computing infrastructure • Empower users and departments • Provide guidance in selecting solutions based on industry standards • Deploy solutions to meet the needs of institutional computing • Provide user support and training

9. Defining Groups • Network services • Supports the physical network (routers, hubs, backbone) • LAN systems • Supports application, group, and personal data servers • Client Support Group (CSG) • Supports faculty and staff via Technology Support Providers (TSPs)

10. Defining Groups (cont.) • Systems Integration Group (SIG) • Supports students and departmental labs • Computer resources • Assists with user account problems • Division of Computing and Information Technology (DCIT) sponsored • College consultants • DCIT sponsored person and college sponsored person(s) that help support the end users of the college

11. Defining Groups (cont.) • Technology Support Provider (TSP) • Supports faculty/staff end users • Help desk • Sponsored by DCIT to assist end users

12. Support Structure 2 Computer resources Client support Systems integration • Support is based on a four tier model Problems 3 1 4 TSPs Network services Faculty Staff College consultant LAN systems Students Help desk Resources

13. Server Strategy and Management • Novell and Windows NT servers maintained by DCIT • DCIT provides hardware and Network Operating System (NOS) • DCIT administers backups • DCIT performs user administration • Group maintains data and security with help of a TSP • Virus protection and software metering

14. Userid Management

15. Automatic Userid System (AUS) Personnel Other Admissions NDS MVS AUS Other UNIX

16. Automating User Maintenance Personnel Other Admissions MVS FTP AUS Old Method Daily UIMPORT run TCP/IP Real-time • Add users • Modify user attributes • Delete users Summer ’97 NDS USRMAINT.NLM

17. Network Design

18. Physical Network Design 100BT Switch Server FDDI T1 Server 100BT Server Server Server Server Server

19. Tree Design

20. Every Person Has a Place Organizations ClemsonU Students Misc. Employee A to Z A to Z A to Z

21. Every Group Has a Place ClemsonU Users Athletics DCIT CAFLS CES Forestry Research Dean's office

22. Partition Design Students Employee Athletics DCIT A CSO CSG APS B A B Z Z ClemsonU

23. Use Dedicated “ROOT” Servers forNDS Replicas FDDI (ITC) CU-ROOT-2 100BT Switch R/W for all Group Server Master for all CU-ROOT-1 R/W optional CU-ROOT-3 R/W for users “A” to “Z”

24. Distribute Network Management

25. Login Script Design • Based on profile scripts and user scripts • No container scripts • Use base profiles • EMPLOYEE • STUDENT • Base profile includes high level organizational scripts based on membership • Organizational scripts controlled by TSPs • Organization scripts may include departmental scripts managed by others

26. Script Design & Management .EMPLOYEE.employee.clemsonu .GROUPIFS.employee.clemsonu .AG.cafls.clemsonu .ENG.ces.clemsonu .Forestry.cafls. .BioE.ces. .Civil.ces. ISALAB User Script

27. Server Timesync Hierarchy Server Server A D Server C Server Server B E External source Prim Secon Ref Prim Secon

28. Server and Network Resource Access

29. Personal Storage (User Data Servers) Office, lab, or dial-in Any faculty or staff member EmployeDn Dorm, lab, or dial-in Any student StudentDn

30. Personal Data Server Configuration EmployeD(2) StudentD(5) Processor Dual Pro–200 Pentium II–300 Memory 1024MB 512MB Disk 90GB (RAID5) 50GB (RAID5) Replicas None None Home ~11,000 ~25,000 directories Base quota 100MB 25MB

31. Collaborative Storage—“Group Servers” (Faculty and Staff) EmployeD Group Server1 Group Server2

32. Collaborative Storage— “Applications Servers” (Students) StudentD Applications Server (N)

33. Group/App/Root Server Average Configuration Group App Root Pro-200 P-200 P2-300 128MB 64MB 384MB 18GB 9GB 4GB Possible R/W None All replicas 25–250 users 25–250 users 250–800 users*

34. Collaborative Storage (Faculty and Students) EmployeD App server Group server1 StudentD

35. Faculty/Student Collaboration • Faculty member wants to put data on the network that students can use • Student submission of work to faculty • Students collaborate on team projects with assistance from faculty member • Students and faculty collaborate on projects or assignments • Publish web pages as a team or class

36. Faculty and TSP/Client Support Management Read Only Group Server1 Create Only Read Write Teams R/W with Tgroups

37. Collaborative Storage and Network Bandwidth Group Server1

38. Public Access Labs

39. The Virtual PC

40. Outline • Environment for the Virtual PC (VPC) • How the current VPC environment evolved • Mechanics of the VPC • Setting up the computer • Boot time • Login and login script • User Profiles • Software involved • Future directions

41. Standard Lab • Standard set of applications • Standard operating system • Contextless login • Standard drive mappings • Identical hard drive contents

42. The Environment as Seen by the Machine • Data servers • Application servers • Hard drive image • Handling locations and hardware

43. Goals of the Virtual PC Paradigm • Easy maintenance • Provide global access to password protected network disk space • Allow user to customize his desktop • Same environment (“look and feel”) regardless of location, hardware, or facility ownership

44. Evolution • Pre-NetWare • Windows 3.11 under NetWare • Windows 95 under NetWare

45. How It Happens to the User

46. Constructing the Machine • The rebuild disk • REBUILD <location> <pctype> {options} • Importance of Virtual Loadable Module (VLM) Client

47. Boot Time Events • Location, PC type, “ISALAB”, and other environment variables • Some registry updates to ensure default desktop appearance and server failover keys

48. Contextless Login • Can’t teach end users what a context is • Using commercial product because NetWare Software Developer Kit (SDK) lacks information

49. The Login Script • Perform some basic actions • Perform group-specific actions • Perform lab actions • Load profile

50. Isitcool—Failover Applications Server Attachment ISITCOOL NLM Work- station 1. Using IP, get info from primary app server Isitcool. 2. If attach failure or Isitcool reports no, try next server. 3. Attach to server using NetWare client. YES! Lab 1 NO! Isitcool? NO! Applications Server(n) ISITCOOL NLM ISITCOOL NLM Workstation Disk Image Applications Applications Server(1) Applications Server(2)