Jump to content


Dmitry Shumov

Established Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by Dmitry Shumov

  1. Hello!

    Given: domain: firma.local It installed SCVMM 2012 r2 under the domain: a.firma.local. It has a cluster named: cluster.a.firma.local cluster node 2: node1.a.firma.local and node2.a.firma.local task, connect cluster.a.firma.local cluster SCVMM 2012 r2.

    Configured run as an account, I try to add a cluster of error pops up:

    892720.png

     

    rechecked everything that is written there - everything is normal. In the DNS A record for all three present name. All names resolvyatsya and Ping. Rights in a domain is. Firewall - off. Not connected cluster. I decided to make knight's move, and ordered all three nodes in the hosts file. Not podklyuchaetsya. I tried to connect nodes poodelnosti. On node1.a.firma.local pops up the same error, but node2.a.firma.local be and can be connected to it. I rechecked everything again. In iron and all of the same settings. Agents set locally, stepping on each node. Does not work. Tell me where and what else can you see?

     

    UPD: made experiment, destroyed the cluster tried to add nodes individually - seeing all nodes. You can add. Assembled on a new cluster - the same error.

  2. Hello!

    Once on the WSUS server walked Server Cleanup Wizard, all updates to the SUP SCCM 2012 has expired: (link to the screenshot), when you try to download any update in the SUP SCCM message is shown: "all software updates in this selection are expired or metadata only the deployment can not be download " errors on the WSUS nor SUP SCCM not. Hand start the synchronization results did not give

    Today logs:

    WSUSCtrl.log:

    Timed Out...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    There are no unhealthy WSUS Server components on WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Successfully checked database connection on WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	25.09.2014 0:29:27	3656 (0x0E48)
    Timed Out...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    There are no unhealthy WSUS Server components on WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Successfully checked database connection on WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	25.09.2014 1:26:26	3656 (0x0E48)
    Timed Out...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    There are no unhealthy WSUS Server components on WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:25	3656 (0x0E48)
    Successfully checked database connection on WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:26	3656 (0x0E48)
    Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	25.09.2014 2:23:26	3656 (0x0E48)
    Timed Out...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    There are no unhealthy WSUS Server components on WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Successfully checked database connection on WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	25.09.2014 3:20:25	3656 (0x0E48)
    Timed Out...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    There are no unhealthy WSUS Server components on WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Successfully checked database connection on WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	25.09.2014 4:17:24	3656 (0x0E48)
    Timed Out...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    There are no unhealthy WSUS Server components on WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Successfully checked database connection on WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	25.09.2014 5:14:23	3656 (0x0E48)
    Timed Out...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    There are no unhealthy WSUS Server components on WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Successfully checked database connection on WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	25.09.2014 6:11:22	3656 (0x0E48)
    Timed Out...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    There are no unhealthy WSUS Server components on WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Successfully checked database connection on WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	25.09.2014 7:08:21	3656 (0x0E48)
    Timed Out...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 8:05:20	3656 (0x0E48)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	25.09.2014 8:05:20	3656 (0x0E48)
    Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 8:05:20	3656 (0x0E48)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	25.09.2014 8:05:20	3656 (0x0E48)
    Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	25.09.2014 8:05:20	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 8:05:20	3656 (0x0E48)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384	SMS_WSUS_CONTROL_MANAGER	25.09.2014 8:05:20	3656 (0x0E48)
    Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	25.09.2014 8:05:20	3656 (0x0E48)
    Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	25.09.2014 8:05:20	3656 (0x0E48)
    Successfully connected to local WSUS s
    

    wsyncmgr.log:

    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 0:00:10	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 1:00:14	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 2:00:13	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 3:00:12	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 4:00:11	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 5:00:10	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 6:00:09	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 7:00:08	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 8:00:07	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:00:06	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:29:19	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:29:34	3668 (0x0E54)
    Wakeup by inbox drop	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:04	3668 (0x0E54)
    Found local sync request file	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:09	3668 (0x0E54)
    Starting Sync	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:09	3668 (0x0E54)
    Performing sync on local request	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:09	3668 (0x0E54)
    Read SUPs from SCF for msk-sccm.vostok-electra.ru	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:09	3668 (0x0E54)
    Found 1 SUPs	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:09	3668 (0x0E54)
    Found active SUP msk-sccm.vostok-electra.ru from SCF File.	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:09	3668 (0x0E54)
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=msk-sccm.vostok-electra.ru SITE=MSK PID=1760 TID=3668 GMTDATE=Чт сен 25 05:30:09.653 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:09	3668 (0x0E54)
    Synchronizing WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:32	3668 (0x0E54)
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=msk-sccm.vostok-electra.ru SITE=MSK PID=1760 TID=3668 GMTDATE=Чт сен 25 05:30:32.663 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:32	3668 (0x0E54)
    Synchronizing WSUS server msk-sccm.vostok-electra.ru ...	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:32	1804 (0x070C)
    sync: Starting WSUS synchronization	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:32	1804 (0x070C)
    sync: WSUS synchronizing categories	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:35	1804 (0x070C)
    Done synchronizing WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:38	1804 (0x070C)
    Sleeping 2 more minutes for WSUS server sync results to become available	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:30:38	1804 (0x070C)
    Set content version of update source {629E3BB8-D63E-4FBB-8510-8B7B338D954F} for site MSK to 28	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	3668 (0x0E54)
    Synchronizing SMS database with WSUS server msk-sccm.vostok-electra.ru	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	3668 (0x0E54)
    STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=msk-sccm.vostok-electra.ru SITE=MSK PID=1760 TID=3668 GMTDATE=Чт сен 25 05:32:39.742 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	3668 (0x0E54)
    Synchronizing SMS database with WSUS server msk-sccm.vostok-electra.ru ...	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	1972 (0x07B4)
    sync: Starting SMS database synchronization	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	1972 (0x07B4)
    requested localization languages: en,ru	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	1972 (0x07B4)
    Syncing updates arrived after 09/24/2014 22:32:09	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	1972 (0x07B4)
    Requested categories: Product=Windows Drivers, Product=Microsoft SQL Server 2012, Product=Windows 8.1, Product=Office 2013, Product=Office 2010, Product=Windows Server 2012, Product=Windows 7, Product=Windows Server 2012 R2, Product=Windows Server 2008 R2, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Service Packs, UpdateClassification=Tools, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	1972 (0x07B4)
    sync: SMS synchronizing categories	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	1972 (0x07B4)
    sync: SMS synchronizing categories, processed 0 out of 251 items (0%)	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:39	1972 (0x07B4)
    sync: SMS synchronizing categories, processed 251 out of 251 items (100%)	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:41	1972 (0x07B4)
    sync: SMS synchronizing categories, processed 251 out of 251 items (100%)	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:41	1972 (0x07B4)
    sync: SMS synchronizing updates	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:42	1972 (0x07B4)
    SyncBatchCount not set, using default 1	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:42	1972 (0x07B4)
    SyncBatchMinCreationDate not set, using default 01/01/2001 00:00:00	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:42	1972 (0x07B4)
    sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:42	1972 (0x07B4)
    Done synchronizing SMS with WSUS Server msk-sccm.vostok-electra.ru	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:43	1972 (0x07B4)
    Set content version of update source {629E3BB8-D63E-4FBB-8510-8B7B338D954F} for site MSK to 28	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:43	3668 (0x0E54)
    STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=msk-sccm.vostok-electra.ru SITE=MSK PID=1760 TID=3668 GMTDATE=Чт сен 25 05:32:43.758 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:43	3668 (0x0E54)
    Sync succeeded. Setting sync alert to canceled state on site MSK	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:43	3668 (0x0E54)
    No changes made to the SMS database, content version remains 28	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:43	3668 (0x0E54)
    Sync time: 0d00h02m34s	SMS_WSUS_SYNC_MANAGER	25.09.2014 9:32:43	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 10:32:43	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 11:32:42	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 12:32:41	3668 (0x0E54)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 13:32:40	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:07:21	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:15:46	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:16:01	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:26:56	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:27:21	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:27:31	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:27:41	3668 (0x0E54)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:27:51	3668 (0x0E54)
    Thread terminated by service request.	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:35:52	3668 (0x0E54)
    SMS_EXECUTIVE started SMS_WSUS_SYNC_MANAGER as thread ID 1600 (0x640).	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:36:50	2016 (0x07E0)
    Log level 2	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:36:50	1600 (0x0640)
    Wakeup by SCF change	SMS_WSUS_SYNC_MANAGER	25.09.2014 14:37:03	1600 (0x0640)
    Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	25.09.2014 15:37:08	1600 (0x0640)
    
    
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.