j.schneider hat geschrieben: ↑11 Feb 2022, 17:07
Dann haben wir die Ursache gefunden.
Ohne den CredentialProvider (opsi-login-blocker) funktioniert das ganze nicht.
Hallo OPSI Team,
ich teste gerade den Upgrade von 20H2 auf 21H2 mit windows10-upgrade_21h2-2. Bei mir ist opsi-login-blocker eingeschaltet.
Von den drei möglichen "execution_method" Funktionen funktioniert nur "loginOpsiSetupUser". Bei den anderen beiden Methoden werden die Fehler gemeldet, die von dem Vorredner schon erwähnt wurden.
Bei dem nachfolgendem Logauszug aus opsi_loginblocker.log wurde die Methode "runAsOpsiSetupUser" verwendet. Hier wird ein Fehler beim Lesen eines Registry Eintrages gemeldet:
Code: Alles auswählen
[1] [2022-03-19 21:38:44.027] [] --------------------------------------------------------------------------------------------------------------
[1] [2022-03-19 21:38:44.028] [] opsi login blocker version 4.2.0.2 initializing on Windows 10 (or above) (credential provider filter)
[1] [2022-03-19 21:38:44.028] [] --------------------------------------------------------------------------------------------------------------
[5] [2022-03-19 21:38:44.028] [] Getting config from registry
[5] [2022-03-19 21:38:44.028] [] log level is: 5
[3] [2022-03-19 21:38:44.028] [] Failed to query registry key 80000002, subKey SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Provider Filters\{d2028e19-82fe-44c6-ad64-51497c97a02a}, valueName LoginBlockerLogDir: 234
[3] [2022-03-19 21:38:44.037] [] Failed to get LoginBlockerLogDir value from registry, using default
[5] [2022-03-19 21:38:44.038] [] OpsiCredentialProviderFilter is enabled
[5] [2022-03-19 21:38:44.038] [] OpsiCredentialProvider is enabled
[5] [2022-03-19 21:38:44.039] [] LoginBlockerTimeoutConnect is 120 seconds
[1] [2022-03-19 21:38:44.040] [] opsi login blocker version 4.2.0.2 initialized on Windows 10 (or above)
[5] [2022-03-19 21:38:44.040] [] opsi com started
[5] [2022-03-19 21:38:44.041] [] Waiting for opsiclientd service to start
[5] [2022-03-19 21:38:44.042] [] Service opsiclientd is running (SERVICE_RUNNING)
[5] [2022-03-19 21:38:44.042] [] Connected to opsiclientd pipe
[5] [2022-03-19 21:38:44.042] [] Sending request: '{"id": 1, "method": "registerClient", "params": ["opsi-login-blocker","4.2.0.2"]}'
[5] [2022-03-19 21:38:44.050] [] Opsi credential provider filter init
[5] [2022-03-19 21:38:44.565] [] Received response: '{"id": 1, "result": "client opsi-login-blocker/4.2.0.2/#1 registered", "error": null}'
[5] [2022-03-19 21:38:45.096] [] Received request: '{"id": 1, "method": "blockLogin", "params": [false]}'
[5] [2022-03-19 21:38:45.096] [] Sending response: '{"id": 1, "result": "not blocking login", "error": null}'
[5] [2022-03-19 21:38:46.081] [] Filtering providers blockLogin=false, loginTriggered=false, rebootTriggered=false, shutdownTriggered=false
[5] [2022-03-19 21:38:46.105] [] Opsi credential provider init
[5] [2022-03-19 21:38:46.113] [] Hiding our tile (setting pdwCount to 0)
VG,
Martin