[Casper] Feature Request: Casper JSS

[Steve Wood]

If you are concerned with end users that have admin rights changing  
the name, why not manage the Sharing pref pane with MCX prefs?  You  
should be able to manage it at a local level by using Workgroup  
Manager to import the preference in and managing it there.

You could use Composer to "watch" the system while you do it and then  
parse thru the folders in Composer to figure out exactly what plist  
file is change.  Then you should be able to push that plist to each  
machine, essentially locking down the pref pane completely.

Of course, this also means that your techs will not be able to change  
it (or any admin for that matter I think), unless that plist file is  
first deleted.  And, of course, if the end users figure out what file  
that is, they can trash it and effect a change as well.

Just a thought.


Thanks!

-
Steve Wood
Director Information Technology
swood at integerdallas.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
iPhone. 940.312.2475 | fx. 214.758.6902 | desk. 214.758.6813



On Apr 22, 2008, at 6:04 PM, Ernst, Craig S. wrote:

> Evening,
>
> It took Tom's email to trigger my memory to ask for this little  
> feature
> related to inventory. Thanks Tom!
>
> I would like the ability to 'LOCK-IN' the name of a computer after  
> it has
> been imaged, meaning that the only time you can modify what the  
> computer
> name should be in the JSS is at the time you image locally with  
> Casper or as
> an admin from the web interface. This assumes my techs name it right  
> the
> first time...=)
>
> Along with this I would like to enforce this with a management  
> option that
> anytime the machine 'checks-in', perhaps best at a recon cycle or  
> maybe even
> every time it checks the JSS, it will also perform a 'Reset Computer
> Name(s)' like you have on the advanced tab. This way if a user that  
> does
> have administrative rights on their computer changes this name, we
> automatically set it back.
>
> Right now if the machine name is different when we run a recon cycle  
> the JSS
> updates to what the local machine is named, which makes sense, but I  
> want to
> enforce it in the other direction.
>
> This essentially always forces a machine name to what we set it at  
> when we
> deploy it so we can maintain standardized naming conventions which  
> we use to
> determine Smart Group memberships for applying policies, etc.
>
> Thanks!
>
> Craig Ernst
> Systems Management & Configuration
> ----------------------------------
> University of Wisconsin-Eau Claire
> Learning & Technology Services
> 105 Garfield Ave
> Eau Claire, WI 54701
> Phone: (715) 836-3639
> Fax: (715) 836-6001
> ----------------------------------
> ernstcs at uwec.edu
>
> _______________________________________________
> Casper mailing list
> Casper at list.jamfsoftware.com
> http://list.jamfsoftware.com/mailman/listinfo/casper



--
The information contained in this email transmission is solely for the addressee(s) named above and is privileged and/or confidential.  If the reader of this message is not the intended recipient or the person responsible to deliver it to the intended recipient; he or she is prohibited from reading or disclosing the information contained in this transmission.  Any examination, use, dissemination, distribution, or copying of this communication is strictly prohibited.  Please contact us immediately by telephone for instructions if you have received this communication in error: (214) 758-6800
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20080422/c0da135a/attachment.htm