Sprache wählen:
  WSUS.DE › Windows Server Update Services › Troubleshooting › Neuer Rechner erscheint nicht in der Console
‹ Vorheriges Thema | Nächstes Thema ›
Seitenindex umschalten Seiten: 1 Thema versendenDrucken
Normales Thema Neuer Rechner erscheint nicht in der Console (Gelesen: 2205 mal)
Ali@s
WSUS Junior Member
*
Offline


I love WSUS

Beiträge: 30
Standort: 37412 Herzberg am Harz
Mitglied seit: 10.01.06
Geschlecht: männlich
Neuer Rechner erscheint nicht in der Console
01.07.08 um 11:07:20
Beitrag drucken  
Hallo und guten Morgen,
ich wollte letzte Woche unserer Domäne einen neuen Rechner hinzufügen und hab dort auch (wie bei allen anderen Rechnern) die autom. Updates via WSUS eingerichtet. Komischerweise erscheint dieser Rechner aber nicht in der Console.

Auf dem Client liegen im Windows-Verzeichnis auch 2 Logfiles. Einmal eine WindowsUpdate.log und einmal eine Windows Update.log.

Im WindowsUpdate-Log erscheint folgendes:

Quote:
2008-06-27      09:36:24+0200      1096      dd4      Service Main starts
2008-06-27      09:36:24+0200      1096      dd4      Using BatchFlushAge = 33567.
2008-06-27      09:36:24+0200      1096      dd4      Using SamplingValue = 558.
2008-06-27      09:36:24+0200      1096      dd4      Successfully loaded event namespace dictionary.
2008-06-27      09:36:24+0200      1096      dd4      Successfully loaded client event namespace descriptor.
2008-06-27      09:36:24+0200      1096      dd4      Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2008-06-27      09:36:24+0200      1096      dd4      Successfully initialized NT event logger.
2008-06-27      09:36:24+0200      1096      dd4      Successfully initialized event uploader 0.
2008-06-27      09:36:24+0200      1096      dd4      Successfully initialized event uploader 1.
2008-06-27      09:36:24+0200      1096      dd4      WU client with version 5.4.3790.5512 successfully initialized
2008-06-27      09:36:24+0200      1096      dd4      Service status is now SERVICE_RUNNING
2008-06-27      09:37:09+0200      1096      dd4      start delayed initialization of WU client
2008-06-27      09:37:09+0200      2748      a88      Trying to make out of proc datastore active
2008-06-27      09:37:09+0200      2748      a88      Out of proc datastore is now active
2008-06-27      09:37:09+0200      1096      dd4      Client Call Recorder finished delayed initialization
2008-06-27      09:37:09+0200      1096      dd4      Setting next AU detection timeout to 2008-06-27 07:37:09
2008-06-27      09:37:09+0200      1096      dd4      Launching Legacy AU client
2008-06-27      09:42:09+0200      2748      a88      Out of proc datastore is shutting down
2008-06-27      09:42:10+0200      1328      6f8      WUCheckForUpdatesAtShutdown failed, hr=8024002B
2008-06-27      09:42:11+0200      2748      a88      Out of proc datastore is now inactive
2008-06-27      09:42:14+0200      1096      44c      Service received logoff notification
2008-06-27      09:42:14+0200      1096      44c      Forwarding control handler info to legacy AU
2008-06-27      09:42:18+0200       704      bc8      WUAutoUpdateAtShutdown failed, hr=8024002B
2008-06-27      09:42:23+0200      1096      44c      Service received SERVICE_CONTROL_SHUTDOWN control
2008-06-27      09:42:23+0200      1096      dd4      Exiting Service Main
2008-06-27      09:42:23+0200      1096      dd4      WUAUENG ServiceMain exits. Exit code is 0x240001
2008-06-27      09:43:03+0200      1096      7dc      Service Main starts
2008-06-27      09:43:03+0200      1096      7dc      Using BatchFlushAge = 33567.
2008-06-27      09:43:03+0200      1096      7dc      Using SamplingValue = 558.
2008-06-27      09:43:03+0200      1096      7dc      Successfully loaded event namespace dictionary.
2008-06-27      09:43:03+0200      1096      7dc      Successfully loaded client event namespace descriptor.
2008-06-27      09:43:03+0200      1096      7dc      Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2008-06-27      09:43:03+0200      1096      7dc      Successfully initialized NT event logger.
2008-06-27      09:43:03+0200      1096      7dc      Successfully initialized event uploader 0.
2008-06-27      09:43:03+0200      1096      7dc      Successfully initialized event uploader 1.
2008-06-27      09:43:03+0200      1096      7dc      WU client with version 5.4.3790.5512 successfully initialized
2008-06-27      09:43:03+0200      1096      7dc      Service status is now SERVICE_RUNNING
2008-06-27      09:43:40+0200      1096      44c      Service received logon notification
2008-06-27      09:43:42+0200      1096      44c      Service received connect notification
2008-06-27      09:43:48+0200      1096      7dc      start delayed initialization of WU client
2008-06-27      09:43:49+0200      2068      818      Trying to make out of proc datastore active
2008-06-27      09:43:51+0200      2068      818      Out of proc datastore is now active
2008-06-27      09:43:51+0200      1096      7dc      Client Call Recorder finished delayed initialization
2008-06-27      09:43:51+0200      1096      7dc      Setting next AU detection timeout to 2008-06-27 07:43:51
2008-06-27      09:43:51+0200      1096      7dc      Launching Legacy AU client
2008-06-27      09:48:52+0200      2068      818      Out of proc datastore is shutting down
2008-06-27      09:48:53+0200      2068      818      Out of proc datastore is now inactive
2008-06-27      10:03:19+0200      1096      44c      Service received SERVICE_CONTROL_STOP control
2008-06-27      10:03:19+0200      1096      7dc      Exiting Service Main
2008-06-27      10:03:19+0200      1096      7dc      WUAUENG ServiceMain exits. Exit code is 0x240001
2008-06-27      10:03:19+0200      1096      f5c      Service Main starts
2008-06-27      10:03:19+0200      1096      f5c      Using BatchFlushAge = 33567.
2008-06-27      10:03:19+0200      1096      f5c      Using SamplingValue = 558.
2008-06-27      10:03:19+0200      1096      f5c      Successfully loaded event namespace dictionary.
2008-06-27      10:03:19+0200      1096      f5c      Successfully loaded client event namespace descriptor.
2008-06-27      10:03:19+0200      1096      f5c      Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2008-06-27      10:03:19+0200      1096      f5c      Successfully initialized NT event logger.
2008-06-27      10:03:19+0200      1096      f5c      Successfully initialized event uploader 0.
2008-06-27      10:03:19+0200      1096      f5c      Successfully initialized event uploader 1.
2008-06-27      10:03:19+0200      1096      f5c      WU client with version 5.4.3790.5512 successfully initialized
2008-06-27      10:03:19+0200      1096      f5c      Service status is now SERVICE_RUNNING
2008-06-27      10:03:19+0200      1708      f28      Trying to make out of proc datastore active
2008-06-27      10:03:20+0200      1708      f28      Out of proc datastore is now active
2008-06-27      10:03:20+0200      1096      e68      Client Call Recorder finished delayed initialization
2008-06-27      10:03:20+0200      1096      e68      Setting next AU detection timeout to 2008-06-27 08:03:20
2008-06-27      10:03:20+0200      1096      e68      Launching Legacy AU client
2008-06-27      10:04:04+0200      1096      f5c      start delayed initialization of WU client
2008-06-27      10:08:20+0200      1708      f28      Out of proc datastore is shutting down
2008-06-27      10:08:21+0200      1708      f28      Out of proc datastore is now inactive
2008-06-27      10:47:50+0200       752       f4      WUCheckForUpdatesAtShutdown failed, hr=8024002B
2008-06-27      10:47:54+0200      1096      44c      Service received logoff notification
2008-06-27      10:47:54+0200      1096      44c      Forwarding control handler info to legacy AU
2008-06-27      10:47:58+0200       704      bd0      WUAutoUpdateAtShutdown failed, hr=8024002B
2008-06-27      10:48:01+0200      1096      44c      Service received SERVICE_CONTROL_SHUTDOWN control
2008-06-27      10:48:01+0200      1096      f5c      Exiting Service Main
2008-06-27      10:48:01+0200      1096      f5c      WUAUENG ServiceMain exits. Exit code is 0x240001
2008-07-01      10:00:47+0200      1096      7b4      Service Main starts
2008-07-01      10:00:47+0200      1096      7b4      Using BatchFlushAge = 33567.
2008-07-01      10:00:47+0200      1096      7b4      Using SamplingValue = 558.
2008-07-01      10:00:47+0200      1096      7b4      Successfully loaded event namespace dictionary.
2008-07-01      10:00:48+0200      1096      7b4      Successfully loaded client event namespace descriptor.
2008-07-01      10:00:48+0200      1096      7b4      Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2008-07-01      10:00:48+0200      1096      7b4      Successfully initialized NT event logger.
2008-07-01      10:00:48+0200      1096      7b4      Successfully initialized event uploader 0.
2008-07-01      10:00:48+0200      1096      7b4      Successfully initialized event uploader 1.
2008-07-01      10:00:48+0200      1096      7b4      WU client with version 5.4.3790.5512 successfully initialized
2008-07-01      10:00:48+0200      1096      7b4      Service status is now SERVICE_RUNNING
2008-07-01      10:00:54+0200      1096      44c      Service received logon notification
2008-07-01      10:00:54+0200      1096      44c      Service received connect notification
2008-07-01      10:01:33+0200      1096      7b4      start delayed initialization of WU client
2008-07-01      10:01:33+0200      1780      6ec      Trying to make out of proc datastore active
2008-07-01      10:01:34+0200      1780      6ec      Out of proc datastore is now active
2008-07-01      10:01:34+0200      1096      7b4      Client Call Recorder finished delayed initialization
2008-07-01      10:01:34+0200      1096      7b4      Setting next AU detection timeout to 2008-07-01 08:01:34
2008-07-01      10:01:34+0200      1096      7b4      Launching Legacy AU client
2008-07-01      10:06:36+0200      1780      6ec      Out of proc datastore is shutting down
2008-07-01      10:06:37+0200      1780      6ec      Out of proc datastore is now inactive


