Does it make sense to start a domain controller in this case?

Question

Active Directory

Before the introduction of the domain controller, there was doubt whether it was worth using it. Doubts are as follows:
1. The enterprise has less than 50 workstations.
2. Only one person sits at each workstation. Those. Ivanov sits at the IVANOV-WS computer , Petrov sits at the PETROV-WS computer, and so on. 3. The company has a maximum of 3 computers, at which different people sit, because they work in shifts. They work so far under the same local computer account. Does it make much sense to start a domain controller under such conditions?

Answer 1

The domain is used not only for users to log in to their computers, but also for
1. Convenient sharing of resources - network drives, network printers
2. Convenient centralized configuration of all computers on the network (updating, installation through policies)
3. In case of change computer - it is more convenient in the domain. The user simply sits down at a new computer, and if his profiles are made via the network, then even his desktop and documents will be loaded. But for this, users need to be disciplined so that they store all personal data on the network.
And other.

Answer 2

There is

Answer 3

50 cars is already a lot. If you need to massively change something, then you will trample your feet and erase your fingers. And through domain policies, everything will be much more convenient. Well, the hair will be soft and silky. :)

Answer 4

A domain is a tool for conveniently managing multiple users and computers.
If you have 1-4 computers and you need to install the same software on them, or make some settings, it's not a problem to bypass them all and do it.
If you have 10 computers, this can also be done, but it is already quite long and tedious. Already there are thoughts to drive everything into the domain.
If you have 30-300 computers - you are tormented to bypass everything. There is no domain here.
And how many users there are working at the computer - it doesn't matter at all.

Answer 5

AD - is not only a valuable fur passwords in one place, but also:
- group policies. This is really powerful stuff!
- quiet installation
- roaming profiles and their backup
- convenience for the admin
- a lot of money for licenses :)

Answer 6

There is an administrator's computer. We make a guest share on it with read access. We put a script in the autoload of computers, which looks at a certain script in this ball. If it is, we launch it. The script does everything it needs to. Do you need several different groups of computers? We make several different scripts in startup for different computers that run different scripts from the admin computer. To get around the restrictions on the number of connections to the admin's computer, we put Debian for the admin instead of Mastday. If the office is not completely poor, then instead of the admin's computer we put a stand-alone server with network drives, backups - yes, with anything. If many people alternately work from one computer, we create many accounts on it, in which we store user records.
Remote profiles in Mastday work pretty well only in the case of small amounts of information stored by the user.