Hab gestern noch beide Updates abgelehnt und danach das neue wieder genehmigt. Dann hab ich den WSUS über Nacht laufen lassen. Angeblich hat er dabei aber einen hohen Traffic im unternehmensnetz erzeugt lt. Admin (bei 1 Update und nur Definitionen?)
Im Taskmanager gestern nachmittag und heut morgen war aber nix (Netzlast nahe 0).
Das SoftwareDistribution.log zeigt jedoch fast durchgehend Einträge die mir noch nicht wirklich was sagen (vereinzelt mit Download). Gibts da nen guten Link?
Aber trotz allem Traffic --> Das betreffende Update steht auf 0%.
Zum Haareraufen!
Edit:
Mal die Logeinträge, die sich in der Art und Weise wiederholen:
Quote:2009-10-05 21:25:25.060 UTC Info w3wp.7 DataAccessCache.DeploymentChange Finished refreshing the syncUpdates cache. New SyncUpdatesHelper: 24323505
2009-10-05 21:29:50.622 UTC Info WsusService.13 ContentSyncAgent.ProcessBITSNotificationQueue ContentSyncAgent recieved Transferred Event for Item: 52a12978-38a4-4520-b855-b59454abb878
2009-10-05 21:29:50.624 UTC Info WsusService.13 ContentSyncAgent.ContentSyncSPFireStateMachineEvent ContentSyncAgent firing Event: FileDownloaded for Item: 52a12978-38a4-4520-b855-b59454abb878
2009-10-05 21:29:51.788 UTC Info WsusService.13 ContentSyncAgent.ContentSyncSPFireStateMachineEvent ContentSyncAgent firing Event: FileVerified for Item: 52a12978-38a4-4520-b855-b59454abb878
2009-10-05 21:29:51.805 UTC Info WsusService.13 EventLogEventReporter.ReportEvent EventId=366,Type=Information,Category=Synchronization,Message=Inhaltsdatei wurde heruntergeladen. Digest: Quelldatei: /msdownload/update/software/uprl/2009/03/wyukon2005setup-kb955706-x64-enu_bf0852
8b2b6ea829aed8296a9202b566e9cc4829.exe Zieldatei: c:\WSUS\WsusContent\29\BF08528B2B6EA829AED8296A9202B566E9CC4829.exe.
2009-10-05 21:29:51.826 UTC Info WsusService.13 ContentSyncAgent.WakeUpWorkerThreadProc ContentSyncAgent found no more Jobs, thread exitting
2009-10-05 21:29:51.900 UTC Info WsusService.13 EventLogEventReporter.ReportEvent EventId=363,Type=Information,Category=Synchronization,Message=Inhaltsynchronisie
rung war erfolgreich.
2009-10-05 21:29:51.941 UTC Info WsusService.13 ContentSyncAgent.WakeUpWorkerThreadProc ServerHealth: Updating Server Health for Component: ContentSyncAgent, Marking as Not Running
2009-10-05 21:29:52.099 UTC Info w3wp.108 DependencyCache.RefreshThreadStart read 13128 UpdateIDs from DB in 78 ms
2009-10-05 21:29:52.339 UTC Info w3wp.10 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2009-10-05 21:29:52.340 UTC Info w3wp.115 ThreadEntry ThreadHelper.ThreadStart
2009-10-05 21:29:52.341 UTC Info w3wp.115 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
2009-10-05 21:29:52.342 UTC Info w3wp.115 DeploymentChangeNotification.InternalEventHandler deployment change event received
2009-10-05 21:29:52.344 UTC Info w3wp.115 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
2009-10-05 21:29:55.054 UTC Info w3wp.27 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2009-10-05 21:29:55.056 UTC Info w3wp.110 ThreadEntry ThreadHelper.ThreadStart
2009-10-05 21:29:55.057 UTC Info w3wp.110 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
2009-10-05 21:29:55.059 UTC Info w3wp.110 ChangeNotificationDispatcher.InternalEventHandler Get event DeploymentChange from dispatchmanager
2009-10-05 21:29:55.067 UTC Info w3wp.15 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2009-10-05 21:29:55.067 UTC Info w3wp.23 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2009-10-05 21:29:56.648 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2009-10-05 21:30:22.341 UTC Info w3wp.6 ServerImplementation.UpdateCache Database change occured; check if we need to update cache.
2009-10-05 21:30:22.344 UTC Info w3wp.6 RevisionIdCache.UpdateCategoryAndRevisionIdCache Fetching the category and revision id change for cache from database
2009-10-05 21:30:22.357 UTC Info w3wp.6 RevisionIdCache.UpdateCategoryCache Refreshing the category cache
2009-10-05 21:30:22.359 UTC Info w3wp.6 RevisionIdCache.UpdateRevisionCache Refreshing the revision cache
2009-10-05 21:30:25.090 UTC Info w3wp.6 DataAccessCache.DeploymentChange Refreshing the syncUpdates cache
2009-10-05 21:30:25.286 UTC Info w3wp.6 DataAccessCache.DeploymentChange LastCacheRefreshTime: 193 milliseconds
2009-10-05 21:30:25.287 UTC Info w3wp.6 DataAccessCache.DeploymentChange Finished refreshing the syncUpdates cache. New SyncUpdatesHelper: 13934249
2009-10-05 21:34:52.402 UTC Info w3wp.38 DependencyCache.RefreshThreadStart read 13128 UpdateIDs from DB in 79 ms
Das sieht fast so aus als ob der manches doch herunterlädt.