none
WSUS and SIDs

    Pergunta

  • Hello,

    I have what I hope to be a simple question but I have searched through the forums here and I amnot finding exactly what I am looking for.

    My question is this:

    In a domain environment does WSUS use the local machines SID to identify the client or the domain SID of the computer object? Are you unable to view the SID associated with a client in WSUS? I am looking but am new to it and am not seeing any reporting stating such so far.

    Thank you.

    quinta-feira, 28 de fevereiro de 2013 20:06

Respostas

  • In a domain environment does WSUS use the local machines SID to identify the client

    No.

    or the domain SID of the computer object?

    No.

    Are you unable to view the SID associated with a client in WSUS?

    The SID associated with the Windows Update Agent is an application ID, not a system ID.

    You'll find it in HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate in the "SusClientID" value.

    It's also logged in the WindowsUpdate.log in the entry where the targeting cookie is initialized:

    2013-02-28 15:14:00:470  956 2054 PT Initializing simple targeting cookie, clientId = 1196dd05-2453-486d-92fa-578f14b14869, target group = <groupName>, DNS name = <machineName>


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    quinta-feira, 28 de fevereiro de 2013 21:16
    Moderador

Todas as Respostas

  • In a domain environment does WSUS use the local machines SID to identify the client

    No.

    or the domain SID of the computer object?

    No.

    Are you unable to view the SID associated with a client in WSUS?

    The SID associated with the Windows Update Agent is an application ID, not a system ID.

    You'll find it in HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate in the "SusClientID" value.

    It's also logged in the WindowsUpdate.log in the entry where the targeting cookie is initialized:

    2013-02-28 15:14:00:470  956 2054 PT Initializing simple targeting cookie, clientId = 1196dd05-2453-486d-92fa-578f14b14869, target group = <groupName>, DNS name = <machineName>


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    quinta-feira, 28 de fevereiro de 2013 21:16
    Moderador
  • Thank you. Am I correct by stating that if a client has the same client sid as another that they can still receive the updates, it is just the reporting aspect of the SUS that will not list one of the duplicate clients?

    I ask because this is the behavior I am seeing. I have found systems that have the same susclientid, thye both still get the updates, but only one is listed in the SUS server reports. So while I assum that is how it works, clarification would be great. Thank you.

    sexta-feira, 1 de março de 2013 13:40
  • Am I correct by stating that if a client has the same client sid as another that they can still receive the updates, it is just the reporting aspect of the SUS that will not list one of the duplicate clients?

    This is correct.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    sábado, 25 de maio de 2013 16:07
    Moderador