Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Migration to New WSUS Server

Answered Migration to New WSUS Server

  • Monday, January 14, 2013 3:45 PM
     
     
    Sign In to Vote
    0

    I am in the process of migrating all of my clients from our current physical server to a new virtual server.

    Current Setup - Physical Server on Domain A

    New Server - VM on Domain B

    I have created the same group names on the new server that I had on the previous one.  I change our group policy to point to the new server name and left all other settings the same since the groups are named the same.  The machines are now showing up on the new server but they are all in teh "Unassigned Computers" group.  Any help on why they aren't going in the correct group?

     

All Replies

  • Tuesday, January 15, 2013 5:30 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Thank you for posting here.

    If you wanna enable the client-targeting feature,change the setting in Options | Computers to use GP or registry settings on computers,define the target group name in the GPO with semi-colon (;) ,and then create target group name in the WSUS computer groups. After a while, the computers will appear in the groups automatically.Remember that change membership option will be greyed-out when you enable client-targeting feature.

    With the "client side targeting"policy set to Enabled, the client will inform the WSUS Server what it's group membership(s) actually are.They would add into a corresponding groups that you enabled the client-targeting on GPO.If not, they will appear in the unassigned groups.

    Remember that change membership option will be greyed-out when you enable client-targeting feature.So you can't move the computer as you like except through GPO.

    Regards,

    Clarence

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Tuesday, January 15, 2013 8:04 AM
     
     
    Sign In to Vote
    0

    Also checking this:

    http://technet.microsoft.com/en-us/library/ee822824%28v=ws.10%29.aspx

    Kind regards,

    Tim
    MCITP, MCTS
    http://directoryadmin.blogspot.com

    This posting is provided 'AS IS' with no warranties or guarantees and confers no rights.

    "If this thread answered your question, please click on "Mark as Answer"

     
  • Tuesday, January 15, 2013 6:04 PM
     
     
    Sign In to Vote
    0

    All of this is already turned on.  The only thing I did was change the server name.

    Old Policy

    Servername: OLDWSUSServer

    Group Name:  Remote Office

    New Policy

    Servername: New WSUSServer

    Group Name:  Remote Office

     
  • Thursday, January 24, 2013 1:46 PM
     
     Answered
    Sign In to Vote
    0
    I rebuilt the server and it is now working.  I'm assuming I configured something wrong the first time.
    • Marked As Answer by Tim.Harris Thursday, January 24, 2013 1:46 PM
    •