Yes, i wil try with that command, thx

I said it in my post:

If i set the password with the same script in the node2, works again. But if we move again to node1, fail again.

If a have to set the password of every user of every database, everytime i move a database... this cluster is a nightmare instead of a solution

This is what i needed

https://www.sqlshack.com/synchronize-logins-between-availability-replicas-in-sql-server-always-on-availability-group/

Thanks again,

Today i installed security patchs on DC1, i have moved all roles to DC2, and we have problems again. This is the cause.

How can i move roles and restart DC1 without this problems ? DCs are server 2016, we have had server 2008 and 2012 and never had this problems.

Thanks again !

OK, this is because my .bat is called w32tm.bat and i just discovered that if the file have the same name of the command, the batch file keeps looping.

https://stackoverflow.com/questions/19047442/my-batch-file-keeps-looping-but-why

I put all the commands in a .bat to execute it in many servers.

After a while, we have problems again.

I have correct the gpo and i have forced the command in all server, what more can i check?

I have opened like admin. Yes, the path is just an example.

On my second post i wrote:

I have also tried reindex the SQL database: https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/reindex-the-wsus-database

removing sync logs, I never did it.

"The problem is not that, the console sometimes cant open because the wsusservices is using all the ram"

I can open the console when wsusservices is not crazy syncronizing...

Yes, im doing weekly the maintenance with the this script:

 [reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration")` | out-null 
 $wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer(); 
 $cleanupScope = new-object Microsoft.UpdateServices.Administration.CleanupScope; 
 $cleanupScope.DeclineSupersededUpdates = $true        
 $cleanupScope.DeclineExpiredUpdates = $true 
 $cleanupScope.CleanupObsoleteUpdates = $true 
 $cleanupScope.CompressUpdates = $true 
 #$cleanupScope.CleanupObsoleteComputers = $true 
 $cleanupScope.CleanupUnneededContentFiles = $true 
 $cleanupManager = $wsus.GetCleanupManager(); 
 $cleanupManager.PerformCleanup($cleanupScope); 

And manual maintenance of updates, approving, rejecting, computers clients etc.

The error in the log was very clear:

Info w3wp.64 ThreadEntry ThreadPoolWorkQueue.Dispatch
Warning w3wp.64 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used.

I think its a bbdd error, because im not doing any manteinance of them, its an SQL express installed in the same server.

I also have to say that I have not seen hardly any information of this error.

Thanks,
Regards,