I had a really hard time convincing a large, corporate client to setup such basic things like a version control system, a central bug tracking system, or any kind of project documentation repository. Oh, did I mention this was only three years ago? It's 2007 and you're not using version control? Anyway, one day, another consultant who sat next to me got laid off and the company's IT guys never came around to remove his computer. So, I moved the computer into the cabinet over my desk and used it as my "phantom dev server" or alternatively "The Travis" (after our laid-off compatriot). I even used it as a staging server for testing deployments. There was one time that a clueless cable-jockey came up looking for the machine, I told him someone had come for it months ago, and we never heard from him again.
Eventually, I developed a simple content management system on the product website because the company's policies were preventing us from making copy and FAQ changes as fast as we needed. Unfortunately, I couldn't get approval to do the project, even though I had a little bandwidth and it was something we really, really needed. I told my confidant in the company what I was doing and he ran interference for me for two days while I cranked the code out. We had to wait a month for another project to get finished to slip it in along-side an approved site deployment, but once it was in the wild, our lives became incredibly easier.
We almost let the cat out of the bag once when we made a change too quickly, though. Management wanted us to change some of the contact info on the site, and to change most of the branding of the site. Since I setup everything to be hosted out of the CMS, including stylesheets, no deployment was necessary. What should have taken two weeks (1 day to finish and then 9 days of bureaucratic shenanigans), took only one day. The plan was to wait the 9 days, then tell them about the change, and use the time to get caught up on support tickets and other "secret" programming going on (like a complete rewrite of the desktop product software, this time without VB6... in 2008). One of the execs dropped into our area for an update, and the stupid phone-support guy blabbed about "oh yeah, that's already done." I stabbed him in the leg with a pen, and "clarified" that the "work was complete and was now in the deployment pipeline." That wasn't the first or the last time that stupid goober's mouth almost got us in trouble.
I miss that job. It was hard to work in the stifling environment of an ossified corporate structure, but I had good friends I was working with, and despite our team being considered "black sheep" and "dangerous mavericks", everyone respected our productivity and we were always involved in all new policy decisions (basically, they were just upset to be told they were wrong). We skirted many lay-offs after that first round because of it.