F
F
Fiasco2014-04-15 10:22:33
SQL
Fiasco, 2014-04-15 10:22:33

Windows Server 2012 - How to fix WSUS error when connecting to WID?

Good day!
There was a problem adding the WSUS role on Windows Server 2012 R2, the database selected was "Windows Internal Database".
Following Google's advice, I added to the "Login as a service": NT SERVICE \ ALL SERVICES, otherwise the role is not stupidly added to the server.
Role installed successfully, post-deployment configuration required. And then there is an error with sending to the log file. Error content:

System.Data.SqlClient.SqlException (0x80131904): Login failed. The login belongs to an untrusted domain and cannot be used in Windows authentication.

The computer is a domain controller, and the user on behalf of which all this is launched is Administrator. Google is already at a loss to answer this, I ask for advice on how to be, thanks in advance.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
O
oia, 2014-04-15
@oia

it is said MS do not use wsus role on DC 2012r2
The WID base by default is called SUSDB.mdf and is stored in the windir%\wid\data\ directory. This database only supports Windows authentication (not SQL). The name of the WSUS database instance will be server_name\Microsoft##WID.
If the WSUS role and the database server are installed on different servers, there are a number of restrictions:
The WSUS database server cannot be a domain controller
The WSUS server cannot be a Remote Desktop Services terminal server at the same time

A
Ars1s, 2014-04-15
@Ars1s

Remove wsus role, download and install wsus 3.0

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question