Recommendations for routine baremetal restores with hardware independence
Posted on 2013-01-30
This is a slightly different sort of enquiry. I have historically supplied to customers most hardware with the OS that ships with it. I have for some time recognised that I need to be able to record the images of deployed machines and keep these as 'reset images' for DR but also for 'Standardisation'.
So I need to image every deployed machine (so no private data) and be able to restore that image (and here is the potential catch) to a replacement machine which is not necessarily the original or same brand/spec of machine.
Similarly I need to be able to create a standard workstation image for a customer and deploy that image on new machines which may vary in specification.
I'd like to also take server images for bare metal restores to replacement hardware, again not necessarily same spec. So we are looking for DR and increasing swap out abilities here.
Can anyone help me along the lines of:
1. Does the likes of Ghost etc, allow hardware independent images to be obtained and burnt and if so what are the restrictions (official and from your experiences)
2. How are licenced products managed (specifically Office and Windows)
3. Are there any papers outlining the procedures to follow and any back ground reading for someone setting this functionality up and running for their shop.
I need to get this sorted as we are spending large amounts of time recycling machines from scratch when what we really need to do is just pickout an appropriate image, burn it, finish and deploy. Is this too simplistic ????
Your thoughts very much appreciated.