Illogical behavior of the WSUS server? or logical?

Question

Windows Server

Good afternoon!
Colleagues, there is a problem, or rather a misunderstanding of the incorrect operation of WSUS servers.
Situation:
One WSUS server - server_1 (win srv 2012 r2) was installed , it was registered in the domain with politicians, they (politicians) scattered computers into groups. Everything worked great.
After some time, it was decided to raise the second WSUS server - server_2 (win srv 2012 r2 ). And make it Downstream (slave) in relation to the server server_1. No sooner said than done.
Synchronization is configured - everything is OK. PCs were divided into two groups, some should take updates from server_1 , others from server_2. Accordingly, two policies have been created:
for the PC and server server_1 and for the PC and server server_2 .
It is quite logical that PCs that used to take updates from server_1 , when they are transferred to the second group and the new policy is applied, should receive updates from server_2 .
But.... The PCs that were moved to the second group are displayed in the consoles of both servers and server_1 and server_2 . And the status of Last Report and Last Contact is different for them.
i.e .:
server_1 Upstream (master)
PC_1 Last Report = 02.12.2019 13:22 | Last Contact = 02.12.2019 13:14
server_2 Downstream (slave)
PC_1 Last Report = 02.12.2019 13:57 | Last Contact = 12/02/2019 13:54
And so on for all PCs that were transferred from one group to another. I tried to delete these server_1 PCs , but after a while they appear there again.
Is this behavior normal?
I read this Microsoft's manual , but it did not add understanding ...

Answer 1

Is it specified in the settings of the second server that it is a replica of the first one?
If yes - the behavior is normal - all permissions to install must be on the first server and, accordingly, the second server is simply obliged to report the names of the computers to the first.