Thanks, Jon!

We'll talk or email directly about Mr. Brownstein. You did right to reassure him about faculty and student involvement in the website.  I wasn't aware of the grant and its conditions; maybe Russ is. In any event, it all works to the positive.

It's a good idea to leave the computers turned on (in any school just about).  OTS pushes their patches overnight, and even though that is usually just once a week there is little point in trying to change the procedure day-to-day. Leaving them logged in to the shared student account also may be helpful, but we should talk about the interaction ofthe login/logoff process and the roaming/mandatory profile.

I'll aim to join you at the school on Tuesday, particularly to look at this stored profile thing.  The interaction is that when there is a roaming but non-mandatory profile, and the user logged in under those conditions, then when the user logs OUT from any client machine, the profile as it exists on that client is stored back to the domain.  So when there is a shared account in use at many stations, it can be tricky to get just the one you want stored and used thereafter.  (To get that one used thereafter, rename ntuser.dat to ntuser.man on the server profile folder for the user, that is, make it mandatory.)  This is something we did last spring, for the sake of getting the printers right primarily, but evidently the printers have been changed or the profile got messed up.  We might also rethink the idea of keeping it mandatory --thatworks for the printers, but the desktop shortcuts for programs are hard to get right for XP and W2K simultaneously.

Are there still some 98s running in there?? I ask because of the message you mention about names being too long.  If that's what it is, I'd suggest upgrading the 98s (or relegating them to a different kind of use, or disposing of them), rather than renaming shares to cater to the limitations of 98s (if that's in fact the issue).

 ==Mitch