Im Windows Update-Log steht Folgendes:

Quote:
2008-07-01 10:07:28  08:07:28   Success   IUENGINE       Starting
2008-07-01 10:07:28  08:07:28   Success   IUENGINE       Determining machine configuration
2008-07-01 10:07:29  08:07:29   Error     IUENGINE       Querying software update catalog from (Du musst Dich Einloggen oder Registrieren um Multimediadateien oder Links zu sehen). (Error 0x80190193)
2008-07-01 10:07:29  08:07:29   Success   IUENGINE       Shutting down


Kann mir da jemand einen Tip geben, wo ich da schauen sollte?

Vielen Dank im voraus.

Frank
  
Zum Seitenanfang
 
IP gespeichert
Permalink für diesen Artikel  
Karotte84
WSUS Junior Member
*
Offline


I Love WSUS!

Beiträge: 43
Mitglied seit: 26.05.08
Re: Neuer Rechner erscheint nicht in der Console
Antwort #1 - 01.07.08 um 11:21:11
Beitrag drucken  
Gefunden in einem anderen Forum als Lösung zu Fehler 0x80190193:


"I found that on my "WSUS Administration" Web Site in IIS, the "Require secure channel (SSL)" box under Directory Security -> Secure Communications -> Edit was checked. The client was trying to access the Selfupdate directory but it was being denied by the server. Try the URL (Du musst Dich Einloggen oder Registrieren um Multimediadateien oder Links zu sehen). (if you're using port 8530) in the Web browser of the client and see if it downloads or gives you an error.

