Deployment via Image

Hey jd,

I can think of a number of reasons why that could cause some problems. The first being is that you would have to build the image, patch OS/software etc., then take it off network before installing Idf so that it does not register with the console and get the endpointID. Or you could script the deletion of the endpointID from the registry as part of the imaging process.

Assuming you had the process worked out for that, once you image a box it would have to be kept off network while it was renamed so you dont have an issue of a console full of the same endpoint names with the guids appended.

Another point would be that what do you do every time Idf releases a new version? Go back to your gold master and update the image and then redeploy that to all your machines on the network? Idf has a pretty aggressive update schedule from our experience. For example we license and started testing version 4.1.3.2 for Windows and 2.1.1 for Mac in January of 2010. A scant 16 months later we are up to 4.7.0.5/3.7.0.5, Win/Mac respectively, with v5 on the way in the next few months (presumably, I do not know of any firm release dates).

Not to mention after each major point release there inevitably are several minor point releases containing other improvements, unforeseen bugs not found in testing, etc. Kind of a headache with an image, if you ask me.

Personally I think you would be better off if you have any type of infrastructure for deploying via SCCM, group policy, BigFix, Apple Remote Desktop or whatever your shop uses/has access to.

I hope that helps you out some.