locked
All machines in Unassigned Computers and not in their correct Groups RRS feed

  • General discussion

  • I have a new WSUS server on Windows 2012 R2.  It is replacing our existing WSUS server.  I changed the GPO's to point the machines to the new server with port 8530.  They are all showing up but they are all in Unassigned Computers and not in the groups that they should belong to.  I am using the same groups and didn't change that policy at all so I know there aren't any typo's or anything like that.

    Mary

    Wednesday, October 8, 2014 8:10 PM

All replies

  • did you migrate the database from the old server? (this would preserve the groups)

    If not, have you created the groups on the new server?


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Wednesday, October 8, 2014 8:49 PM
  • I actually made the the server a replication/downstream server of the old server so I could have all the groups and approvals and from there made it it's own stand alone WSUS server.

    Mary

    Wednesday, October 8, 2014 8:51 PM
  • I actually made the the server a replication/downstream server of the old server so I could have all the groups and approvals and from there made it it's own stand alone WSUS server.

    This is a natural behavior of migrating via replication when using Server-Side Targeting.

    You have two options:

    • Use the console to put the computers in the groups in which they belong.
    • If the *original* server is still available, you can use the free WSUSComputerMigrator tool from SolarWinds to export the group names/members from the old server and import them to the new server.

    Since the clients have already checked in with the new server, you'll need to *DELETE* all existing computer records on the new server IMMEDIATELY BEFORE performing the import using the free tool.


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

    Thursday, October 9, 2014 3:54 AM
  • Worked like a charm, Thanks!

    Mary

    Thursday, October 9, 2014 4:14 PM
  • Well, I thought it did but new computers aren't going into the correct group they are staying in Unassigned.

    Mary

    Tuesday, October 14, 2014 4:35 PM
  • Well, I thought it did but new computers aren't going into the correct group they are staying in Unassigned.

    Did you set Options -> Computers to "Use Group Policy..." ?

    Are the clients actually being assigned to a group via Group Policy? (e.g. does the Registry Value exist and have the correct data? does the WindowsUpdate.log reflect the assigned target group?)


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

    Wednesday, October 15, 2014 2:37 AM

  • Options are set now, that should help.  Thanks!



    Wednesday, October 15, 2014 1:01 PM