40 new desktops - some show up in Unassigned some don't show up at

Discussion in 'Windows Update' started by Eric, Mar 17, 2009.

  1. Eric

    Eric Guest

    I have a WSUS 3.0 SP1 machine that is controlling the updates to machines in
    our domain. I have just rolled out 40 computers, all with different names, as
    new desktops for our users. The computers are sitting within different OUs,
    that have Group Policies attached to point them towards the WSUS server. All
    of the computers are correctly showing the greyed out options in Automatic
    Updates on the client, and they're definitely contacting the local server.
    What's odd is that some of the new computers (in different OUs), are showing
    up in the Update Services console under Unassigned Computers, but most of
    them are not anywhere.

    Are there logs or anywhere on the server/clients that I should be looking
    for errors? This is a little confusing to say the least. We're using the same
    Administrative template that we were using before in our Group Policy.

    Thank you,

    Eric, Mar 17, 2009
    1. Advertisements

  2. Perhaps ask in the SUS related newsgroups?

    From the web:

    Inside your newsreader:

    Cross-posted for convenience.
    Shenan Stanley, Mar 17, 2009
    1. Advertisements

  3. Eric

    Harold Himes Guest

    I've had this problem when the desktops have duplicate SIDs. Did you image
    the Desktops? Did you you run sysprep or newsid afterwards?
    Harold Himes, Mar 17, 2009
  4. Eric

    Dave Mills Guest

    The logfile is %windir%\WindowsUpdate.log.

    It sounds like the new GPO's are not specifying the correct group name or that
    the groups specified has not been created in the WSUS console.
    Dave Mills, Mar 18, 2009
    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.