Results 1 to 3 of 3

Thread: WSUS SP2 Requirest Updated Report Viewer

  1. #1
    Join Date
    Jul 2004
    Posts
    128

    WSUS SP2 Requirest Updated Report Viewer

    Hi, I just came here to share a small info about WSUS SP2 Requirest Updated Report Viewer. I am running SBS 2003 and recently I installed both SP and viewer on the same as well as my Vista workstation. Installation went fine with no reboot required. As soon as the servers install finishes, configuration wizard starts. Don’t panic and just cancel it. Just remember that while installing WSUS 3.0 SP2, you will need to upgrade to the newest version of the report viewer.

    You can get more info about the same here: Microsoft Report Viewer Redistributable 2008 http://www.microsoft.com/downloads/d...f-416d75a1b9ef

  2. #2
    Join Date
    Jan 2006
    Posts
    278

    RE: WSUS SP2 Requirest Updated Report Viewer

    Hi Dave,

    Thanks for your post and sharing. : )

    Best regards,

  3. #3
    Join Date
    Jul 2004
    Posts
    128

    Re: WSUS SP2 Requirest Updated Report Viewer

    You are welcome. I found something new. Outlook spell checks the subject line, but apparently Windows Mail doesn't. Something worth knowing as my eyesight worsens with age.

Similar Threads

  1. Replies: 9
    Last Post: 08-09-2011, 10:19 PM
  2. Replies: 5
    Last Post: 02-01-2011, 10:54 AM
  3. WSUS v3 SP2 - Force detect/report/update immediately
    By Cic!cone in forum Server Update Service
    Replies: 6
    Last Post: 19-03-2010, 08:20 PM
  4. wsus clients not contact wsus server error = 0x80244023 and 0x8019
    By Dilbert in forum Server Update Service
    Replies: 3
    Last Post: 06-03-2009, 11:47 PM
  5. Some WSUS-Clients report 0x8024400E
    By pushpendra in forum Server Update Service
    Replies: 5
    Last Post: 10-07-2008, 06:54 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,632,105.96017 seconds with 17 queries