A white Christmas?

As temperatures drop to brass monkey levels, the chance of snow lingers, just in time for our company Christmas party this Friday! So it could be a white Christmas after all...
Why are we having a Christmas party in January? It's not calendar iconoclasm (more's the pity). The official line is that when we merged this year, we couldn't anticipate how big the company would be when booking a venue. The real reason is a combination of tight-fistedness and incompetence. We always knew the merger was happening, but didn't book anything early enough and balked at the prices of the venues that remained.
I'm steadily beginning to appreciate the gap between brewery and piss-up in the merged company's competencies. Example.
I've been trying to push an internal knowledge management initiative. We were almost ready to launch a new portal providing access to all our documents and people in time for the aforementioned Christmas party.
Then "technical support" got their mitts on it.
Their contribution was to:

1. switch the domain name settings so now a quarter of the staff can't access it;
2. move a third of all our documentation to a new file server without telling anyone; it then broke and it'll take 4-6 weeks to fix.

The adage of "if it ain't broke" rarely applies to the systems administrator mentality. But it appears here that the idea of fixing broken things doesn't apply either.
*** Updated ***
And there's still more... having sent the content authors a user guide telling them how to add content, one has now come back telling me that some people can't see the content he's entered. Did he enter it into the portal? No. What am I meant to do with these people?