In my opinion, this is a BAD idea.
We have different snapins for different OSs and we have to manage many types of images at any given time. We have a list a of snapins a mile long - many of which cannot / should not run on some images. Someday, Access Control will be implemented inside FOG, but until then, we manage FOG use on an honor system. Some people have the task to decide what snapins go on what machines, while others have the job of deploying snapins.
FOG’s ability to image and then apply snapins is a good feature, but in my life, we’re normally deploying snapins more frequently on an as-needed basis to repair an existing snapin install or to send software to a PC that didn’t need it until sometime long after imaging. We’re also always making new snapins for maintenance and to meet the users’ needs and these are always deployed one at a time. In point of fact, we create images that have the majority of the snapins already installed (like MS Office) to save on the deployment time.
In my opinion, allowing single snapin delivery of any snapin will lead to a lot more extra work in the form of re-imaging to undo mistakes being made.
I strongly suggest that you consider returning this feature to how it’s been. The inconvenience of having to select a snapin for a PC prior to deploying that snapin actually saves time we’ll have to spend due to mistakes and acts as a safeguard against time-consuming mistakes.
Jim