Hello All,
Hopefully Lance is watching again...
So you see a theme here with my subject, granularity.
I spent some time today troubleshooting why a system wasn't binding after
imaging. After looking through the logs it appears it never attempted to
bind. I then asked them which configuration they were using to image, and
they were apparently using the Standard Configuration, rather than the Smart
Configurations based upon that Standard Configuration. The Smart
configurations have the different AD bindings in them.
The point here is that I would like to somehow limit the view of a person to
only be allowed to use particular configurations. This would allow me to say
this group of Office people can only see these few Offices Configurations,
this group of Lab people can only see these few Labs Configurations, and
this lonely tech in this college on gets this configuration.
This would have helped my particular situation today, they could have used
only 1 of 2 configurations, and are thus less likely to screw up.
An alternative to this would be in Casper Admin hiding configurations from
Casper Imaging. I could hide my Standard Configurations.
I think it's very important to be as granular as possible because it allows
me better control to prevent people from making mistakes, or accessing
things they shouldn't, which then wastes more of my time when they do. It
allows me to make the system even more idiot-proof, accept for the guy who's
running it. That would be me. =)
Any takers?
And then on a side note since I can't seem to find it anywhere. Can a line
be put into the jamf.log at imaging time that states what configuration was
used when it was imaged?
Thanks for your time today. That is all.
Craig E