Und dann noch in der Eingabeaufforderung: wuauclt.exe /resetauthorization /detectnow

Jetzt sollte es klappen."

Versuch ist es wert, denke ich mal.
  
Zum Seitenanfang
 
IP gespeichert
Permalink für diesen Artikel  
Sunny
Microsoft MVP
*****
Offline



Beiträge: 15188
Mitglied seit: 11.02.07
Geschlecht: männlich
Re: Neuer Rechner erscheint nicht in der Console
Antwort #2 - 01.07.08 um 11:28:55
Beitrag drucken  
Hier gibts Abhilfe: (Du musst Dich Einloggen oder Registrieren um Multimediadateien oder Links zu sehen).
Lösch doch mal alles in der Registry unterhalb dieses Schlüssels: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

Jetzt ein GPUPDATE /FORCE ausführen und evtl. auch den Client neu starten.
  
Zum Seitenanfang
 
IP gespeichert
Permalink für diesen Artikel  
Sunny
Microsoft MVP
*****
Offline



Beiträge: 15188
Mitglied seit: 11.02.07
Geschlecht: männlich
Re: Neuer Rechner erscheint nicht in der Console
Antwort #3 - 01.07.08 um 11:30:07
Beitrag drucken  
Karotte84 schrieb on 01.07.08 um 11:21:11:
Gefunden in einem anderen Forum als Lösung zu Fehler 0x80190193:

