And if you were going to say that the link provided was for the WID only...
You cannot run the SQL Server service under a local non-system account or by using SQL Server authentication. WSUS supports Windows authentication only.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi , I have a standalone WSUS server in a workgroup - I've attempted to migrate the WID database to a standard SQL server but am having connection issues.
One of the steps on the migration document ( https://learn.microsoft.com/en-us/windows-server/administration/windows-server-update-services/manage/wid-to-sql-migration#detach-susdb-from-the-windows-internal-database ) is to add the server name and domain as a security login [FQDN][WSUSComputerName]$ however the WSUS server is not on a domain but rather a workgroup and I can't add this entry in.
Without this i am seeing the error below when connecting to the SQL server from the WSUS server process and the WSUS console doesn't load.
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Could not find a login matching the name provided. [CLIENT:CLIENTIP )
Am I missing a permission here ?
Answer accepted by question author
And if you were going to say that the link provided was for the WID only...
You cannot run the SQL Server service under a local non-system account or by using SQL Server authentication. WSUS supports Windows authentication only.
Thank you the links are at least helpful to understand the official stance. A similar post while old here https://blog.vittoriopavesi.com/2006/02/wsus-with-sql-authentication.html?m=1 again references the same keys. I will mark your answer correct though.
Read Lawrence's response.
Security implications for the very least.
No it is not.
WSUS in Workgroup mode, CANNOT use a dedicated Remote SQL Server and must use the WID. You can use a LOCAL SQL Server though.
The reason: WSUS only supports Windows Authentication. Windows Authentication can't happen across workgroup nodes.