
<h2>School Hours Summary</h2>
<ul>
	<li>Canter 1:20</li>
	<li>Fermi 2:15 + 1:30 == 3:45</li>
	<li>Leadership 1:20</li>
	<li>Murray 0:40</li>
	<li>Sexton 2:30 + ~1:30 == ~4:00</li>
	<li>Wadsworth 3:00</li>
	<li>Woodlawn 3:30</li>
</ul>
<strong>===============================</strong><strong> </strong>

<hr />
<h2>Status on previously deferred items, ongoing projects, and specific to-do's</h2>
<ul>
	<li>Planning for new system of regular check-ups for selected labs
<ul>
	<li>Canter only lab (305?) -- Russ or Mitch or NSP</li>
	<li>Wadsworth 221 (old desktop wireless) -- Mitch or Russ or Noah, or take reports from techco /teachers [Townsend, Warden]</li>
	<li>Till 206 (previously unattended lab, now Media Center auxiliary site) -- Jimmy, Christie, Mitch, and LMS/Teachers [Gaal, Igay?]</li>
	<li>Establish a rota of CUIP and school characters to do the checking and reporting</li>
	<li>For some of these, consider scheduling a weekly "maintenance hour" which would be blocked out from class sign-out. (If we do this, and if it's at a time the lab could be productively used, then we need to be religious about actually sing that time as designated.)</li>
	<li>In any case [whether or not there is a maintenance hour], get a reservations calendar page posted right at the door</li>
	<li>If those work out, think about adding Fermi</li>
	<li>If those work out, think about adding Sexton 322</li>
	<li>If those work out, think about adding Mollyson.</li>
</ul>
</li>
	<li>Reports from that system:
<ul>
	<li>Canter 305: not implemented. But Russ mentioned it to Preetha when we visited the lab.</li>
	<li>Wadsworth 221: discussed with Russ and Sharon, email discussion with Noah</li>
	<li>Till 206: not implemented. (In theory, this was <em>already</em> sort-of in place, with Thurman doing the managing and receiving reports, Jimmy doing the regular periodic checkups, and Christie / Lee Ann / and I doing the baseline overall check-and-clean. The was really the separate original case from which the idea of formalizing it for a few schools developed.)</li>
	<li>Fermi: At meeting with principal and AP, Shaz brought this up.</li>
</ul>
</li>
	<li>Sexton NSIT machines. Last week: installed two. To-do for this week: install remaining three; remove raided case from Number 6.
<ul>
	<li>Result: completed installations of remaining three.</li>
	<li>Left to do: remove hulk</li>
</ul>
</li>
	<li>Sexton classrooms, check existing computers, especially for wireless.
<ul>
	<li>Ms. Khan: not done</li>
	<li>Room 302(?): nt done</li>
</ul>
</li>
	<li>Sexton laptops, seeMr. Smith:
<ul>
	<li>Sara reminded him (and me) about these, but no substantive progress this week.</li>
</ul>
</li>
	<li>WPMU (WordPress MultiUser). Previous week: “To do: Make decent text front page. Prune themes and plugins. Continue staff testing before general release.” Last week: "Still need to do the front page etc. Not sure if staff tryouts are proceeding apace."
<ul>
	<li>Some staff testing done this week.</li>
	<li>Press SR on issue (or go behind his back!:) ) of releasing a little NSP expertise time from their school hours to do the themes and plugins pruning. Result: Erin will work on this.</li>
</ul>
</li>
	<li>"WP 2.1 — ugrade most freestanding weblogs. Distribute themes and plugins, taking care not to clobber existing mods." combined with "Make sure all bloggers have access to special themes or plugins via shared collection ...Need to separate the plugins/themes from the other upgrade files; revise `newblog' script so it <strong>does</strong> pick up all the themes; and establish the upgrade copy routine so it <strong>does not</strong> clobber anything already in place (because it may have been edited by our bloggers!), yet <strong>does</strong> supply any missing ones ".
<ul>
	<li>This week: revised the newblog script on main server, to pick up core WP files and extra themes/plugins from different places. This doesn't do much in itself, but the separation allows for the upgrade to proceed peacefully.</li>
</ul>
</li>
	<li>Followup with Till engineers on their office computer. Last week said: "Someone should continue helping Mr. Blaze learn his way around the computer, and check his CPS email. Possibly the computer should be joined to INSTR, if they don’t object to needng to sign on." Check with Sudduth on that.
