I'm off work today, sick.  Many thanks to the knob at the desk across the hallway from me who came to work sick and spent the whole day yesterday coughing and sneezing into the communal air.  Did I say thank you?  Actually, no, I meant FUCK YOU.  You turd.

Since I am at home, and have time to myself, I thought I'd do a bit of experimentation with Veeam, a backup product for virtualised environments.  Of course, this meant resurrecting my VMware study lab, which I am ashamed to say, has sat idle for the last.. ohhh… at least six months.  Give or take another six months.  In the process of setting up Veeam, I figured I'd try to reproduce the VM environment at work.  This involves configuring a NAS device and using it as a backup target.  Hmm.  i have a VM called "FreeNAS".  Funnily enough, it runs FreeNAS.  A NAS.  That's free.  I set about configuring Active Directory integration on the device and it was playing silly-buggers, so I figure OK, what the hell.. I'll just create a new one.  I downloaded the latest version of FreeNAS, quickly configured it and configured the AD integration.  Or so I thought.  It refused to work, giving me a vague "service couldn't start" message.  Super-helpful.  So I googled, and discovered this cautionary tale, which in turn pointed to this cautionary tale.

You can guess what happened to my domain controller VM, right?  Shame on the FreeNAS GUI designers who didn't think that "hostname" could be interpreted to mean "hostname of the DC" instead of "hostname of the freenas box".  So, with my AD hosed, and not enough care factor to try to fix it, I'm recreating my AD environment too.  Bugger.