How to fix the problem that a limited number of PCs are displayed in a domain on windows server 2012 in Network Neighborhood?

Question

Windows Server

Good afternoon.
There is a domain on winows server 2008r2, which includes the main office and several additional ones. We recently joined another office to the domain by installing a domain controller there on windows server 2012. Server 2012 is not an r2 version, since there is no license for it in the organization. In total, there are approximately 200 PCs in the domain. But in the newly joined to the domain office, there was a problem: When opening the network place, exactly 50 first computers in alphabetical order are displayed. Moreover, this problem occurs only if Server 2012 is assigned as the browser master. If you transfer the role to a regular PC with windows 7 pro, then the problem disappears. Google found only a proposal to upgrade to r2 and install the MS update from 08.2014. But as I mentioned above, we do not have a license for the r2 version. Maybe someone faced a similar problem and knows how to fix it on a regular server 2012? I really don't want to roll back to server 2008, since keeping the master browser on the client computer is not an option...
UPD: I want to clarify a few points. I myself am just starting to study servers, and I am raking after the previous employee. Today, everything is organized in such a way that each user has a personal exchange folder on his computer and with the help of them they exchange files. In this regard, and the need for a master browser and viewing 200 machines in a networked environment. Perhaps it really is worth moving them all to a file server, but it may not be possible to completely abandon personal folders.
Concerning several master browsers in a network. We have each office located in a separate network segment and each has a domain controller, which is the only browser master in its segment. At the same time, the main master browser of the domain is the main controller, so there are no problems with re-elections.
Actually I read that the master browsing system is outdated. But nowhere did I find how to organize everything correctly in modern operating systems.

Answer 1

Browsing is a crutch, besides, it lives its own life and is constantly buggy.
In addition, if you think about it, then it is not needed on the network at all, and it needs to be turned off. Sharing some resources on workstations is a cant of this size. All resources must be tied to servers in one way or another. The number of file servers is very limited, and access to them is decided by connecting network drives on clients or, at most, by appropriate shortcuts on the desktop. To drive parasitic traffic on the network for this and spend an engineer's time solving problems with browsing is a waste of company money.