<ul>
	<li>Not done.</li>
</ul>
</li>
	<li>Check and update NSP enrollments in Mailman maillist and as users + categories in reporting blog.
<ul>
	<li>Result: done, including addition of Ariel M., Louisa, and Kathy to mailing list, reporting blog sign-on, and reporting blog categories.</li>
</ul>
</li>
	<li>“Deferred longer term: Trial installation of Skeletonz CMS” or other CMS. Last week: –Still deferred
<ul>
	<li>This week: Still deferred.</li>
</ul>
</li>
	<li>“Carried forward:: Installation and tryout of Retrospect for desktop backups in CUIP lab”
–Last week: "Still a to-do<strong>. BUT do not defer forever the basic shared-drive setup for Sara and Shaz! Do that sooner!"</strong>
<ul>
	<li>This week: CDs initially not found in lab. Need to bring copy from home.</li>
</ul>
</li>
	<li>“Carried forward:: Track down my writeup in email (to Duff) to put inWiki documentation for INSTR at<a href="http://techwiki.cuip.net/HowTo_Update_Student_INSTR_Accounts_with_Legacy_SI_Data"> http://techwiki.cuip.net/HowTo_Update_Student_INSTR_Accounts_with_Legacy_SI_Data</a> and update <a href="http://techwiki.cuip.net/HowTo_Get_Student_Data_from_Legacy_SI">http://techwiki.cuip.net/HowTo_Get_Student_Data_from_Legacy_SI</a> with notes about not relying on floppy diskette.”
=-- Last Week: "Still a to-do. Also this week there was Yet Another email I ean towikify if I can remember what it was!"
<ul>
	<li>That additional item was the emails to Jimmy about power-on password and to Linda Sudduth about the related idea of a BIOS-setup admin password.</li>
</ul>
</li>
	<li>“Carried forward: Doing something with the extra NSIT machines we held back — especially after whinging so much about needing a computer work table!”
– I haven’t dealt with these, but Russ and Christie have in various ways.
<ul>
	<li>Most of the 400s turned out short on special RAM. We will probably finish these off between staff use and passing along to a community project who have contacted Duel (tho it may be all they need is monitors).</li>
</ul>
</li>
</ul>
===============================
<h2>To-do items added this week for next, or new continuing projects</h2>
<ul>
	<li>DNS settings update for office computers
<ul>
	<li>Did my own desk</li>
	<li>Next week: Do the other desks or remind the people</li>
	<li>INFO: The two new manual DNS addresses are 128.135.247.50 and 128.135.249.50</li>
</ul>
</li>
	<li>Send deferred email draft introducing Sanjaya and Joe Mills, for desktop background management technique to be brought over from Ray to MLA</li>
	<li>Dumas: Get Oadie info about printer scripts.</li>
	<li>Wadsworth: Finish student logins update with Sharon.</li>
</ul>
<strong>===============================</strong>
<h2>This week's activity not at or for a specific school</h2>
<strong>------------------------------------------------</strong>
<h3>CUIP Team</h3>
<ul>
	<li>Overall (I was not involved in all) we made four NSP-school-Introduction visits (including one transfer).</li>
	<li>I advised Craig on troubleshooting a web-form problem.</li>
	<li>Discussion with NSP VISTA Michael about a detail of the NSP web site. They are maintaining the site on their own now, that's good for all!</li>
</ul>
<strong>------------------------------------------------</strong>
<h3>eCUIP</h3>
<strong>------------------------------------------------</strong>
<h3>Chicago Web Docent</h3>
Worked with Julia to clarify the logins and upload for updating the CMAP student flash file. We also resolved another of those pesky password contradictions.

<strong>------------------------------------------------</strong>
<h3>CUIP Office — Facility and Computing</h3>
<ul>
	<li>Per NSIT e-memo, update DNS settings on office computers.</li>
