"Up-ping" the uptime of your Lite-Touch server
Daniel Oxley: I like the lite-touch installation (LTI) feature of MDT, it think it's great and is very impressive as it allows clients to easily see the benefit that they will gain by using MDT to create and deploy their images. I can go on-site with a customer to demo the product and have a basic MDT server configured to deploy Windows Vista and Office 2007 (both with the most basic of configurations) over the network in their laboratory, all in one day. Admittedly, the setup won't do much else because it lacks all the details but, as a demo, it works well. However, one thing that LTI does not offer is 'high-availability'; something that Systems Center Configuration Manager excels at.In one of my previous posts I wrote about using DNS to create 'distribution points'-like behaviour in LTI scenarios. That post got quite a bit of feedback, so with this post I want to 'steal' another Configuration Manager feature so that it can be applied to a LTI scenario, namely, making your MDT server highly available. With this post you will be able to improve the reliability of your deployments by ensuring that your single point of failure (your MDT server) is always available, simply by clustering your MDT distribution share. As before, I once again recommend Systems Center Configuration Manager as the product of choice if you need a highly-available platform for installing your images as it really is the best option available; the content offered in this post could never replace the functionality offered by Systems Center Configuration Manager.(continue at source)








