Protected Images & Hosts / Groups
Nice to see protection on the images. Could we see it on the hosts/groups as well?
don’t get me wrong. we know how to script installs / use GPO.
just some items are just not worth the work at the moment.
only items like Sage or bspoke applications we use.
Wayne Workman last edited by Wayne Workman
@ITCC If you have specialized hosts, you can build a specialized image just for them… this image should have all the settings that host needs. Plus, if you have Active Directory at your disposal, then a lot of “post-config” can be handled by AD. I can’t remember the last time I had to install a network printer manually… or install some obscure piece of software. All that stuff is either installed or linked to via GPOs. Everything from custom config files, map drives, management software, power settings, yada yada, anything you can think of can be done with AD GPOs.
And, personally, I re-do all settings for a group when I use a group. I also re-do all settings for a host when I image a host.
I do three things, I set the correct image, I set the AD settings I want, and I set the service settings I want… then I’ll start whatever task. I do this every single time. Be it a group or individual host… this isn’t necessary, but I’m an anal person and I want to make very sure that the host(s) I’m doing something with have the settings I want them to use at that particular moment in time.
It would be nice to protect the upload host against changes. so if someone creates a group they don’t alter these machines.
Another protection idea (maybe for FOG 2.0) when you deploy to some machines it would be nice if you could some how verify a high profile machine. So if it needs extra work or you have to remember to bake some config from it 1st then you have to acknowledge you know this is required. Currently we set these machines to not boot from PXE so we have to do it manual, forcing you to think about it.
I feel “protected” things should be dealing with files, not with individual objects. Objects on the GUI are nothing more than definitions of things. Protecting a definition, I feel, is not necessary. The reasoning for protecting Snapins and Images is because those are files that could potentially be damaging if they were uploaded over or lost.
Wayne Workman last edited by
@ITCC I don’t feel like protecting groups and hosts is really important… What is your reasoning?