What is the correct way to introduce a domain controller into an existing peer-to-peer network?

Question

System administration

Good afternoon,
How to properly implement a domain controller in an existing peer-to-peer network?

The essence of the question is not how to plan and implement it, but what difficulties you have to face when you introduce it into the DC network (before that, it was not on the network). and in particular, what about the programs and files installed on users' computers, because they will not be available and they will have to be reinstalled / reconfigured?

PS there is no experience of introducing DC, they don’t laugh much

Answer 1

what to do with programs and files installed on users' computers, because they will not be available and they will have to be reinstalled / reconfigured

Transfer the profile to the domain, there are many programs, here is an example: https://exonix.ru/%D0%A1%D1%82%D0%B0%D1%82%D1%8C%D...
There will be no problems.

Answer 2

"Introducing" is relatively simple - you raise, configure DNS and forwarding, create all users, start including computers in the domain. In order for the computer to enter the domain, it is necessary to configure its DNS client on a domain controller, otherwise it will not see the domain.
After adding a PC to the domain, local software will be available, user profiles will have to be migrated, including potential roaming profile features for domain users.

Answer 3

The main question: Why do you need a domain controller? Or are you just interested in possible problems?
Various problems may arise .... for example:
1. All kinds of "assemblies" of Windows, which may not be entered into the domain at all or may not be entered correctly.
2. Availability of local users administrator rights and various other "permissions" (NTFS, registry branches, etc.).
3. "Zoo" versions of Windows on computers
4. A hotbed of viruses on a PC
5. Who knows how the firewall is configured and whether it is configured at all.
6. Impossibility (difficulty) of applying group policies due to points 1-5...
7. Unauthorized installed software on a PC that already has all the necessary rights...
Well, and much more....
PS As for me, it's easier to make a "naked" installation of the system and deliver the user with the necessary software + return all his files to him.
And so many more options all at once and do not remember.

Answer 4

The main problem is grated rolls and flint people. They are accustomed to the only way, only on the desktop and only climb all the computers. But these percentages are usually 10, no more.
Start by migrating the main, same-type and young mass of users. You will translate the rest later, slowly, with difficulty - but without revolutions, each separately dealing with piles of ancient features (such as 10 tender sites that you work with, but passwords are lost, with ancient plug-ins for programs from 2001, with mail in The Bat, etc. difficulties). Reassure them, explain that there is no enemy among you. It is often convenient to combine this with replacing the PC with a new and faster one.
When the main backbone of the team joins the new infrastructure and realizes that it really has become better, gets used to entering network passwords, the moral support of veterans will collapse. On their problems - you will sigh - and say - you see - everyone has already passed and everything is ok there, and you cling to the old ...
Water wears away the stone. :)