Mark, Gordon, Eric, Loren, and Klark

Dan

• (Klark) DHCP Challenges:
• : The committee resolved a few years ago to only use a single DHCP server and to require every machine to register to receive a lease (by MAC address). We currently have two DHCP servers and few public addresses. Folks are asking to not have to register machines to receive a lease. We need to rework our policy?
  • Do we want dynamic DHCP? Yes.
  • Do we want static DHCP? Yes.
• : Let's prototype Klark's proposal to give control to the end-user with exported logs etc.
• Revised open lab policy (Resolutions and Policy)
• : Let's post and deploy (midnight, devotional, and Sunday are no-console): start Spring semester. Post coming spring semester signs now. Replace with permanent signs in spring semester.
  • Eric: publicize the new late policy. No badges. Email Gordon to get on the list. List is checked dynamically. You must register for after hours building access and late pass. Two separate lists. Everyone who had badges before are on the list. Lists are cleaned with key audit annually.
• ostickets for unified ticketing system report (Dan, Klark, Loren)?
• : Webmasters are trying to resolve the LDAP issue. There are several suggestions from the campus CSR list. Alterus also has a help desk system and BYU has a site license.
  • Loren: Alterus
  • Klark: eval things from the CSR list
• Who to host the ticket system?
• Wiki content export report (frequency etc. to report to faculty)?
• MediaWiki upgrade path.
• CS Website redesign and merging HTML servers and content to a single server
• Computer in CS conference room (Klark)

• Virtualization in the Open Labs
• Windows 7 Image
• Spring Image Needs?

I adapted the information from the Spolsky article, incorporated some of the ideas we've discussed in out committee, and put a strawman version of possible training points on Loren's helpdesk wiki s://cswiki.cs.byu.edu/helpdesk/index.php/New_Help_Desk_Employee. Since this is restricted access, he may need to authenticate to show you. Feel free to hack it to pieces. Most pressing, perhaps, is settling on a more palatable term “customer” and the associated “customer service”.

The text looks great. We need to target it for majors other than computer scientists since the help desk folks have a breadth of backgrounds. Let's stick with the customer service term.

1. gmail for the department, Klark says
2. :“I've created the compsci.byu.edu domain with gmail and I've set up the addresses as well. However, the name has still not propagated and Google states that it will be another couple of days before it will happen. When everything is working, I'll let you know.”
   • Mark: and Eric play with calendaring.
   • Eric: explore google docs in the same domain.
   • Klark: open tickets for the redirect
3. : It appears that this is working, we need to publicize and document how faculty can use this.
4. We need to set up a monitoring system to determine why the back of the phone is often faster than the department internet
5. :Nagio server
6. :Did we get a bigger pipe to the university
7. Create a department mail server for cs.byu.edu with no dependencies
8. :We are working to configure it
9. After the problems at the beginning of the semester, Parris approved purchasing a mirror system that we could install new things on. How is this coming?
10. : Klark is working with a salesman
11. It seems like having BYU do the wireless is not happening. I think we should look into improving cs-wireless so it has better coverage
12. : Klark is working with OIT, lets keep this on the agenda
13. : We need to get cs-wireless working in 1170
14. We need to document the services we provide and make sure they are continually tested.
15. :Wikis
16. :Svn
17. :Web server for laboratories