Get-WSUSServer Authorization Error
Hallo Leute,
ich habe einen WSUS Server welcher nicht AD gejoint ist eingerichtet. Wenn ich nun von einem System welches im gleichen Netz liegt in der Powershell den Befehl absetze :
erhalte ich diesen Fehler:
Get-WsusServer : The request failed with HTTP status 401: Unauthorized
Könnt ihr mir sagen was das Problem verursacht????
UAC ist aus
FW ist aus
PING funktioniert
ich habe einen WSUS Server welcher nicht AD gejoint ist eingerichtet. Wenn ich nun von einem System welches im gleichen Netz liegt in der Powershell den Befehl absetze :
Get-WsusServer -Name WSUS.DOMAIN.COM -PortNumber 8530
erhalte ich diesen Fehler:
Get-WsusServer : The request failed with HTTP status 401: Unauthorized
Könnt ihr mir sagen was das Problem verursacht????
UAC ist aus
FW ist aus
PING funktioniert
Bitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 307483
Url: https://administrator.de/forum/get-wsusserver-authorization-error-307483.html
Ausgedruckt am: 26.12.2024 um 15:12 Uhr
9 Kommentare
Neuester Kommentar
Hi.
Sorry, my german writing isn't as good as my understanding so i'm writing in English.
You have to authorize yourself to the WSUS Server, because the server you are trying to access isn't in your domain you have to provide credentials wich have enough rights on the WSUS with the cmdlet by using the -Credentials Attribute, or by storing the credentials in your wallet for the target system. Otherwise the powershell console uses the credentials of the current user, which has no rights on the WSUS!
So, this is absolutely normal behavior, if you do not authorize yourself to the remote system, correctly.
Regards
Sorry, my german writing isn't as good as my understanding so i'm writing in English.
You have to authorize yourself to the WSUS Server, because the server you are trying to access isn't in your domain you have to provide credentials wich have enough rights on the WSUS with the cmdlet by using the -Credentials Attribute, or by storing the credentials in your wallet for the target system. Otherwise the powershell console uses the credentials of the current user, which has no rights on the WSUS!
So, this is absolutely normal behavior, if you do not authorize yourself to the remote system, correctly.
Regards
If you are running a server outside a domain an want to access it via Powershell you have to configure WSMAN and the Trusted Hosts which the Server trusts, otherwise you won't be able to connect.
See
https://4sysops.com/archives/enable-powershell-remoting-on-a-standalone- ...
See
https://4sysops.com/archives/enable-powershell-remoting-on-a-standalone- ...
Zitat von @winlin:
Ok i will checkout wsman...i think that i should cremte a certificate too and store IT on that machine from Where i want To connect right????
That's not required... only if you want to use an https listener.Ok i will checkout wsman...i think that i should cremte a certificate too and store IT on that machine from Where i want To connect right????
https://blogs.technet.microsoft.com/heyscriptingguy/2013/11/29/remoting- ...
p.s. your question mark key is damaged ...
I dont see you are defining the credentials object?
I suppose you totally forgott to configure the WSUS Server for Remoting!!
You should have also read the links inside the above site. You need to understand the concept before you do anything else ....
Also you should set the following registry entry on the WSUS Server to get around UAC issues if you are using UAC on the WSUS Server
https://www.windowspro.de/tipp/uac-filter-fuer-windows-fernwartung-absch ...
I suppose you totally forgott to configure the WSUS Server for Remoting!!
You should have also read the links inside the above site. You need to understand the concept before you do anything else ....
Also you should set the following registry entry on the WSUS Server to get around UAC issues if you are using UAC on the WSUS Server
https://www.windowspro.de/tipp/uac-filter-fuer-windows-fernwartung-absch ...