Everything has become a blur. Thursday evening the file server which was being phased out this weekend lost two drives on one of the arrays. Turns out one worked well enought I could bring it back up and get a backup, but some stuff was definitely lost. So starting at like 8pm I jump into trying to get that part of the weekend's migration done that evening. Without being able to script anything first... :( I did manage to get most of it up and running though, and wasn't up all night. Friday was squashing bugs from the night before. Permissions problems, restoring lost data from earlier backups, plus trying to plan for that night/weekend. Friday afternoon my new powerbook was dropped off at my office which was good news. The bad part is that the only thing I was really able to do with it was plug it in to charge it since I was so busy. Friday evening involved locking down everything, starting backups, and doing the active directory part of the migration. My part was active directory. Migrating the users and groups was the easy part. The hard part was then sorting out all the groups. This process involved matching groups up with the department and renaming to match our new official short name for it. Then finding all user login scripts, matching up the users to the groups defining new policy application, and then migrating all the scripts over into the policies. This process actually went pretty smoothly, and was working fine. The restores finished after for most things smoothly and the exceptions were dealt with. Sunday I was woken up by my phone ringing, alerting me to the fact my dad's computer wouldn't boot. That's never too fun to deal with, especially when backups are questionable. After working on more of the login script stuff (it went smoothly, definitely not quickly), it was family time since it's that holiday. We all went out to eat, and on the way stopped to get a new hard drive for my dad's computer. That was good, but setting up the thing again wasn't. Windows 98 can be a pain... The old drive did run well enough to copy stuff off it, although fsck didn't like some stuff and couldn't fix it (just exited). I'm curious how much of the data is corrupted. That was left in a semi-usable state for him to finish installing. Monday was worse than usual. Something about the policies and the users didn't get along well and people weren't getting their drives or in some cases were getting random drive mappings that no scripts pointed to (still not sure what was causing those). Ended up fixing that in a way I didn't want to (converted domain local to universal so it gets passed in their AD credentials), but at least it's working. So far my guess is something with doing the group lookups combined with tons of hits from SID History lookups effectively swamped the DCs for a short time, and the multiple retries kept them a little slow. Sometimes drives would map minutes after login when we were first troubleshooting. Had to sort out some manual drives people had done as well as just wrong login scripts too. Plus more restores since we lost those drives on Thursday. At this point most things are fixed I think. Hopefully no new surprised tomorrow. I have a few things to clean up, and ideas about how to handle other things before the next updates to try and eliminate as many items depending on the old SIDs as possible. It's interesting to see some of the weird looking permissions that can result though when multiple SIDs for the same object but with different permissions exist. I'll just be happy in a few months when the whole structure stabilizes from all this object moving (with the way AD works these changes mean two objects for each one for about 60 days for replication purposes). These next couple weeks will hopefully mean a semi-break from AD stuff though (finally). Anyways, I did get a chance to get the powerbook configured decently for my purposes. I'm managing to load the thing down pretty well (I had the CPU pegged most of the day and I was trying to be nice and close things I wasn't using). It makes this intersting sound when the CPU is loaded too, but Ted might look at that tomorrow so we'll see. Hopefully there's nothing really too wrong with it. For email I'm sorta using Thunderbird. I have issues with it's GUI. We'll see how long it sticks around before I go to pine or something.