+ Post New Thread
Page 3 of 5 FirstFirst 12345 LastLast
Results 31 to 45 of 63
Windows Server 2008 R2 Thread, How to Setup WSUS on 2003/2008/2008 R2 Server in Technical; gpedit locally can do it you can create a reg file that does it...
  1. #31


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,577
    Thank Post
    228
    Thanked 853 Times in 732 Posts
    Rep Power
    294
    gpedit locally can do it
    you can create a reg file that does it

  2. #32

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Quote Originally Posted by Gaga View Post
    Hello Michael,

    Is there a way I can point my clients to the Wsus server with having to do it with GPO's. I work in an environment where I have limited access to AD and Group Policy management. I was hoping to figure out a way to have my 10 other Windows 2003 Servers to talk to the Wsus without having to GPOs.

    Your post was very helpful.

    Adam
    If you import the below reg file, this should allow you to use WSUS without using GPOs:

    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    "WUServer"="http://SERVERNAME"
    "WUStatusServer"="http://SERVERNAME"
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
    "NoAutoUpdate"=dword:00000000
    "AUOptions"=dword:00000004
    "ScheduledInstallDay"=dword:00000000
    "ScheduledInstallTime"=dword:0000000a
    "DetectionFrequencyEnabled"=dword:00000001
    "DetectionFrequency"=dword:00000001
    "AutoInstallMinorUpdates"=dword:00000001
    "IncludeRecommendedUpdates"=dword:00000000
    "NoAutoRebootWithLoggedOnUsers"=dword:00000001
    "RebootRelaunchTimeoutEnabled"=dword:00000001
    "RebootRelaunchTimeout"=dword:00000078
    "RescheduleWaitTimeEnabled"=dword:00000001
    "RescheduleWaitTime"=dword:0000003c
    "UseWUServer"=dword:00000001

  3. 2 Thanks to Michael:

    Davit2005 (21st April 2012), speckytecky (21st April 2012)

  4. #33

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Quote Originally Posted by edutech4schools View Post
    Should we go for the 2010 version?
    In my testing the Microsoft Report Viewer Redistributable 2010 didn't work with WSUS 3 SP2.

    I would however recommend the Microsoft Report Viewer Redistributable 2008 SP1 which you can download here

  5. #34

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340

    Thumbs up

    Manage WSUS from a Workstation

    Requirements: Windows XP SP3, Windows Vista or Windows 7

    Additional requirements: A 2003, 2008 or 2008 R2 server with WSUS 3.0 SP2 already setup/configured.

    For your reference, even if you have a 64Bit server running 2008 R2 and a 32Bit Windows 7 workstation, this method will still work. It simply means you're running an x64 version of WSUS on your server and an x86 version of the console on your workstation. There is no difference in the software and/or its options/tools. This may sound obvious, but I have been asked similar questions before!

    On your workstation:

    Download/install Report Viewer 2008 SP1 here first.

    Download/install WSUS 3.0 SP2 here (x86 or x64)

    When you run Setup, choose Administration Console only

    You can now access Windows Server Updates Services on Administrative Tools. When you run it first time, you'll be prompted for the SERVERNAME and Port.

    Enter your SERVERNAME, you don't need the FQDN. If you've installed WSUS using default settings (on your server) leave the port as 80 and leave SSL unticked. Click on Connect and you can now manage WSUS from your workstation. You have access to all tools, just as you would on the server itself.

    I've used this method for years, but I thought I'd share as I didn't include it with setting up WSUS guides.

  6. Thanks to Michael from:

    speckytecky (29th April 2012)

  7. #35

    Join Date
    Feb 2012
    Location
    Calical
    Posts
    6
    Thank Post
    1
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Thanks Michael. I did it through the local group policy. It works Awesome.

    Cheers,

  8. #36
    TechSupp's Avatar
    Join Date
    Mar 2007
    Location
    South Yorkshire
    Posts
    1,876
    Thank Post
    295
    Thanked 120 Times in 101 Posts
    Rep Power
    40
    Dragging this back up again, sorry. I had set up a WSUS server (ran dhcp, ad, etc etc) that worked just fine untill the server itself started playing up so we had a new server to run AD, DHCP ect except WSUS. We had the old server demoted from a domain controller to a plain old PC running Server 2003, now the question is can I still run WSUS on the PC running Server 2003 and have the WSUS group policy manage the clients on the new 2008 R2 server? Trying to fix the original 2003 install at the moment but cant figure out if its truly broken or not possible to run it in this way or not which is why it wont play ball?

  9. #37

    Join Date
    May 2011
    Location
    Jus North of London, close but not too close
    Posts
    736
    Thank Post
    172
    Thanked 56 Times in 54 Posts
    Rep Power
    35
    It is poss to have WSUS on a completely different server not a DC. It is then possible to setup the basic settings within group policy and get the clients pointing to computer groups. It is also possible to override the client targeting for particular OU's by just changing the targetted group if necessary :-)

    On a connected note, Anyone know how to point SCCM to a different WSUS if WSUS has broken? Cheers

  10. #38

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    You can install WSUS on a DC or Member Server.

    You can of course setup GPOs so workstations know where to download updates and when to apply updates, but WSUS by default will place computers in the Unassigned group. To my knowledge, there isn't a GPO to specify which group computers should go into.

    All is not lost however. Once computers have reported to WSUS, you can then move them into groups you've created in WSUS, and then target updates accordingly.

    Targetting is useful for testing purposes, but also for very large networks with 1000+ workstations. Using a combination of different GPOs, different sets of workstations would/could update at different times. This can be a lot of work initially, but BITS delivers updates intelligently, keeping network traffic as low as possible.

  11. #39

    plexer's Avatar
    Join Date
    Dec 2005
    Location
    Norfolk
    Posts
    13,341
    Thank Post
    624
    Thanked 1,584 Times in 1,421 Posts
    Rep Power
    414
    You can apply wsus groups via gpo.

    Ben

  12. #40
    TechSupp's Avatar
    Join Date
    Mar 2007
    Location
    South Yorkshire
    Posts
    1,876
    Thank Post
    295
    Thanked 120 Times in 101 Posts
    Rep Power
    40
    Well, managed to breathe life in to the WSUS server again and I can confirm now that a WSUS server can be on its own and the clients can be told where it is via our DC server GPO, very happy now! Funny how little things like that keep you going. My main problem was getting the original install uninstalled, had to use the MS cleanup utility to get rid of it then reinstall it. Clients started replying to it fairly quickly as well after it was synchronised. Happy bunny now.

  13. #41

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Quote Originally Posted by plexer View Post
    You can apply wsus groups via gpo.

    Ben
    Which GPO allows you to do this? Please share, as it's something that could prove useful!

  14. #42

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Quote Originally Posted by TechSupp View Post
    Well, managed to breathe life in to the WSUS server again and I can confirm now that a WSUS server can be on its own and the clients can be told where it is via our DC server GPO, very happy now! Funny how little things like that keep you going. My main problem was getting the original install uninstalled, had to use the MS cleanup utility to get rid of it then reinstall it. Clients started replying to it fairly quickly as well after it was synchronised. Happy bunny now.
    Glad you got it all sorted. WSUS is definitely worth setting up. I've started work on a new network recently with no WSUS whatsoever, so god knows yet how out-of-date everything is! Frightening to find networks like this

  15. #43

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    @plexer - Are you referring to the following GPO:

    Computer Config > Policies > Admin Templates > Windows Components > Windows Update - Enabled - Enable client-side targetting?

    So if I specify a target group, will it actually move the computer object in WSUS to that group, or will it just tell the workstation to read information from that target group? It's not very clear.

  16. #44

    Join Date
    Dec 2007
    Posts
    864
    Thank Post
    90
    Thanked 164 Times in 139 Posts
    Rep Power
    49
    Quote Originally Posted by Michael View Post
    @plexer - Are you referring to the following GPO:

    Computer Config > Policies > Admin Templates > Windows Components > Windows Update - Enabled - Enable client-side targetting?

    So if I specify a target group, will it actually move the computer object in WSUS to that group, or will it just tell the workstation to read information from that target group? It's not very clear.
    The computer object will be moved into the corresponding WSUS Computer Group.
    The computer group will also be created automatically if it does not already exist.

  17. Thanks to MYK-IT from:

    Michael (29th April 2012)

  18. #45

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Thanks! I'll certainly have to try this out!

SHARE:
+ Post New Thread
Page 3 of 5 FirstFirst 12345 LastLast

Similar Threads

  1. How to setup a windows server 2008
    By vlan2 in forum Windows Server 2008 R2
    Replies: 2
    Last Post: 15th February 2011, 12:47 PM
  2. Replies: 6
    Last Post: 11th July 2010, 10:15 AM
  3. Connect to a 2008 R2 server from a 2003 TS Client
    By dhoward_westexetc in forum Windows Server 2008 R2
    Replies: 1
    Last Post: 9th June 2010, 10:30 AM
  4. Replies: 5
    Last Post: 13th April 2010, 05:26 PM
  5. Essential tools to manage a Windows 2003/2008 domain?
    By reggiep in forum Windows Server 2000/2003
    Replies: 8
    Last Post: 6th May 2009, 09:47 AM

Thread Information

Users Browsing this Thread

There are currently 8 users browsing this thread. (0 members and 8 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
  •