Unfortunately this isn't one of those success stores. But then again if I wrote about those I'd be hitting a few thousand posts a year, and plus they're really boring to write about. We began the project by powering up some virtual machines and test importing the configuration from ISA 2006 to Forefront TMG 2010, and all appeared fine. The ruleset was there, the VPN configurations were there, and so on.
A little less than a month ago Patrick from Red-Track online marketingcontacted me and wanted to know if I'd be interested in reviewing a TrainSignaltraining DVD, specifically one about Exchange 2010. If you want the final word on the quality of the training head straight to the final paragraph, otherwise strap in; This is a long post. I'll have to be honest, I had never heard of TrainSignal until that point, and I was wondering if it was a bit of a scam.
Following up to yesterday's post on LXC: Linux Containers, I had a quick play with 2 ULAsubnets (aka RFC4193 addresses - dont forget that site-local was depreciated) - one subnet was dedicated to the LXC containers, one for my normal LAN. Perhaps unsurprisingly IPv6 appears to work perfectly well in this setup. I also altered the setup and bridged a container directly to eth0 on the host node, and watched the container assign itself a stateless address based on my prefix, and again everything appeared to work perfectly well out onto the public v6 network (courtesy of Hurricane Electric's Tunnel Brokerservice).
I've been toying with migrating my server into a containerized system, and almost bought a new server in preparation to migrate everything across. I'd chosen and tested my solution, OpenVz. All was good with the world. Until I saw that OpenVz was effectively being dropped from Ubuntu 10.04 (Lucid Lynx) and most likely Debian 6.0 (Squeeze). The reason for the drop is simply because the OpenVz patches haven't been forward ported into the current kernel.
Mark Baggett over at PauldotComput together an interesting article on running a command on every machine in your domain from the command line. I genuinely hadn't considered tying dsquery and wmi together in this way. The best thing is that with a little tweaking you can easily run the same command against a subset of your domain. For instance, say you had X terminal/web/sql servers that all lived in the same OU - just dsquery against that and you're laughing.