"Apparently can't trust Windows Server 2003 farther than I can throw it. And it's bolted into a rack."

That's what I typed into the windows downtime manager when it asked me why it was unexpectedly shut down earlier tonight - because it locked up. It pretty well describes how I'm feeling about it right now. For some reason one of the domain controllers doesn't seem to want to quite authenticate with the other and sync because the load is high. The load is high because of the migration tool, which was running on both. In defense of 2003, I think some of it may be caused by the domain which is going away, which was acting a little goofy today. I had to demote a domain controller to even connect in a mode where I could transfer accounts off of it. Now that the one migration is running, I apparently need to wait until it's finished to do the others. Oh well, should take long enough I can sleep without worrying about it finishing too early. I also get to run some other processes on the accounts while waiting for the roaming profiles to transfer (the accounts themselves finished long ago).

At the rate it's going, I just hope it finishes by late evening on Saturday, otherwise it's gonna be interesting as I'll have to move schedules around. I think I have some classifications of users I can stage groups on though (given we have a bunch of "likely-not-eligible-but-we-don't-want-to-track-them-down-right-now" accounts, those can be last on the list). At least the systems seem to be responding reasonably well the one is up and stable.