this post was submitted on 17 Jun 2023
12 points (100.0% liked)
Sysadmin
5613 readers
1 users here now
A community dedicated to the profession of IT Systems Administration
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One thing that worked for me in a similar situation was to enforce an "owner" tag or some kind of registry on everything.
Basically, if you set something up, change some configuration, whatever - put your email address on it.
Write a readme.md or wiki or guide too, but at the very minimum put your name down as the owner so that when someone comes along and wants to know if it's safe to change/upgrade/delete, they can find you and ask. If someone leaves, you can do a quick search and get them to handover/write up anything they were responsible for.
This will be important as the company gets larger - don't put your personal (or anyone's) email address on it. Put a department DL or Teams Group email on it, unless you alone want to be the only supporter and owner of whatever it is until you leave the company.
This is already a huge problem for me. A lot of accounts have the names of former IT admins that left 5 years ago and no one has bothered to update contact info with some of our suppliers. We are getting better at it now but I'm still finding more accounts that no one seems to know we have.