Hi,
There will be problems with the scripts because they run with the rights of the
administrator who created them.
All affected scripts must be updated by the existing administrator. (ex. add
description or comment line).
Efim
> 5 окт. 2018 г., в 18:49, Solomon Miler написал(а):
>
> User_X
Solomon
While it is never an acceptable best practice, users do sometimes use an
individual account to automate tasks. It's possible that external tasks, jobs,
scripts, etc. have been configured to use that account to authenticate with the
server(s). However, anything created like schedules and
User_X created various entities on tsm (schedules, associations, scripts etc ).
User_X leaves the company,
User_X needs to be removed from tsm. (remove admin User_X)
Is there a concern / any side-effects you can think of.
Thank you.
Solomon Miler
Senior Data Protection Engineer, VP