Question Locked

Writing procedures on managing a server OS/clients

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are a small company, we do not have a formal IT department but I'm "the guy" (without the pay).

We are wanting to get more PCs in for the production floor and "go paperless". I am wanting to get a domain controller to manage all the computers (except management PCs in the front offices, they are exempt and allowed to run amok with administrator privileges).

My direct manager is a Quality Manager, well-versed in ISO 9001 and helping us get certified for ISO 9001, and is huge on documentation.

Apparently I will in essence be required to write "Work Procedures" on mainly how to configure the server, such as adding users, editing group policies, and managing the server in general. The idea so that anyone can easily be trained from scratch and take my spot at a moment's notice.

I get documenting devices/locations, IP addresses, schemes, and other configurations and assets, but is being required or is it a normal practice to teach/write documentation for a potential new guy from scratch to be a system or network administrator without much prior knowledge?

I know it sounds like a weird question, I am pretty sure normal companies require at least a degree in information systems and certifications and are expected to come in already having that knowledge (or something like an intern who is currently studying said subject matter).

1 reply

by kees_b edited

It makes sense to document how you do things and when you do it. Not only for your successor, but for yourself also. In case of doubt about the level of detail needed, just discuss it with your manager.

I think an ISO 9001 certification for IT is an overkill for non-IT companies. Do you mind if your garage is certified for IT? Probably not. But you prefert them to be certified for car tech, wouldn't you.

This discussion is closed to new replies.