...
If this long-standing practice were to change, it cannot be done quickly. (8 days, with almost no processing or communication, was recently presumed.) A change will force us in Chemistry to remove the client from many of our systems to better protect ... (flesh out consequences...). Making "forced" changes to computers by default, simply because they are running software to increase their visibility, is neither balanced nor necessary. This is especially true given that these are centrally provisioned tools feeding into central inventory systems, an for which we are not provided viable alternatives.
Language Oliver sent Mike and Fred Fri. 8/10/2018 re: opt-in vs opt-out (in that case, forcing name changes, by default):
To Mike's question, "It would be nice to have a solid reasoning behind why not to enforce the name change on all ARTS computers. What would be the negative effect of this policy in your area?": My continued recommended approach is to spend time working problems of the "collective" highest priority, preferably after getting reports on the current state of the systems. And offer select solutions as opt-in to those who may benefit, on their own schedule.
If such services are NOT opt-in, TSPs will all need to understand exactly what will or will not happen to our systems, now AND in the future, sometimes for a proposed solution which we may not have a need for. TSPs should not have to be made to make an effort to "defend" ourselves from default actions taken centrally. Instead, we each should be responsible to vet any proposed policy we elect to apply to my systems.
So if I may turn your question on its head: It would be nice to have a solid reasoning behind why we must enforce the name change on all ARTS computers. What would be the negative effect of making this policy available to every area?
Additional details
The two management tools used at Cornell are each focused primarily on one of two supported computer operating systems (OS):
...