The computer has not reported status yet ?

Discussion in 'Update Services' started by Bob, Dec 28, 2007.

  1. Bob

    Bob Guest

    Hello,

    I'm slowly moving users over to a new server - 2003 - and WSUS 3.0 off a
    2000 server with WSUS 2.0.

    I have three groups, moved the computers from two groups so far. In my
    servers group, I have my 2 DC's which are in the All Computers groups, but
    not showing in the Servers group where they should be - all other servers are
    good.

    When I look at the computers my 2 DC's do not give me the IP/OS, etc, it
    just says ------ The computer has not reported status yet.

    These are the only 2 systems that are not reporting status. I moved the
    computers in the servers group about 18-19 hours ago, all others show a
    status with todays date.

    Can you tell me what would prevent a computer from not reporting status ?
    how to fix ?

    Thanks,
    Bob
     
    Bob, Dec 28, 2007
    #1
    1. Advertisements

  2. Check the WindowsUpdate.log file on the DCs. Try running

    wuauclt /detectnow

    and check the file.

    This could be caused by an invalid server name specified or perhaps you
    cloned the computers?

    --

    Regards,
    Hank Arnold
    Microsoft MVP
    Windows Server - Directory Services
     
    Hank Arnold (MVP), Dec 28, 2007
    #2
    1. Advertisements

  3. I'd bet a dozen donuts that you failed to update the policy linked to the
    "Domain Controllers" OU.



    --
    Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
    Senior Data Architect, APQC, Houston, Texas
    MVP - Software Distribution (2005-2007)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Dec 28, 2007
    #3
  4. Bob

    Bob Guest

    I did wuauclt.exe /detectnow previously on both DC's and again a few minutes
    ago. The computers are not cloned.

    I also did gpupdate/force.

    The server name is not invalid, same name's in the same group name - servers
    group name.

    What is the windows update log file ?

    Thanks,
    Bob
     
    Bob, Dec 28, 2007
    #4
  5. Bob

    Bob Guest

    Ok ----------- I found the mystery.... I ran the command - wuauclt.exe
    /detectnow, then I opened the windowsupdate.log file, and --------- I see
    both DC's are still pointing to my old WSUS server !!

    Can you tell me how to point the two DC's to my "new" WSUS server 3.0 ??

    The other member servers are all where they need to be, same with my
    computers, I also checked the log on those servers and they are pointing to
    the new WSUS.


    If someone can tell me how to get my two DC's to target the new WSUS server,
    I should be set...


    Thanks !
    Bob
     
    Bob, Dec 28, 2007
    #5
  6. As I believe I suggested about nine hours ago, and prior to the last two
    replies you've posted...

    Update the GPO linked to the Domain Controllers OU! :)


    --
    Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Dec 29, 2007
    #6
  7. Bob

    Bob Guest

    Thanks for the replies, but ------ my GP has 3 groups ----- test,
    production, servers ------ ALL three groups in my GP ARE pointing to the new
    WSUS server ------ the two DC's are in the SERVERS group, along with my non-
    DC servers.

    I assume this is what you suggest I do, which I'm already going ---- that
    was the first thing I did, before I moved computers. If we are on the same
    page, then this is not working. Please advise.

    Bob
     
    Bob, Dec 30, 2007
    #7
  8. Bob

    Bob Guest

    Update *************** please disregard the last reply from me, I
    found/resolved the problem. My DC's are now reporting to the new WSUS server.

    Thanks,
    Bob
     
    Bob, Dec 30, 2007
    #8
  9. Could you post the solution? Others may benefit...

    --

    Regards,
    Hank Arnold
    Microsoft MVP
    Windows Server - Directory Services
     
    Hank Arnold (MVP), Dec 30, 2007
    #9
  10. This is a highly unorthodox and not-recommended configuration.

    However are you applying the "Default Domain Controllers Policy" to the
    domain controllers if they're no longer in their own OU?

    Why would you take the domain controllers out of the "Domain Controllers" OU
    which is created, by default, when the domain and first DC was created?

    --
    Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Dec 30, 2007
    #10
  11. I'm most interested, also, since it now appears that his DCs were not in the
    "Domain Controllers" OU!


    --
    Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Dec 30, 2007
    #11
  12. Bob

    Bob Guest

    Well ---- the naming of the OU's and Group names on WSUS were not the same.
    I did not setup the old WSUS/OU, but here we go -----

    The OU Domain Controller did not has the same name on WSUS, the OU Domain
    controller pointed to the Servers group on the WSUS. If I did the creation
    naming I would have done the following -----

    Have the OU and Group name on WSUS match exactly, there are 4 OU names - DC,
    Servers, Production, Test. But the group names on WSUS are ---- Server,
    production, Test ---- notice no computer group name DC, that is what I was
    missing. Why the previous person pointed the DC OU to the "Servers" group I
    don't know ---- I would have pointed the DC OU to the DC computer group name
    on WSUS.

    Sorry if a bit run on, but I'm good to go.

    Thanks,
    Bob
     
    Bob, Dec 30, 2007
    #12
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.