OK, i'm sitting on a train departing at 7:29. it's kinda pissing me off, given that this is, after all, a freaking friday. so i'm feeling just a tad peevish.
my train won't pull into my station until around 8:36--according to the schedule, at least. yeah, right...that's so gonna happen. mm-hm.
what kills me of course is that there was no way that this could have been avoided, i don't think. and it's all the damned new server's fault.
we've been running a jury-rigged network set-up for the past half-year or so. it was intended as a stop-gap measure. but the boss kept putting off pulling the trigger on the decision to buy the server. every time he did, i knew he wouldn't actually make a decision until something forced him to take it seriously. well, that finally happened: we can't do something critical for a new customer w/out the added horsepower the new server would provide.
now, i'm what passes for an IT department in my office of 6 people. i'm not an IT guy. i'm a relationship manager. i can wear the IT hat for a little while, but honestly, it just doesn't work well b/c while i can do general PC support, or even in some cases some trickier things, i just don't have the kind of in-depth knowledge you need to fill that role properly. no, that's what we've got our consultants for.
now, when you move everything from one server to another, this normally requires some downtime. in a windows network, you have to add all the machines to the new server (domain). OK, no big deal. however, windows has a really delightful little quirk: it's too damned stupid to know that when you do such a thing, a user on that computer has to have all of the files associated w/ him or her to the new domain as well*.
be that as it may: do you know how much data a user can put on a machine in just a year? i don't know about anyone else, but i had to move around 12 gigs of data. that's 12000 megabytes. why is it necessary to move everything and chew up the hard drive even more?
and do you know how long it takes to copy that much data? to the new server? OK, that was a rhetorical question but if you didn't know, don't ever try moving that much data onto a USB drive. ever. only heartache can possibly be the result.
and why o why is it so all-fired important important to make this process so painful and slow? or for that matter, why in the world would anyone want to put a user's personal documents on the local hard drive of the user's PC instead of on the server by default? you know, a server? something that routinely actually catches the back-up process that your server does?
there's a bottle of gin w/ my name on it. and mr. bottle and i are gonna get very well acquainted tonight.
gah!
ed
*i need a M$ geek to explain to me why in the hell that makes any gorrammed sense whatsoever, and further, why it's necessary for windows to throw everything specific to the user in so many different damned places. what kind of network admin has never had to migrate domains, esp in a large network? you would think that w/ the corporate world's tendency to reorganize, they would make such a thing painless, wouldn't you? damned redmond marketing geniuses...



