The hardware that is backing our upgrade/migration to Exchange 2003 has been delayed. A shipping error somewhere, and Compaq can't tell us when they'll have the hardware available to ship. "Backordered." This has the unfortunate side-effect of pushing our upgrade of this product to the period between the end of second summer term and the beginning of fall quarter.
The admin who has put together the Exchange migration process will be on vacation for most of July. Its one of those "use it or lose it" things for vacation balance. After my predecessor left and before I arrived there were only two admins to answer phones, and that made for some interesting scheduling of vacations. Both of the admins have balances that'll likely get dumped come their anniversary dates. Both of 'em have been taking lots of vacation now that I'm here.
Anyway, Exchange is effectively halted until August. Which runs it right into our planned upgrade from NetWare 6.0 to NetWare 6.5. Since that particular migration involves taking down the cluster for non trivial amounts of time, it will HAVE to happen during the dead period between terms. Have to have to. We only get three weeks a year to do these kinds of upgrades and if the technology isn't there... we wait another year. We'd like to try NetWare 7, but it won't be out in time. We're also upgrading Banner during this period if I've read the notices correctly.
Because these two projects will end up overlapping, the admin who planned the Exchange upgrade will not be able to also plan the NetWare upgrade. That task has fallen to me, and I'm very happy to have it. This is exactly the sort of thing I was doing at OldJob and haven't been able to do at this job. I look forward to this project as a way to prove that the CNE after my name is well earned, not just a paper one.
As I look into this project I see that my planning skills are beginning to atrophy. Not good. I need this in order to stay sharp.
The admin who has put together the Exchange migration process will be on vacation for most of July. Its one of those "use it or lose it" things for vacation balance. After my predecessor left and before I arrived there were only two admins to answer phones, and that made for some interesting scheduling of vacations. Both of the admins have balances that'll likely get dumped come their anniversary dates. Both of 'em have been taking lots of vacation now that I'm here.
Anyway, Exchange is effectively halted until August. Which runs it right into our planned upgrade from NetWare 6.0 to NetWare 6.5. Since that particular migration involves taking down the cluster for non trivial amounts of time, it will HAVE to happen during the dead period between terms. Have to have to. We only get three weeks a year to do these kinds of upgrades and if the technology isn't there... we wait another year. We'd like to try NetWare 7, but it won't be out in time. We're also upgrading Banner during this period if I've read the notices correctly.
Because these two projects will end up overlapping, the admin who planned the Exchange upgrade will not be able to also plan the NetWare upgrade. That task has fallen to me, and I'm very happy to have it. This is exactly the sort of thing I was doing at OldJob and haven't been able to do at this job. I look forward to this project as a way to prove that the CNE after my name is well earned, not just a paper one.
As I look into this project I see that my planning skills are beginning to atrophy. Not good. I need this in order to stay sharp.
That's a lot of upgrading, speaking as a student and an Exchange user I certainly hope it gets worked out. Isn't it fun when stuff like a late shipment messes up a schedule? :(