none
Problema WSUS: Clientes no ven parches RRS feed

  • Pregunta

  • Estimados

    Escribo para que me puedan coloborar con el problema que tengo en el WSUS 3.0 SP2 (IIS: Port=80) en ingles bajo Win 2003 Standard Edition SP2 en ingles x86 en Grupo de Trabajo... el WSUS que tengo descarga los parches de Microsoft sin problemas, sin embargo los clientes (granja 150 servers) no descargan los parches que se tienen para desplegar del WSUS, se ejecuto wuauclt.exe /detectnow en clientes, luego (http://www.crog.es/?p=281):
    net stop wuauserv
    REG DELETE “HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update” /v LastWaitTimeout /f
    REG DELETE “HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update” /v DetectionStartTime /f
    Reg Delete “HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update” /v NextDetectionTime /f
    net start wuauserv
    wuauclt /detectnow
    Y nada, luego se reiniciaron los servicios del WSUS y de actualizacion de los clientes, del IIS del WSUS, BITS del WSUS, y nada
    se bajo e instalo el agente de WSUS para clientes y nada, se borro la carpeta repository de WBEM en system32 que por ahy un foro lo indicaba y nada, por ay se puede hacer como se menciona en: http://www.cabai.com.ar/2008/05/cmo-forzar-la-deteccin-de-un-cliente-de-wsus.html pero no lo he aplicado.
    Por ultimo decidi reinstalar el WSUS (borre todo) y no funciono, reinstalar el Report Viewer 2008 con el WSUS y no funciono....
    Restaure un system state de un mes pasado y nada
    La verdad que no se que mas hacer... lo ultimo pensado es que algun registro en regedit o archivo de sistema este ocasionando ello.... y tocaria reinstalar sistema operativo.... que es lo ultimo que quiero hacer...
    Si alguien puede hecharme una mano para solucionar el problema.... se lo agradeceria eternamente

    Gracias

    jueves, 15 de octubre de 2009 17:33

Respuestas

  • Como te comentaba anteriormente, aparentemente del lado cliente no hay ningún problema, así que habría que ver del lado servidor...

    Te preguntaba particularmente si en la consola de WSUS las diferentes actualizaciones están ya aprobadas para su instalación. Los equipos cliente ya aparecen en la consola?

    Saludos!
    jueves, 15 de octubre de 2009 19:46
  • Hola,

    Para que los clientes puedan encontrar y descargar los updates, tenés que aprobarlos en la consola. Una vez que los apruebes, recién ahí el servidor WSUS los descarga del sitio de Windows Update para ponerlos a disposición de los clientes.

    Cualquier otra duda, comentanos.

    Saludos!
    jueves, 15 de octubre de 2009 20:48
  • Tené en cuenta que una vez aprobadas las actualizaciones se realiza la descarga de las mismas desde el sitio de Microsoft Update, lo cual puede tomar un tiempo considerable según la cantidad de updates (podés ver el estado de la descarga en la pantalla principal de la consola de WSUS).

    Una vez que haya finalizado la descarga, recién ahí los clientes podrán comenzar a descargar las actualizaciones desde el servidor WSUS.

    Lo que hace el comando wuauclt /detectnow es forzar la búsqueda de actualizaciones desde el cliente.

    Saludos!
    jueves, 15 de octubre de 2009 23:22
  • Hola,

    Ojo que las sincronizaciones no son en realidad las descargas. La sincronización lo que hace es buscar todas las actualizaciones disponibles en el sitio de Microsoft Update, para luego mostrártelas en el listado dentro de la consola. Las descargas las realiza una vez que dichas actualizaciones son aprobadas, de lo contrario la descarga no se realiza (esto es lógicamente para no ocupar espacio en disco innecesariamente).

    Cómo tenés organizado el tema de los grupos de equipos dentro del WSUS? Están todos dentro de "Equipos sin asignar" o tenés grupos definidos?

    Saludos!
    viernes, 16 de octubre de 2009 13:57

Todas las respuestas

  • P.D. Log de Cliente:

    2009-10-15 12:05:30:328 820 e10 AU #############
    2009-10-15 12:05:30:328 820 e10 AU ## START ##  AU: Search for updates
    2009-10-15 12:05:30:328 820 e10 AU #########
    2009-10-15 12:05:30:328 820 e10 AU <<## SUBMITTED ## AU: Search for updates [CallId = {859F6121-C6C8-40E9-938E-BEBA4B5B20D1}]
    2009-10-15 12:05:30:328 820 8e4 Agent *************
    2009-10-15 12:05:30:328 820 8e4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-15 12:05:30:328 820 8e4 Agent *********
    2009-10-15 12:05:30:328 820 8e4 Agent  * Online = Yes; Ignore download priority = No
    2009-10-15 12:05:30:328 820 8e4 Agent  * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
    2009-10-15 12:05:30:328 820 8e4 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2009-10-15 12:05:30:328 820 8e4 Agent  * Search Scope = {Machine}
    2009-10-15 12:05:30:328 820 8e4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2009-10-15 12:05:30:328 820 8e4 Misc Microsoft signed: Yes
    2009-10-15 12:05:30:328 820 8e4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2009-10-15 12:05:30:328 820 8e4 Misc Microsoft signed: Yes
    2009-10-15 12:05:30:328 820 8e4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2009-10-15 12:05:30:343 820 8e4 Misc Microsoft signed: Yes
    2009-10-15 12:05:30:343 820 8e4 Setup ***********  Setup: Checking whether self-update is required  ***********
    2009-10-15 12:05:30:343 820 8e4 Setup  * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-10-15 12:05:30:343 820 8e4 Setup  * IsUpdateRequired = No
    2009-10-15 12:05:30:468 820 8e4 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2009-10-15 12:05:30:468 820 8e4 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.12.241/ClientWebService/client.asmx
    2009-10-15 12:05:30:859 820 8e4 Agent  * Found 0 updates and 49 categories in search; evaluated appl. rules of 138 out of 261 deployed entities
    2009-10-15 12:05:30:859 820 8e4 Agent *********
    2009-10-15 12:05:30:859 820 8e4 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-15 12:05:30:859 820 8e4 Agent *************
    2009-10-15 12:05:30:859 820 b18 AU >>##  RESUMED  ## AU: Search for updates [CallId = {859F6121-C6C8-40E9-938E-BEBA4B5B20D1}]
    2009-10-15 12:05:30:859 820 b18 AU  # 0 updates detected
    2009-10-15 12:05:30:859 820 b18 AU #########
    2009-10-15 12:05:30:859 820 b18 AU ##  END  ##  AU: Search for updates [CallId = {859F6121-C6C8-40E9-938E-BEBA4B5B20D1}]
    2009-10-15 12:05:30:859 820 b18 AU #############
    2009-10-15 12:05:30:859 820 b18 AU Featured notifications is disabled.
    2009-10-15 12:05:30:859 820 b18 AU AU setting next detection timeout to 2009-10-16 12:58:37
    2009-10-15 12:05:32:765 820 8e4 Report REPORT EVENT: {2B188040-F581-40BC-BF7A-605C6F229ECC} 2009-10-15 12:05:27:765-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2009-10-15 12:05:32:765 820 8e4 Report REPORT EVENT: {24FBEB2B-A593-4B47-8AED-963A7D2D9774} 2009-10-15 12:05:27:765-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2009-10-15 12:05:32:765 820 8e4 Report REPORT EVENT: {7BCE6071-35E5-4132-B492-95949A4B63C6} 2009-10-15 12:05:29:375-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2009-10-15 12:05:32:765 820 8e4 Report REPORT EVENT: {E5D803C6-0C0C-48BA-B184-DEECBFB077BF} 2009-10-15 12:05:29:375-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2009-10-15 12:05:32:765 820 8e4 Report REPORT EVENT: {01A4AFB3-759A-4CB4-B34B-FD63984AA82B} 2009-10-15 12:05:30:109-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2009-10-15 12:05:32:765 820 8e4 Report REPORT EVENT: {5E7D58CD-9CAF-4EF9-B65B-5D4B2006D34B} 2009-10-15 12:05:30:109-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2009-10-15 12:05:32:765 820 8e4 Report REPORT EVENT: {AC9C04B7-3E13-487A-AED8-F076A66397F1} 2009-10-15 12:05:30:859-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2009-10-15 12:05:32:765 820 8e4 Report REPORT EVENT: {234CCD67-1376-42E0-BE35-1A504EA95785} 2009-10-15 12:05:30:859-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2009-10-15 12:06:50:828 820 8e4 Report Uploading 10 events using cached cookie, reporting URL = http://192.168.12.241/ReportingWebService/ReportingWebService.asmx
    2009-10-15 12:06:51:421 820 8e4 Report Reporter successfully uploaded 10 events.
    jueves, 15 de octubre de 2009 17:35
  • P.D. Log de WSUS

    2009-10-15 17:35:01.078 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:03.000 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:03.140 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:03.140 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:03.140 UTC Info w3wp.407 ThreadEntry ThreadHelper.ThreadStart
    2009-10-15 17:35:03.140 UTC Info w3wp.407 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:03.140 UTC Info w3wp.407 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:03.328 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:03.328 UTC Info w3wp.405 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:03.328 UTC Info w3wp.405 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:03.328 UTC Info w3wp.405 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:04.515 UTC Info WsusService.23 CatalogSyncAgentCore.ImportMultipleUpdates Imported 100/100 updates in 1 iterations; 0 will be retried
    2009-10-15 17:35:04.515 UTC Info WsusService.23 CatalogSyncAgentCore.GetUpdateDataInChunksAndImport 927 updates to go
    2009-10-15 17:35:06.093 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:08.046 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:08.156 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:08.156 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:08.156 UTC Info w3wp.403 ThreadEntry ThreadHelper.ThreadStart
    2009-10-15 17:35:08.156 UTC Info w3wp.403 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:08.156 UTC Info w3wp.403 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:08.343 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:08.343 UTC Info w3wp.401 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:08.343 UTC Info w3wp.401 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:08.343 UTC Info w3wp.401 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:11.187 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:11.984 UTC Info WsusService.23 CatalogSyncAgentCore.ImportMultipleUpdates Imported 100/100 updates in 1 iterations; 0 will be retried
    2009-10-15 17:35:11.984 UTC Info WsusService.23 CatalogSyncAgentCore.GetUpdateDataInChunksAndImport 827 updates to go
    2009-10-15 17:35:13.062 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:13.156 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:13.156 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:13.156 UTC Info w3wp.399 ThreadEntry ThreadHelper.ThreadStart
    2009-10-15 17:35:13.156 UTC Info w3wp.399 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:13.156 UTC Info w3wp.399 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:13.343 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:13.343 UTC Info w3wp.397 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:13.343 UTC Info w3wp.397 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:13.343 UTC Info w3wp.397 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:16.296 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:18.109 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:18.171 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:18.171 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:18.171 UTC Info w3wp.394 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:18.171 UTC Info w3wp.394 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:18.359 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:18.359 UTC Info w3wp.393 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:18.359 UTC Info w3wp.393 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:18.359 UTC Info w3wp.393 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:19.640 UTC Info WsusService.23 CatalogSyncAgentCore.ImportMultipleUpdates Imported 100/100 updates in 1 iterations; 0 will be retried
    2009-10-15 17:35:19.640 UTC Info WsusService.23 CatalogSyncAgentCore.GetUpdateDataInChunksAndImport 727 updates to go
    2009-10-15 17:35:21.343 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:23.109 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:23.218 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:23.218 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:23.218 UTC Info w3wp.391 ThreadEntry ThreadHelper.ThreadStart
    2009-10-15 17:35:23.218 UTC Info w3wp.391 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:23.218 UTC Info w3wp.391 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:23.453 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:23.453 UTC Info w3wp.389 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:23.453 UTC Info w3wp.389 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:23.453 UTC Info w3wp.389 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:26.375 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:27.031 UTC Info WsusService.23 CatalogSyncAgentCore.ImportMultipleUpdates Imported 100/100 updates in 1 iterations; 0 will be retried
    2009-10-15 17:35:27.031 UTC Info WsusService.23 CatalogSyncAgentCore.GetUpdateDataInChunksAndImport 627 updates to go
    2009-10-15 17:35:28.140 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:28.250 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:28.250 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:28.250 UTC Info w3wp.387 ThreadEntry ThreadHelper.ThreadStart
    2009-10-15 17:35:28.250 UTC Info w3wp.387 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:28.250 UTC Info w3wp.387 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:28.500 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:28.500 UTC Info w3wp.385 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:28.500 UTC Info w3wp.385 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:28.500 UTC Info w3wp.385 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:31.421 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:33.171 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:33.265 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:33.265 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:33.265 UTC Info w3wp.382 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:33.265 UTC Info w3wp.382 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:33.515 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:33.515 UTC Info w3wp.381 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:33.515 UTC Info w3wp.381 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:33.515 UTC Info w3wp.381 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:35.578 UTC Info WsusService.23 CatalogSyncAgentCore.ImportMultipleUpdates Imported 100/100 updates in 1 iterations; 0 will be retried
    2009-10-15 17:35:35.578 UTC Info WsusService.23 CatalogSyncAgentCore.GetUpdateDataInChunksAndImport 527 updates to go
    2009-10-15 17:35:36.437 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:38.187 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:38.265 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:38.265 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:38.265 UTC Info w3wp.378 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:38.265 UTC Info w3wp.378 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:38.515 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:38.515 UTC Info w3wp.377 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:38.515 UTC Info w3wp.377 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:38.515 UTC Info w3wp.377 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:41.468 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:43.218 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:43.265 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:43.265 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:43.265 UTC Info w3wp.375 ThreadEntry ThreadHelper.ThreadStart
    2009-10-15 17:35:43.281 UTC Info w3wp.375 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:43.281 UTC Info w3wp.375 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:43.531 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:43.531 UTC Info w3wp.373 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:43.531 UTC Info w3wp.373 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:43.531 UTC Info w3wp.373 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:46.500 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:48.234 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:48.281 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:48.281 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:48.281 UTC Info w3wp.370 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:48.281 UTC Info w3wp.370 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:48.531 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:48.531 UTC Info w3wp.369 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:48.531 UTC Info w3wp.369 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:48.531 UTC Info w3wp.369 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:48.875 UTC Info WsusService.23 CatalogSyncAgentCore.ImportMultipleUpdates Imported 100/100 updates in 1 iterations; 0 will be retried
    2009-10-15 17:35:48.875 UTC Info WsusService.23 CatalogSyncAgentCore.GetUpdateDataInChunksAndImport 427 updates to go
    2009-10-15 17:35:51.531 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:53.281 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:53.296 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:53.296 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:53.296 UTC Info w3wp.366 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:53.296 UTC Info w3wp.366 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:53.531 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:53.531 UTC Info w3wp.365 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:53.531 UTC Info w3wp.365 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:53.531 UTC Info w3wp.365 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:54.859 UTC Info WsusService.23 CatalogSyncAgentCore.ImportMultipleUpdates Imported 100/100 updates in 1 iterations; 0 will be retried
    2009-10-15 17:35:54.859 UTC Info WsusService.23 CatalogSyncAgentCore.GetUpdateDataInChunksAndImport 327 updates to go
    2009-10-15 17:35:56.593 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:58.500 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:58.500 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:58.500 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:58.500 UTC Info w3wp.362 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:58.500 UTC Info w3wp.362 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:35:58.578 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:35:58.578 UTC Info w3wp.361 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:35:58.578 UTC Info w3wp.361 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:35:58.578 UTC Info w3wp.361 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:36:01.703 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:36:03.531 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:36:03.531 UTC Info w3wp.13 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:36:03.531 UTC Info w3wp.11 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:36:03.531 UTC Info w3wp.358 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:36:03.531 UTC Info w3wp.358 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:36:03.843 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-10-15 17:36:03.843 UTC Info w3wp.357 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2009-10-15 17:36:03.843 UTC Info w3wp.357 DeploymentChangeNotification.InternalEventHandler deployment change event received
    2009-10-15 17:36:03.843 UTC Info w3wp.357 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
    2009-10-15 17:36:05.796 UTC Warning WsusService.23 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used.
    2009-10-15 17:36:05.843 UTC Warning WsusService.23 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used.
    2009-10-15 17:36:06.734 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange

    jueves, 15 de octubre de 2009 17:38
  • Hola,

    El log del cliente no muestra ningún error en particular, así que al menos desde ese lado todo parece estar bien. Ejecutaste la herramienta de diagnóstico en el equipo cliente? --> http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE

    Y aunque pueda resultar una pregunta algo tonta... los updates están aprobados para instalación en los grupos correspondientes?

    Comentanos luego cómo te fue.

    Saludos!
    jueves, 15 de octubre de 2009 17:53
  • Hola

    Gracias por responder el tool para cliente lo ejecute y no mostro nada raro: 
    WSUS Client Diagnostics Tool

    Checking Machine State
            Checking for admin rights to run tool . . . . . . . . . PASS
            Automatic Updates Service is running. . . . . . . . . . PASS
            Background Intelligent Transfer Service is running. . . PASS
            Wuaueng.dll version 7.4.7600.226. . . . . . . . . . . . PASS
                    This version is WSUS 2.0

    Checking AU Settings
            AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
                    Option is from Control Panel

    Checking Proxy Configuration
            Checking for winhttp local machine Proxy settings . . . PASS
                    Winhttp local machine access type
                            <Direct Connection>
                    Winhttp local machine Proxy. . . . . . . . . .  NONE
                    Winhttp local machine ProxyBypass. . . . . . .  NONE
            Checking User IE Proxy settings . . . . . . . . . . . . PASS
                    User IE Proxy. . . . . . . . . . . . . . . . .  NONE
                    User IE ProxyByPass. . . . . . . . . . . . . .  NONE
                    User IE AutoConfig URL Proxy . . . . . . . . .  NONE
                    User IE AutoDetect
                    AutoDetect not in use

    Checking Connection to WSUS/SUS Server
                    WUServer = http://192.168.12.241
                    WUStatusServer = http://192.168.12.241
            UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
            Connection to server. . . . . . . . . . . . . . . . . . PASS
            SelfUpdate folder is present. . . . . . . . . . . . . . PASS

    Me olvidaba aplique el tool de debug y aplique las opciones y no tuve suerte.
    En los clientes estan habilitados en algunos casos para que notifique - luego descargue y descargue para instalacion
    Tambien me baje los servicios del Mcafee

    Saludos
    jueves, 15 de octubre de 2009 17:59
  • Como te comentaba anteriormente, aparentemente del lado cliente no hay ningún problema, así que habría que ver del lado servidor...

    Te preguntaba particularmente si en la consola de WSUS las diferentes actualizaciones están ya aprobadas para su instalación. Los equipos cliente ya aparecen en la consola?

    Saludos!
    jueves, 15 de octubre de 2009 19:46
  • Hola

    Los clientes siempre han aparecido en la consola indicando el estado y el porcentaje, y los parches se muestan: 6 install y el resto como not approved, el despliegue de parches se realizaba no desde la consola si no desde los mismos servidores.
    Confirmame tengo que aprobar para que esten activos y se puedan ver o es ya para instalarlos en los servers

    Saludos.
    jueves, 15 de octubre de 2009 19:54
  • Hola,

    Para que los clientes puedan encontrar y descargar los updates, tenés que aprobarlos en la consola. Una vez que los apruebes, recién ahí el servidor WSUS los descarga del sitio de Windows Update para ponerlos a disposición de los clientes.

    Cualquier otra duda, comentanos.

    Saludos!
    jueves, 15 de octubre de 2009 20:48
  • Gracias

    lo que hice es aprobar todos los parches... toca esperar, por consulta que proceso se genera cuando se de wuauclt.exe /detectnow

    Garcias
    jueves, 15 de octubre de 2009 21:46
  • Hola

    aún sigo esperando  y nada de las descargar a los clientes.
    alguna sugerencia

    Saludos.
    jueves, 15 de octubre de 2009 22:53
  • Tené en cuenta que una vez aprobadas las actualizaciones se realiza la descarga de las mismas desde el sitio de Microsoft Update, lo cual puede tomar un tiempo considerable según la cantidad de updates (podés ver el estado de la descarga en la pantalla principal de la consola de WSUS).

    Una vez que haya finalizado la descarga, recién ahí los clientes podrán comenzar a descargar las actualizaciones desde el servidor WSUS.

    Lo que hace el comando wuauclt /detectnow es forzar la búsqueda de actualizaciones desde el cliente.

    Saludos!
    jueves, 15 de octubre de 2009 23:22
  • Hola pablitoms

    las sincronizaciones con windows update muestra que ya culminaron, sin embargo antes del problema la carpeta de WSUS pesaba aprox 25 GB. actualmente solo 3GB. por lo que no se en que estado esta.
    jueves, 15 de octubre de 2009 23:26
  • Hola,

    Ojo que las sincronizaciones no son en realidad las descargas. La sincronización lo que hace es buscar todas las actualizaciones disponibles en el sitio de Microsoft Update, para luego mostrártelas en el listado dentro de la consola. Las descargas las realiza una vez que dichas actualizaciones son aprobadas, de lo contrario la descarga no se realiza (esto es lógicamente para no ocupar espacio en disco innecesariamente).

    Cómo tenés organizado el tema de los grupos de equipos dentro del WSUS? Están todos dentro de "Equipos sin asignar" o tenés grupos definidos?

    Saludos!
    viernes, 16 de octubre de 2009 13:57
  • Hola pablitoms

    Gracias por tus aportes... creo que fui de lo mas complejo a lo mas basico... ya descargan los parches una vez aprobados... se probo y funciona sin problemas... antes de los problemas los clientes los tenia distribuidos en grupos... ahora toca volverlos a agrupar... una vez mas gracias.

    Saludos.

    P.D. Doy por cerrado el caso.
    domingo, 18 de octubre de 2009 12:21
  • Me alegro que ya esté solucionado. Saludos!!
    martes, 20 de octubre de 2009 1:32