locked
SCE Last contact with computers was 14 days ago RRS feed

  • Question

  • Every thing was working fine in System Center Essentials 2007 then I noticed that the last contact was 14 days ago with ALL computers and servers. I checked the GPO based on my last fix of this issue and found that the only Default GPO that is listed on the primary and secondary servers (Windows 2003 srv pk 2) is the one on the secondary. How do I use the one on the primary server instead. I was having hardware issues with the primary so I moved all FSMO rolls and the GAL to the secondary temporarily. Could this be the reason that all clients are using the secondary for the GPO?

    Thanks

    Saturday, September 5, 2009 3:57 PM

Answers

  • Hi,

    After running the wizard, can you find SCE managed computer group and SCE managed computers group policy in AD?

    If you can, please run following command on client to manually report their status to SCE server:

    gpupdate /force

    wuauclt /reportnow
    • Marked as answer by Eric Zhang CHN Tuesday, September 15, 2009 9:42 AM
    Wednesday, September 9, 2009 10:27 AM
  • This resolved our issue. Below are the notes form Microsoft's fee based support.



    WSUS clients failing to report back to WSUS server I hope that you were delighted with the service provided to you. I am providing you with a summary of the key points of the case for your records. If you ever have any questions please feel free to call me.  

     

    Problem:

    ========

     

    WSUS clients failing to report back to WSUS server

     

    Resolution:

    ==========

     

    Ø  We checked Windowsupdate.log and found is failing with following error.

    -----------

    DownloadFileInternal failed for http://adminsrv.ourcompany.com:8530/SelfUpdate/wuident.cab: error 0x80190193

    2009-09-16        13:04:59-0400    1028     770       IsUpdateRequired failed with error 0x80244018

    ----------

     

    Ø  We tried running Wsusutil /detectnow and it came up working properly except client not reporting.

     

    We tried accessing http://localhost/selfupdate/wuident.cab on Wsus server and we could access the can file

    We tried the same from Client side. and tried accessing  http://adminsrv.ourcompanycom:8530/SelfUpdate/wuident.cab , It failed with 403 error

     

    Ø  We checked IISlog and found following.

    --------------

    2009-09-14 19:01:32 W3SVC73335825 192.168.1.211 HEAD /selfupdate/wuident.cab 0909141901 8530 - 192.168.1.189 Windows-Update-Agent 403 2 5

    2009-09-14 19:01:32 W3SVC73335825 192.168.1.211 GET /selfupdate/wuident.cab 0909141901 8530 - 192.168.1.189 Windows-Update-Agent 403 2 5

    2009-09-14 19:01:32 W3SVC73335825 192.168.1.211 HEAD /selfupdate/wuident.cab 0909141901 8530 - 192.168.1.189 Windows-Update-Agent 403 2 5

    2009-09-14 19:01:32 W3SVC73335825 192.168.1.211 GET /selfupdate/wuident.cab 0909141901 8530 - 192.168.1.189 Windows-Update-Agent 403 2 5

    -------------

     

     

    Ø  Found it could be issue with Metabase and permission, Looked  at metabase in c:\windows\system32\inetsrv

     

    Checked IISmebase.xml file and found following entries

    -------

    "<IIsWebVirtualDir Location ="/LM/W3SVC/1/ROOT"

      AccessFlags="AccessExecute | AccessRead | AccessWrite | AccessScript | AccessNoRemoteExecute | AccessNoRemoteRead | AccessNoRemoteWrite | "

    ---------------

     

    Ø  We installed IIS resource kit and usd Metabse to fine the value of accessfilter it was set to 30216, changed the value to 513 & Ran IISreset and We could access the selfupdate and wuident.cab file

     

    Ø  Ran Wuauclt /detectnow and client came up fine on SCE console.

    • Marked as answer by bizzie247 Wednesday, September 16, 2009 7:56 PM
    Wednesday, September 16, 2009 7:55 PM

All replies

  • Saturday, September 5, 2009 3:59 PM
  • Hi,

    If you cannot find SCE managed computers group policy, please open SCE console, in administration space, re-run "Feature configuration Wizard" which will automatically create SCE related group policy and computer group.
    Monday, September 7, 2009 11:37 AM
  • Thanks, I ran the wizard but it didn't help. Still no contact with new machines and the old ones still last contact 15 days.

    Monday, September 7, 2009 4:25 PM
  • Hi,

    After running the wizard, can you find SCE managed computer group and SCE managed computers group policy in AD?

    If you can, please run following command on client to manually report their status to SCE server:

    gpupdate /force

    wuauclt /reportnow
    • Marked as answer by Eric Zhang CHN Tuesday, September 15, 2009 9:42 AM
    Wednesday, September 9, 2009 10:27 AM
  • This resolved our issue. Below are the notes form Microsoft's fee based support.



    WSUS clients failing to report back to WSUS server I hope that you were delighted with the service provided to you. I am providing you with a summary of the key points of the case for your records. If you ever have any questions please feel free to call me.  

     

    Problem:

    ========

     

    WSUS clients failing to report back to WSUS server

     

    Resolution:

    ==========

     

    Ø  We checked Windowsupdate.log and found is failing with following error.

    -----------

    DownloadFileInternal failed for http://adminsrv.ourcompany.com:8530/SelfUpdate/wuident.cab: error 0x80190193

    2009-09-16        13:04:59-0400    1028     770       IsUpdateRequired failed with error 0x80244018

    ----------

     

    Ø  We tried running Wsusutil /detectnow and it came up working properly except client not reporting.

     

    We tried accessing http://localhost/selfupdate/wuident.cab on Wsus server and we could access the can file

    We tried the same from Client side. and tried accessing  http://adminsrv.ourcompanycom:8530/SelfUpdate/wuident.cab , It failed with 403 error

     

    Ø  We checked IISlog and found following.

    --------------

    2009-09-14 19:01:32 W3SVC73335825 192.168.1.211 HEAD /selfupdate/wuident.cab 0909141901 8530 - 192.168.1.189 Windows-Update-Agent 403 2 5

    2009-09-14 19:01:32 W3SVC73335825 192.168.1.211 GET /selfupdate/wuident.cab 0909141901 8530 - 192.168.1.189 Windows-Update-Agent 403 2 5

    2009-09-14 19:01:32 W3SVC73335825 192.168.1.211 HEAD /selfupdate/wuident.cab 0909141901 8530 - 192.168.1.189 Windows-Update-Agent 403 2 5

    2009-09-14 19:01:32 W3SVC73335825 192.168.1.211 GET /selfupdate/wuident.cab 0909141901 8530 - 192.168.1.189 Windows-Update-Agent 403 2 5

    -------------

     

     

    Ø  Found it could be issue with Metabase and permission, Looked  at metabase in c:\windows\system32\inetsrv

     

    Checked IISmebase.xml file and found following entries

    -------

    "<IIsWebVirtualDir Location ="/LM/W3SVC/1/ROOT"

      AccessFlags="AccessExecute | AccessRead | AccessWrite | AccessScript | AccessNoRemoteExecute | AccessNoRemoteRead | AccessNoRemoteWrite | "

    ---------------

     

    Ø  We installed IIS resource kit and usd Metabse to fine the value of accessfilter it was set to 30216, changed the value to 513 & Ran IISreset and We could access the selfupdate and wuident.cab file

     

    Ø  Ran Wuauclt /detectnow and client came up fine on SCE console.

    • Marked as answer by bizzie247 Wednesday, September 16, 2009 7:56 PM
    Wednesday, September 16, 2009 7:55 PM