Предыдущая тема :: Следующая тема |
Автор |
Сообщение |
ibicus
Зарегистрирован: 21.06.2006 Сообщения: 4
|
Добавлено: Пт Июн 23 2006 16:02 Заголовок сообщения: WSUS Не обнаруживаются компьютеры. |
|
|
После установки WSUS административной консолью WSUS не видятся компьютеры домена.
Групповя политика для них определена.
Как жить дальше. |
|
Вернуться к началу |
|
![](templates/subSilver/images/spacer.gif) |
ANDronis
Зарегистрирован: 16.02.2005 Сообщения: 158
|
Добавлено: Пн Июн 26 2006 07:20 Заголовок сообщения: Re: WSUS Не обнаруживаются компьютеры. |
|
|
ibicus писал(а): | После установки WSUS административной консолью WSUS не видятся компьютеры домена.
Групповя политика для них определена.
Как жить дальше. |
клиенты пытаются подключиться к wsus? интересует наличие ошибок в файле WindowsUpdate.log |
|
Вернуться к началу |
|
![](templates/subSilver/images/spacer.gif) |
ibicus
Зарегистрирован: 21.06.2006 Сообщения: 4
|
Добавлено: Вт Июн 27 2006 16:52 Заголовок сообщения: Re: WSUS Не обнаруживаются компьютеры. |
|
|
клиенты пытаются подключиться к wsus? интересует наличие ошибок в файле WindowsUpdate.log[/quote]
2006-06-23 15:16:16+0400 264 4f4 CreateService for wuauserv succeeded
2006-06-23 15:34:34+0400 840 540 Service Main starts
2006-06-23 15:34:34+0400 840 540 Using BatchFlushAge = 19868.
2006-06-23 15:34:34+0400 840 540 Using SamplingValue = 675.
2006-06-23 15:34:34+0400 840 540 Successfully loaded event namespace dictionary.
2006-06-23 15:34:34+0400 840 540 Successfully loaded client event namespace descriptor.
2006-06-23 15:34:34+0400 840 540 Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2006-06-23 15:34:34+0400 840 540 Successfully initialized NT event logger.
2006-06-23 15:34:34+0400 840 540 Successfully initialized event uploader 0.
2006-06-23 15:34:34+0400 840 540 Successfully initialized event uploader 1.
2006-06-23 15:34:37+0400 840 540 WU client with version 5.4.3790.2180 successfully initialized
2006-06-23 15:34:37+0400 840 540 Service status is now SERVICE_RUNNING
2006-06-23 15:35:22+0400 840 540 start delayed initialization of WU client
2006-06-23 15:35:22+0400 1736 6cc Trying to make out of proc datastore active
2006-06-23 15:35:25+0400 1736 6cc Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 added
2006-06-23 15:35:25+0400 1736 6cc Service 9482F4B4-E343-43B6-B170-9A65BC822C77 added
2006-06-23 15:35:25+0400 1736 6cc Data store successfully created
2006-06-23 15:35:25+0400 1736 6cc Out of proc datastore is now active
2006-06-23 15:35:25+0400 840 540 Client Call Recorder finished delayed initialization
2006-06-23 15:35:25+0400 840 540 AU is not configured yet, generating timeout to launch setup wizard
2006-06-23 15:35:25+0400 840 540 AU finished delayed initialization
2006-06-23 15:37:51+0400 840 540 AU received event of 3
2006-06-23 15:40:24+0400 1736 6cc Out of proc datastore is shutting down
2006-06-23 15:40:25+0400 1736 6cc Out of proc datastore is now inactive
2006-06-23 15:45:03+0400 840 34c Service received connect notification
2006-06-23 15:45:03+0400 840 540 AU received event of 3
2006-06-23 15:45:19+0400 840 34c Service received logon notification
2006-06-23 15:45:19+0400 840 540 AU received event of 3
2006-06-23 16:50:34+0400 840 490 Setting AU Approval Type to 4
2006-06-23 16:50:35+0400 840 490 Setting Install Schedule Day to 0
2006-06-23 16:50:35+0400 840 490 Setting Install Schedule Time to 16
2006-06-23 16:50:35+0400 840 490 AU Options changed through user preference.
2006-06-23 16:50:35+0400 840 490 AU Restart required....
2006-06-23 16:50:35+0400 840 540 AU received event of 1
2006-06-23 16:50:35+0400 840 540 Setting next AU detection timeout to 2006-06-23 12:50:35
2006-06-23 16:50:36+0400 1500 5a8 Trying to make out of proc datastore active
2006-06-23 16:50:37+0400 1500 5a8 Out of proc datastore is now active
2006-06-23 16:50:37+0400 840 540 Setting AU scheduled install time to 2006-06-24 12:00:00
2006-06-23 16:50:37+0400 840 540 AU received event of 1
2006-06-23 16:50:37+0400 840 540 WU client succeeds CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id {6EFAF1AB-F605-477A-BD66-D72C6DD2A58E}
2006-06-23 16:50:37+0400 840 5ac WU client executing call {6EFAF1AB-F605-477A-BD66-D72C6DD2A58E} of type Search Call
2006-06-23 16:50:37+0400 840 5ac Checking for different Redirector at: http://download.windowsupdate.com/msdownload/update/v5/redir/wuredir.cab
2006-06-23 16:50:40+0400 840 490 Setting AU Approval Type to 4
2006-06-23 16:50:40+0400 840 490 Setting Install Schedule Day to 0
2006-06-23 16:50:40+0400 840 490 Setting Install Schedule Time to 16
2006-06-23 16:50:40+0400 840 490 AU Options changed through user preference.
2006-06-23 16:50:40+0400 840 490 AU settings changed through User Preference.
2006-06-23 16:50:40+0400 840 490 Setting AU scheduled install time to 2006-06-24 12:00:00
2006-06-23 16:50:41+0400 840 5ac Successfully refreshed Redirector cab.
2006-06-23 16:50:45+0400 840 5ac Loading inf file C:\WINDOWS\SoftwareDistribution\SelfUpdate\wusetup.inf
2006-06-23 16:50:45+0400 840 5ac Section name: cdm: Index: 0
2006-06-23 16:50:45+0400 840 5ac Section name: iuengine: Index: 1
2006-06-23 16:50:45+0400 840 5ac Section name: wuapi: Index: 2
2006-06-23 16:50:45+0400 840 5ac Section name: wuauclt: Index: 3
2006-06-23 16:50:45+0400 840 5ac Section name: wuauclt1: Index: 4
2006-06-23 16:50:45+0400 840 5ac Section name: wuaucpl: Index: 5
2006-06-23 16:50:45+0400 840 5ac Section name: wuaueng_SelfUpdate: Index: 6 |
|
Вернуться к началу |
|
![](templates/subSilver/images/spacer.gif) |
ANDronis
Зарегистрирован: 16.02.2005 Сообщения: 158
|
Добавлено: Ср Июн 28 2006 07:47 Заголовок сообщения: |
|
|
здается мне это логфайл сервера wsus, а интересует лог клиентской машины. Желательно свежий - для этого у клиента:
- стопим сервис Automatic Updates,
- в %systemroot% удаляем файл WindowsUpdate.log,
- в реестре удаляем все ключи (кроме "по умолчанию") в ветке HKLM/software/microsoft/windows/CurentVersion/WindowsUpdate
- потом из cmd запусти wuauclt /detectnow через пару минут просмотри файл WindowsUpdate.log там будем указано, куда лезла машина за апдейтами и какие при этом ошибки. |
|
Вернуться к началу |
|
![](templates/subSilver/images/spacer.gif) |
ibicus
Зарегистрирован: 21.06.2006 Сообщения: 4
|
Добавлено: Чт Июн 29 2006 15:55 Заголовок сообщения: |
|
|
Вот собственно лог. Клиентская машина лезет куда надо.
Сервер видится, но возникает ошибка 80072.
Клиентские машины на сервереWSUS по прежнему не видятся.
2006-06-29 16:29:32+0400 860 478 Service Main starts
2006-06-29 16:29:32+0400 860 478 Using BatchFlushAge = 12167.
2006-06-29 16:29:32+0400 860 478 Using SamplingValue = 720.
2006-06-29 16:29:32+0400 860 478 Successfully loaded event namespace dictionary.
2006-06-29 16:29:32+0400 860 478 Successfully loaded client event namespace descriptor.
2006-06-29 16:29:32+0400 860 478 Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2006-06-29 16:29:32+0400 860 478 Successfully initialized NT event logger.
2006-06-29 16:29:32+0400 860 478 Successfully initialized event uploader 0.
2006-06-29 16:29:32+0400 860 478 Successfully initialized event uploader 1.
2006-06-29 16:29:32+0400 860 478 WU client with version 5.4.3790.2180 successfully initialized
2006-06-29 16:29:32+0400 860 478 Service status is now SERVICE_RUNNING
2006-06-29 16:29:32+0400 244 6d0 Trying to make out of proc datastore active
2006-06-29 16:29:33+0400 244 6d0 Out of proc datastore is now active
2006-06-29 16:29:33+0400 860 744 Client Call Recorder finished delayed initialization
2006-06-29 16:29:33+0400 860 744 Setting next AU detection timeout to 2006-06-29 12:29:33
2006-06-29 16:29:33+0400 860 744 Setting AU scheduled install time to 2006-06-30 06:00:00
2006-06-29 16:29:33+0400 860 744 AU finished delayed initialization
2006-06-29 16:29:33+0400 860 478 AU received event of 1
2006-06-29 16:29:33+0400 860 478 WU client succeeds CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id {13F09F44-64B6-45DC-8AC2-48002C94EF1D}
2006-06-29 16:29:33+0400 860 744 Triggering AU detection through DetectNow api
2006-06-29 16:29:33+0400 860 478 AU received event of 1
2006-06-29 16:29:33+0400 860 424 WU client executing call {13F09F44-64B6-45DC-8AC2-48002C94EF1D} of type Search Call
2006-06-29 16:29:33+0400 860 424 DownloadFileInternal failed for http//192.168.0.40/SelfUpdate/wuident.cab: error 0x80072ee6
2006-06-29 16:29:33+0400 860 424 IsUpdateRequired failed with error 0x80072ee6
2006-06-29 16:29:33+0400 860 424 OS Version = 5.1.2600.2.0.65792
2006-06-29 16:29:34+0400 860 424 Computer Brand = Microsoft Corporation
2006-06-29 16:29:34+0400 860 424 Computer Model = Virtual Machine
2006-06-29 16:29:34+0400 860 424 Bios Revision = 080002
2006-06-29 16:29:34+0400 860 424 Bios Name = BIOS Date: 08/14/03 19:41:02 Ver: 08.00.02
2006-06-29 16:29:34+0400 860 424 Bios Release Date = 2003-08-14T00:00:00
2006-06-29 16:29:34+0400 860 424 Locale ID = 1049
2006-06-29 16:29:34+0400 860 424 ClientVersion: iuengine.dll = 5.4.3790.2180
2006-06-29 16:29:34+0400 860 424 ClientVersion: wuapi.dll = 5.4.3790.2180
2006-06-29 16:29:34+0400 860 424 ClientVersion: wuauclt.exe = 5.4.3790.2180
2006-06-29 16:29:34+0400 860 424 ClientVersion: wuauclt1.exe = 5.4.3790.2180
2006-06-29 16:29:34+0400 860 424 ClientVersion: wuaucpl.cpl = 5.4.3790.2180
2006-06-29 16:29:34+0400 860 424 ClientVersion: wuaueng.dll = 5.4.3790.2180
2006-06-29 16:29:34+0400 860 424 ClientVersion: wuaueng1.dll = 5.4.3790.2180
2006-06-29 16:29:34+0400 860 424 ClientVersion: wuauserv.dll = 5.4.3790.2180
2006-06-29 16:29:34+0400 860 424 ClientVersion: wucltui.dll = 5.4.3790.2180
2006-06-29 16:29:35+0400 860 424 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2006-06-29 16:29:35+0400 860 424 WU client failed Searching for update with error 0x80072ee6
2006-06-29 16:29:35+0400 860 424 Search Callback Failed, hr is 0x80072ee6
2006-06-29 16:29:35+0400 860 424 Setting next AU detection timeout to 2006-06-29 17:29:35
2006-06-29 16:29:35+0400 860 424 Setting AU scheduled install time to 2006-06-30 06:00:00
2006-06-29 16:29:35+0400 860 424 WU client calls back to search call AutomaticUpdates with code Call failed and error 0x80072ee6
2006-06-29 16:29:35+0400 860 424 WU client completed and deleted call {13F09F44-64B6-45DC-8AC2-48002C94EF1D}
2006-06-29 16:29:40+0400 860 424 REPORT EVENT: {33C9D0FB-50D2-4551-9D28-D924F235D787} 1 2006-06-29 16:29:33+0400 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80072ee6 SelfUpdate Failure Software Synchronization Error: Agent failed detecting with reason: 0x80072ee6
2006-06-29 16:29:40+0400 860 424 REPORT EVENT: {60960969-CBA5-4054-A492-81D6C0EA84BF} 2 2006-06-29 16:29:35+0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee6 AutomaticUpdates Failure Software Synchronization Error: Agent failed detecting with reason: 0x80072ee6
2006-06-29 16:29:40+0400 860 424 Created new event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{784ED3AC-57A3-4DDE-A946-48E208187421}.bin for writing.
2006-06-29 16:29:40+0400 860 424 Created new event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{C3E857C4-77E9-4DDC-8CE4-297DCC4BF788}.bin for writing. |
|
Вернуться к началу |
|
![](templates/subSilver/images/spacer.gif) |
ibicus
Зарегистрирован: 21.06.2006 Сообщения: 4
|
Добавлено: Чт Июн 29 2006 17:40 Заголовок сообщения: |
|
|
Всем спасибо. Нашел ошибку. Компьютеры увидились. |
|
Вернуться к началу |
|
![](templates/subSilver/images/spacer.gif) |
|