+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 16
Windows Server 2008 R2 Thread, WSUS in Technical; I gather that there can only be one Windows Update Server on a network. If this is correct then how ...
  1. #1
    leco's Avatar
    Join Date
    Nov 2006
    Location
    West Yorkshire
    Posts
    2,026
    Thank Post
    595
    Thanked 125 Times in 119 Posts
    Rep Power
    41

    WSUS

    I gather that there can only be one Windows Update Server on a network. If this is correct then how would I move/transition/migrate the current one onto a new server? Do I have to stop the current one whilst installing a new one?

  2. #2

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,828
    Thank Post
    875
    Thanked 1,675 Times in 1,458 Posts
    Blog Entries
    12
    Rep Power
    444
    Its just easier to setup a new WSUS server then setup your settings in WSUS and point your clients in group policy.

    another way: How to move WSUS 3.0 to a new server | Exchange Server Pro

    There is no reason why you can't have more than one WSUS server

  3. Thanks to FN-GM from:

    leco (3rd May 2010)

  4. #3
    leco's Avatar
    Join Date
    Nov 2006
    Location
    West Yorkshire
    Posts
    2,026
    Thank Post
    595
    Thanked 125 Times in 119 Posts
    Rep Power
    41
    Looked at that article but the wizard boxes are not the same as the ones I'm getting. I'm installing onto a W2K R2 server from Server Manager, so perhaps that's why.

  5. #4

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,828
    Thank Post
    875
    Thanked 1,675 Times in 1,458 Posts
    Blog Entries
    12
    Rep Power
    444
    Might be, i thought they would have been the same.

    Really im thinking installing from a fresh, doing the config then pointing clients to the new server will be just as quick and easier. It doesn't take long at all to setup.

  6. #5
    joe90bass's Avatar
    Join Date
    Oct 2007
    Location
    S Wales
    Posts
    1,349
    Thank Post
    322
    Thanked 107 Times in 96 Posts
    Rep Power
    50
    Quote Originally Posted by FN-GM View Post
    Its just easier to setup a new WSUS server then setup your settings in WSUS and point your clients in group policy.
    That's what I've done in the past, I've never tried migrating.

  7. #6

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,828
    Thank Post
    875
    Thanked 1,675 Times in 1,458 Posts
    Blog Entries
    12
    Rep Power
    444
    We did as well, in all honesty i couldn't be bothered messing around.

  8. #7
    leco's Avatar
    Join Date
    Nov 2006
    Location
    West Yorkshire
    Posts
    2,026
    Thank Post
    595
    Thanked 125 Times in 119 Posts
    Rep Power
    41
    OK thanks will have a go at just installing onto the new server and see where that gets me.

  9. #8

    3s-gtech's Avatar
    Join Date
    Mar 2009
    Location
    Wales
    Posts
    2,712
    Thank Post
    144
    Thanked 548 Times in 492 Posts
    Rep Power
    149
    Easiest way is to set the new server as a secondary WSUS server, pulling its updates from the first. You can then import the settings from the first, and when they're finished synchronising (the second will download all updates from the first), set the new one to update from Microsoft. Saves having to re-download tens of GB of updates. You then just point the clients to the new one with GP. Did this a few weeks back, worked like a charm.

  10. #9
    leco's Avatar
    Join Date
    Nov 2006
    Location
    West Yorkshire
    Posts
    2,026
    Thank Post
    595
    Thanked 125 Times in 119 Posts
    Rep Power
    41
    Thanks 3s-gtech wish I'd read that earlier. Still I've now got all the updates on the new machine now (downloaded overnight from MS), have set GP to point at it. Left it now gathering all the network computers so hopefully tomorrow it should be almost fully populated. Stray teacher laptops may be an issue for a while I'm guessing.

  11. #10


    Join Date
    Dec 2005
    Location
    In the server room, with the lead pipe.
    Posts
    4,630
    Thank Post
    275
    Thanked 777 Times in 604 Posts
    Rep Power
    223
    If you CNAME oldwsusserver to newwsusserver the laptop issue will be reduced.

    (Assumes old server is being decommissioned / renamed).

  12. #11

    powdarrmonkey's Avatar
    Join Date
    Feb 2008
    Location
    Alcester, Warwickshire
    Posts
    4,859
    Thank Post
    412
    Thanked 777 Times in 650 Posts
    Rep Power
    182
    Quote Originally Posted by leco View Post
    I gather that there can only be one Windows Update Server on a network.
    This is incorrect (which you've probably gathered, but for the sake of casual surfers).

  13. Thanks to powdarrmonkey from:

    leco (4th May 2010)

  14. #12
    leco's Avatar
    Join Date
    Nov 2006
    Location
    West Yorkshire
    Posts
    2,026
    Thank Post
    595
    Thanked 125 Times in 119 Posts
    Rep Power
    41
    Quote Originally Posted by powdarrmonkey View Post
    This is incorrect (which you've probably gathered, but for the sake of casual surfers).
    Yeah found that out now - but since I was following the instructions to the letter thought I'd better check first. Maybe the wording in the instructions could have been better, a tad ambiguous.
    Quote Originally Posted by pete
    If you CNAME oldwsusserver to newwsusserver the laptop issue will be reduced. (Assumes old server is being decommissioned / renamed).
    Would you expand on this suggestion please, I'm not quite sure what you mean. But yes the old server is to be decommissioned. Thanks.

  15. #13


    Join Date
    Dec 2005
    Location
    In the server room, with the lead pipe.
    Posts
    4,630
    Thank Post
    275
    Thanked 777 Times in 604 Posts
    Rep Power
    223
    CNAME = Canonical Name. On your dns server add a CNAME of oldserver pointing to newserver. It's handy if you want to abstract a service (mail. web, apps) from hardware and makes changeovers easier for end-users.

    CNAME is one of the options if you manually add a dns entry in the management console.

    So if an end user/computer requests oldserver, the dns server will redirect them to newserver.

  16. Thanks to pete from:

    leco (4th May 2010)

  17. #14
    leco's Avatar
    Join Date
    Nov 2006
    Location
    West Yorkshire
    Posts
    2,026
    Thank Post
    595
    Thanked 125 Times in 119 Posts
    Rep Power
    41
    Ooh thanks that looks really useful. (I think I did say I was learning - fast.) I've put in PTR and A records before but not CNAME. However, I can't actually put that one in yet as the old server is still DHCP and other stuff. That is unless specific services can be specified in the new DNS record? (can you tell I'm not sure what I'm talking about here?)

  18. #15


    Join Date
    Dec 2005
    Location
    In the server room, with the lead pipe.
    Posts
    4,630
    Thank Post
    275
    Thanked 777 Times in 604 Posts
    Rep Power
    223
    If the old server's still doing stuff that the new server isn't doing, then no - you can't add the CNAME yet.

    Unless it's only doing dhcp because the client machines will sleep with anyone giving them an ip, they don't care about their name.

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 3
    Last Post: 21st February 2008, 08:50 AM
  2. wsus
    By chrbb in forum Windows
    Replies: 4
    Last Post: 13th December 2007, 11:03 PM
  3. WSUS ?
    By mac_shinobi in forum General Chat
    Replies: 19
    Last Post: 20th April 2007, 09:42 AM
  4. Replies: 1
    Last Post: 8th November 2006, 09:57 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •