[ryse]

larkost – Thank you for your in depth response! 💡

I am pleased to be a apart of the instaDMG community. You and your team have truly done a great job.

I took your advice and looked over InstaUp2Date -> This looks like a really nice add on. The theory of having a catalog file for different imaging scenarios, with nesting capabilities makes a lot of sense. That same theory is exactly what we are working towards, although we are going to store these packages out on a server (software repository). This repository will be broken up into different categories and based on the machine name it will determine which software packages to provision into the vanilla image after it is laid down. This leads me to my question… Is there a particular reason why both instaup2date and instaDMG are including the packages inside of the outputted ASR Image VS storing them out on a server? In a large deployment scenario with multiple sites it would be quite the task to build out and maintain different images based on all of the different software requirements for a large organization. It would be easier to build and maintain these catalog file’s in a central spot. Just a thought..

Thanks again for answering my previous questions…

[Author]

Posts