CalNetAD Planning Committee

March 19, 2002

Room 775B, Tan Hall, 10-12 PM

Updated: 03/20/2002

Agenda

1. Initial Production Status

2. New CalNetAD members

3. Planned Infrastructure improvements

4. Test Machine

5. Discussion of CalNet Directory integration requirements for faculty, staff, and students

   Please refer to the directory integration problem statement page as a framework for the discussion of the integration agenda item at the planning meeting.

6. Demonstrations:

   • Quest Software will be presenting on 4/8 in 236 Evans at 3:00 PM.
   • Okena may be presenting their IDS solution on 3/25 in 60 Evans at 3:00 PM

    

7. Other Business

Notes

Initial Production Status

The CalNetAD project has moved into its Initial Production Phase. All of the GPO templates have been loaded into the test environment and tested. Back-up restore and other disaster recovery procedures have been tested. After the IIS GPOs have been tested by COIS, the GPO templates will be moved into production.

New CalNetAD members

The following units will be joining CalNetAD:

• IST Operations (IST-OPS)
• Ocean Engineering Graduate Group (OE)
• Workstation Microcomputer Facilities (IST-WSS)
• CCS-SDA is also joining and will add new servers to the CAMPUS domain.

Planned Infrastructure improvements

A new Dell 2550 server has been purchased to serve as a third domain controller for the CAMPUS domain. The project team is currently looking at several sites outside of the Evans basement machine room as a potential home for the DC.

Test Machine

The test machine (Dell 2550) and environment (VMWare Server) is complete. VMs have been established for test versions of the KDC, DNS, and Active Directory domains and their controllers.

Discussion of CalNet Directory integration requirements for faculty, staff, and students

Karl Grose began the discussion by outlining CalNetAD user naming conventions for CalNetID and local user accounts that will help avoid name collisions when directory integration is implemented. (See also the CalNetAD Naming Standards document for additional information).

There was general agreement that faculty and staff user accounts should be loaded into departmental OUs. It was also generally agreed that the home department code from the Payroll Action Form (PAF) would be useful as the department designator to map to CalNetAD OUs. However, it was also agreed that changes to the PAF Home Department Code would not be sufficient to cause an automatic move into or out of an OU without prior agreements from the involved parties. Issues that need more discussion are dual appointments and account deletions.

There was a general discussion of the problems surrounding student user accounts. There were no objections to the CalNetAd Project Team's suggestion of initially loading students into one OU.

Other Business

Kevin Burney asked about the progress of getting CalNetAD included in the Remedy trouble ticket system. Mike Blasingame informed the Committee that work is in progress to modify the Remedy system to include CalNetAD. When the Remedy changes are complete, local OU administrators will be able to call the IST Trouble Desk, report a CalNetAD problem, and get a trouble ticket number. The administrator will be informed when the trouble has been corrected. It was also suggested that a web page displaying all of the open trouble tickets could be a helpful tool for CalNetAD administrators.

John Ives gave an update from the Security Subcommittee. He reported that the subcommittee had reviewed and signed-off on the site GPOs. Another meeting has been scheduled for the subcommittee and notice has been sent out to the members. John wants more staff devoted to full time security auditing. The team is looking into automated logging and auditing products to minimize FTE and offer distributed auditing and logging to OU administrators.