Monday was just miscellaneous stuff. Fixes on the OS X side, eliminating another account which existed in more than one domain, etc. Apparently the Help Desk got a bit of traffic as I heard some complaining, but nothing that hit me this time. Finished off the day by getting a call asking for some help connecting a remote office to their NT4 server. Wouldn't be a big dael, except the server team had no clue they had a server out there (it was apparently before they merged in, and we were never told it existed). Now to see if we can get a trust going followed by replacing that with a machine where we don't have to worry about someone's laptop getting infected and coming back to work to take down the network. Lunch was C1, which was cool. We chatted quite a bit with Dan, which is always good. Not often you hear your waiter say some of the stuff he says... Read lots of AD planning stuff, specifically in relation to Windows Server 2003. Not sure if we'll go that route, but we'll see what benefits it'd have. They have some interesting hardware requirements for their systems. Academia has a much different usage pattern than corporate, which makes everything need to be taken with a grain of salt. Unfortunately that means we have to guess, and half the time means overshooting excessively and the other half it barely works and is slow. Such is life I guess, although you know it's bad when the MS people feel sorry for anyone in an academic environment. Tuesday was gonna be my day to try and plan out the AD structure before we make any massive changes. That didn't happen unfortunately. Ended up looking a some Storage Server 2003 stuff, and then investigating claims of slowness on the student file server. I poked a bit and changed policies to hopefully cause student accounts to be less dependent on realtime access to the server (with the tradeoff of slightly longer login/logout). Unfortunately the policy didn't reverse well, at least in the short term. Maybe it'll happen tomorrow. Then told everyone to basically not update any Windows documentation until they hear otherwise from me, which probably won't be until mid-summer. Hopefully we won't make too drastic of changes and create too much of a documentation crunch. Spent a good chunk of my evening hooking up my myth box again. I had configured it to boot in runlevel 3 and left it sitting in a corner just recording stuff. First I had to figure out how to get it to boot into X without a mouse. Not too bad, assuming I don't want to be able to plug a mouse in and have it work. I had to wire up my kvm and a bunch of VGA cables to get it into my av system though, which is sorta a mess right now. I need to do something about cable lengths with the new system. If I can get the AMX stuff up and running I could leave a lot of stuff behind the rack rather than in it and save space, which would be nice if that works. Anyways, I started off with an upgrade of mythtv, and now am not sure why the internal audio doesn't work. I finally loaded in the right modules and the mythvideo component plays fine, but the internal recorded programs doesn't. Sorta annoying to have that problem... Then there's this whole audio sync thing. I think that's an issue with either the divx files themselves though, or with the ac3 decoding. It only is really noticable after a couple hours of the movie (and then only a second or two without compensation turned on). I'm not sure how I'm gonna fix that since it's not a constant adjustment I can throw in either. Well, didn't get much done for visitors tomorrow, but oh well, such is life.