</ul>
<strong>------------------------------------------------</strong>
<h3>CUIP Servers</h3>
<strong>===============================</strong>
<h2>This week's activity at or for specific schools</h2>
<h3>Canter</h3>
Friday for ~~1:30 with Russ and Preetha
<ul>
	<li>NSP school intro for Preetha. Didn't get to meet Dr. Epps or Ms. Ahad, but Russ gave overview of the school and arranged a WP tutorial forPreetha to come to.</li>
	<li>The odd server spontaneous shutdowns are NOT (as I was speculating) coming from an automatic-install setting for Windows Updates. There have been 4 of these events since the new year began. Time of day approx. 1PM, 3PM, 6PM, 9PM; some of these while school was in session and there was no thunderstorm or power outage. We'll continue to wait and watch.</li>
</ul>
<h3>Fermi</h3>
<ul>
	<li>Monday w/ Christie, 2:15. We continued the room-by-room survey. Circumstances put us into the other mode: wedid not get much farther along the hallway, but did a pretty thorough job in the rooms we hit.</li>
	<li>Thursday w/ Shaz and Christie, 1:30 (including waiting time which we turned into impromptu rump CUIP staff meeting) -- overview meeting with Principal Dr. Sanders and AP Mr. Taylor.</li>
</ul>
<h3>Leadership at South Shore</h3>
<ul>
	<li>NSP Introduction, Ariel Marcus. (With Sara and Russ.) We met with Mr. Ruffin and Principal Patrick, and visited the rooms where the tech action currently is.</li>
</ul>
<h3>Murray</h3>
<ul>
	<li>Friday for 0:40. Checked in with Joe Mills, discussed summer. Fixed a student's weird roaming profiles problem; showed Joe how an admin can take ownership of files when necessary, and together we figured out the file-deletion fix for clearing a roaming profile.</li>
</ul>
<h3>Ray</h3>
<ul>
	<li>Email discussion w Mary, Erik, and both NSPs about role of the two Windows servers. I was happy to see SP's report this week on srv01's apparent improvement in network share speed for ghost purposes.</li>
</ul>
<h3>Sexton</h3>
<ul>
	<li>Tuesday for 2:30 w/Sara. We installed the remaining 3 NSIT computers; to Ms. Rose's office, to room xxx, and to Ms. Jackson's classroom on first floor.</li>
	<li>Friday for ~1:30 w/ Sara. NSP introduction with Louisa. Met Principal Bradley, AP Mr. Smith , TechCo Ms. Rose, Ms. Khan and her UTEP student-teacher, and Ms. Ludlow. Also a good once-over for the lab proceedures.</li>
</ul>
<h3>Wadsworth</h3>
Thursday 2/08 for 3:00 with Russ
<ul>
	<li>Briefly stepped into 1st floor new lab to look at progress. Wiring and furniture setups both are going forward well.</li>
	<li>Lab 321 with the laptop carts: In very good shape, they could start using any day now; need a usage plan, but there are no other major technical or logistic obstacles. The printing seemed to be in trouble, until Russ thought to reboot the Wireless Bridge devices, which cleared it right up.
<ul>
	<li>Let's get full info about the Wireless Bridge device from Linksys/Cisco, including part no. and if possible cost. Share with other schools needing wireless printing solutions: Price (where ....), Sexton, maybe Dumas if I understand Oadie's inquiry.</li>
</ul>
</li>
	<li>Ersatz lab 221 not doing too badly. Look into putting a delay into the printer script, it might stop having those connection errors. To almost everyone's surprise, computer #6 was working fine! The touch-every-station-for-INSTR operation still not complete.</li>
	<li>I coached Sharon through the first half of the INSTR student login updates operation.</li>
	<li>Issue with Ms. Cooksey's laptop.</li>
</ul>
<h3>Woodlawn</h3>
<ul>
	<li>Monday w/ Mischa and Christie, for 3:30. We checked out the laptops from the rolling cart. We got through all 21 that were on hand. (Where are the other three?) On each: verified that school/cps would work; moved from the old WOODLAWN1 domain to INSTR; if Symantec Update was causing problems for Trend, uninstalled Symantec; if a text file was opening in Notepad on login, removed it from the startup folder; etc.</li>
	<li>The school does not yet have fully-formulated plans for using these. We briefly discussed how some other schools are succeeding with wireless laptop carts. Carisa thinksthere are wireless PC-cards for these, she will look around for them.</li>
	<li>Someone will need to reassemble the chargers into the cart, plugged into the cart's power distribution, so that it can be used to charge them up. (Today we were using the chargers outside of the cart, as power sources for running the computers from current.)</li>
</ul>