I believe using extension mobility it is possible to lock phones individually. However we are running 3.1(1) without the Extension Mobility. For call authorisation and accounting is there any way users can lock their phone to prevent other users misusing their phones.
I know of a school where a kid went around re-programming 7960s to point to phantom callmanagers. He tought it was funny...Cost the school alot of money to walk around behind him re-programming the phones..
I think you can put all the security in the world on something and someone will find a way to get around it if they want to bad enough. This conversation has been going on for years it started with whether to lock the door at you house or not. If your door is locked and someone wants in bad enough the break the window or do something else. In the work place you can try to hire the right people and hope to minimize this, but this is a different problem in a school environment.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.