There was a big reorganization, merging the program I support into a new beast along with a few other programs that used to be sort of independent but have roughly... and I mean very roughly related missions. In real terms their missions are completely unrelated but happen to touch on some of the same populations sometimes. It was a transparent move to create a new SES position. But whatever.
So, I'm responsible for our primary IT tool, a database/web interface that allows the entire staff to do their jobs, document it, and report on it. It's evolved from a recordkeeping application into something that sends automagic emails, performs validation, etc etc over basically a decade of feature creep. Now it is essential to daily operations, as in if the staff can't access it, no work can really be done. I'm sure if it disappeared they could find a new way forward, but there would be a lot of down time while new procedures were established.
Anyway, this database resides on servers belonging to Network A, which also provides all our desktop support, interwebs access, helpdesk services, general IT shit.
Now, there is an enterprise-wide push to put everyone on random networks onto Network B. Someone decided that this reorg was a perfect opportunity to force us to move to Network B at the same time as physically moving offices to sit with our new amalgamated program office.
Sounds great, right? Except they didn't tell Network B that they would need to host our database and website... when they found out they said they would need a few months to sort out all the requirements. But we need to move right now! Ok, well then we can't host your shit.
Now, Network A and B don't play nice with one another. You can't access resources on one from the other... so if our computers and interweb are coming from Network B, there is no chance of reaching our essential workflow tool on Network A servers, in their present configuration.
I brainstormed with the application developers and we came up with some options:
1. Don't move networks until we can move hosted resources? - rejected, move has to happen right now, no waiting.
2. Ask Network A if they can whitelist some connections from Network B so we can use our shit - rejected, muh security!
3. Make our resources on Network A public-facing so we can get to them from everywhere and hope our authentication is good enough to keep the chinese from hacking us - not rejected outright - possible!
Our new program leadership counter-proposed some ideas:
1. Each person will have two computers on their desk, one connected to Network A and one connected to Network B.... wtf
2. Set up some VPN scheme so you have a Network B computer but only use it to VPN into Network A to do all your work... wtf
3. Leave some users on Network A and everyone can just tell them what they need updated in the database via email... wtf
Needless to say, this was kicked around amongst higher ups with no idea wtf they were talking about for all of the time we had to prepare for the move, so all the work to implement our 3rd idea had to be done in the last 2 days. Let me tell you this was a giant clusterfuck. I am usually very diplomatic, but I think I hurt some feelings on this one and likely burned some bridges.
Network B tech monkeys are now working over the weekend to get all the shit wired up, we'll see if it worked on Monday.
Anyway, the first big shakeup of the administration was a total clusterfuck, but at least I get a cube with a window out of the deal.