"I found that on my "WSUS Administration" Web Site in IIS, the "Require secure channel (SSL)" box under Directory Security -> Secure Communications -> Edit was checked. The client was trying to access the Selfupdate directory but it was being denied by the server. Try the URL (Du musst Dich Einloggen oder Registrieren um Multimediadateien oder Links zu sehen). (if you're using port 8530) in the Web browser of the client and see if it downloads or gives you an error.


Wenn es das wäre, hätte jeder Client ein Problem. Das ist aber beim OP nicht der Fall.
  
Zum Seitenanfang
 
IP gespeichert
Permalink für diesen Artikel  
Ali@s
WSUS Junior Member
*
Offline


I love WSUS

Beiträge: 30
Standort: 37412 Herzberg am Harz
Mitglied seit: 10.01.06
Geschlecht: männlich
Re: Neuer Rechner erscheint nicht in der Console
Antwort #4 - 01.07.08 um 11:31:52
Beitrag drucken  
Quote:
"I found that on my "WSUS Administration" Web Site in IIS, the "Require secure channel (SSL)" box under Directory Security -> Secure Communications -> Edit was checked. The client was trying to access the Selfupdate directory but it was being denied by the server. Try the URL (Du musst Dich Einloggen oder Registrieren um Multimediadateien oder Links zu sehen). (if you're using port 8530) in the Web browser of the client and see if it downloads or gives you an error.


Da hab ich auch schon geschaut. Der Haken ist dort nicht gesetzt. Sonst würde auch die anderen 100 Clients, denke ich mal, nix ziehen.

Danke dir trotzdem.

Frank
  
Zum Seitenanfang
 
IP gespeichert
Permalink für diesen Artikel  
Ali@s
WSUS Junior Member
*
Offline


I love WSUS

Beiträge: 30
Standort: 37412 Herzberg am Harz
Mitglied seit: 10.01.06
Geschlecht: männlich
Re: Neuer Rechner erscheint nicht in der Console
Antwort #5 - 01.07.08 um 11:48:29
Beitrag drucken  
Sunny, vielen Dank  Kuss

Das hat geholfen...
  
Zum Seitenanfang
 
IP gespeichert
Permalink für diesen Artikel  
Sunny
Microsoft MVP
*****
Offline



Beiträge: 15188
Mitglied seit: 11.02.07
Geschlecht: männlich
Re: Neuer Rechner erscheint nicht in der Console
Antwort #6 - 01.07.08 um 12:00:25
Beitrag drucken  
Ali@s schrieb on 01.07.08 um 11:48:29:
Sunny, vielen Dank  Kuss

Das hat geholfen...


Freut mich und Danke für die Rückmeldung. Zwinkernd
  
Zum Seitenanfang
 
IP gespeichert
Permalink für diesen Artikel  
Seitenindex umschalten Seiten: 1
Thema versendenDrucken
‹ Vorheriges Thema | Nächstes Thema ›
Bookmarks: Facebook Google Google+ Linked in Twitter Yahoo
 
  « Übersicht ‹ Forum oben  



Nutzungsbedingungen | Datenschutz
Kontakt | RSS | Feedback | Impressum
Facebook | News einsenden


WSUS.DE » Powered by YaBB 2.6.11!
YaBB Forum Software © 2000-2025. Alle Rechte vorbehalten.

Valid RSS Valid XHTML Valid CSS Powered by Perl Source Forge