Hallo

i install WSUS in server 2012 in port 8530 .

The installation was successful
I tried to get through the browser address server http://localhost:8530/
And I get an error This page can’t be displayed

How do I address the problem of the message.

thanks

אם תגובתי פתרה את בעייתך - לחץ/י, על "סמן כתשובה" ליד סימן ה V הירוק.

Hi,

I'm trying to pull a report on recently approved updates. I have a feeling I'm making a mistake, but for some reason I can't pull a report that shows only updates I updates approved last week.

Any suggestions or advice welcome.

Thanks.

Windows server has been running without issues up until this weekend: Two updates were installed; KB3020370 April 25 & KB3048761 April 26

From looking at the logs, it seems that the server started its infinite reboot loop April 25th.  I want to be able to see what is triggering the windows request to reboot. The two KBs mentioned above show as install successfully; so I don't think they are the culprit to the infinite reboot. But I am out of thoughts on how to proceed further in troubleshooting this issue.

Any thoughts would be greatly appreciated!

Robstg

Please  advise me what could be reasons for this issue and how to resolve it.   because of this  client is  not able to scan and  retreive updates against SUP and SCEP Defintion is not getting updated. a few set of servers are facing this issue. Another set of servers( sccm client is working fine against same SUPs.

Hi All,

I'm having an issue where all Windows 8.1 clients are downloading updates just not reporting back into my console. This seems to be happening since I upgraded to Windows Server 2012R2 (from 2008R2) and created a new WSUS implementation.

The Windows Update Fix-It does fix the issue but this is happening on 50+ pcs and I really need to be able to silently deploy a fix to them.  I'd also like to know what caused it so it doesn't happen again. I do have 1 or 2 Windows 7 machines this happens on, but 99% is on Windows 8.1. I've tried manually fixing based on the Fix-It findings but nothing I have done so far has worked.

Does anyone have any ideas where I should start?

Here are the Fix-It Issues Found:

1. Service Registration is missing or corrupt.

       Reset service registration

2. Windows Update erroe 0x8007000D (2015-04-20-T-09_02_15A)

       Resetting Windows Update data store

3. Problem installing recent updates

       Repair Windows Update

I believe #3 is caused because I use WPP to publish Adobe Flash Player. I do not have my 400+ PCs segregated by OS, rather by departments. So Win 8 machines get Adobe Flash Player WPP updates and constantly fail. I have thought this might be an issue.

We have seen many people struggling with migration from WSUS 3.2 to WSUS 6. Here is a guide to follow:Migrate Windows Server Update Services to Windows Server 2012.

In this article, we introduce another method to do the migration. In brief, this method uses WSUS hierarchy. We setup the new server as a downstream server in replica mode. Once metadata and update file are synchronized, we make it an upstream server and customize it with the settings we need.

1. Apply KB2734608

KB2734608 enables servers that are running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012.

Figure 1

Figure 2-4 show the current status of the WSUS 3.2 Server.

Figure 2

Figure 3

Figure 4

2. Setup the new WSUS server and configure it the downstream server

Firstly, please install the WSUS server role on Windows Server 2012 R2. In the configuration wizard, set it as the downstream server of WSUS 3.2 server in replica mode. During the synchronization, metadata, update files will be downloaded, and we don’t need to export and import them manually. (Figure 5)

Figure 5: WSUS post installation—Replica mode

3. Configure WSUS client settings

After configure the WSUS server, we need to point WSUS clients to the new server.

Note: The default ports of new WSUS server are 8530 and 8531.

For domain-joined clients, we can modify the WSUS related GPOs to point clients to the new server.

For non-domain joined clients, we can change the WUStatusServerregistry key. (Don’t forget to backup the registry before editing). (Figure 6)

The location is HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\

Figure 6

Then, run command: Wuauclt /resetauthentication /detectnow /reportnow. (Figure 7)

Figure 7

Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Getting this error in wsus on 2012. I cannot download any updates. 

any idea?

Log Name:      Application
Source:        Windows Server Update Services
Date:          7/1/2014 7:26:57 PM
Event ID:      12072
Task Category: 9
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      wsus2012
Description:
The WSUS content directory is not accessible.
System.IO.IOException: The device is not ready.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at System.IO.FileInfo.Open(FileMode mode, FileAccess access, FileShare share)
   at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Server Update Services" />
    <EventID Qualifiers="0">12072</EventID>
    <Level>2</Level>
    <Task>9</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-02T02:26:57.000000000Z" />
    <EventRecordID>485447</EventRecordID>
    <Channel>Application</Channel>
    <Computer>wsus2012/Computer>
    <Security />
  </System>
  <EventData>
    <Data>The WSUS content directory is not accessible.
System.IO.IOException: The device is not ready.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at System.IO.FileInfo.Open(FileMode mode, FileAccess access, FileShare share)
   at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)</Data>
  </EventData>
</Event>

I have a single WSUS server (version 3.2.7600.226) running on a Windows 2008 R2 VM.  Devices are happily talking to it and downloading some patches, but the server says that there are nearly 200 more patches to deploy to these devices.  The patches have been approved but the system says they failed to download.  On investigation we are getting the following events at regular intervals 13042, 10023, 12002, 12012, 12032, 12022, 12042 & 12052.  I have searched for fixes to these various but they all require WSUSUTIL.EXE CHECKHEALTH to be run and it doesn't work on our server it returns a FATAL ERROR: Unable to contact the WSUS Service. 

The service is installed and I can run WSUSUTIL for other tasks.  Does anyone have any ideas where I can go next?

This is not an issue/question, I'm just posting something which may help others in doing WSUS reporting tasks.  I hope you will find this information useful and feel free to enhance it any way you can by sharing it with others.

.

WSUS has always lacked a few things with its built-in reporting capabilities which by the time you are patching end-points above double digits within a not-so-flat design, it can become a major time waster.  One thing I've always wanted in the Computer reports in WSUS was to see a breakdown of system compliancy of all servers/desktops by having an additional column which would reflect the computer groups and containers that I've used to organize my WSUS hierarchy.

.

I'm specifically referring to the Computer Tabular Status report.  This would eliminate the need to run a separate report for each computer group and then grouping them all together manually afterwards.  Using this code, I can now view all the computer groups and the systems contained within them in a single view.

.

To do this I've scoured around the net and by spending some time in SQL, I've written a basic SQL query which you can issue against your WSUS database either through SQL Management Studio or just by wrapping the code into a script and using SQLCMD.exe

.

In my specific case, I'm using the basic Windows Internal DB but if you just re-work some of the table paths it can be used against a full SQL DB install as well.  This was done under WSUS 3.0, I'm not sure if Win 2012 WSUS has enhanced reporting or not but I know WSUS 3.0 is still very common.

SELECT tbTargetGroup.Name, tbComputerTarget.FullDomainName, tbComputerTarget.IPAddress, tbComputerSummaryForMicrosoftUpdates.Installed, tbComputerSummaryForMicrosoftUpdates.NotInstalled, tbComputerSummaryForMicrosoftUpdates.InstalledPendingReboot, tbComputerSummaryForMicrosoftUpdates.Downloaded, tbComputerSummaryForMicrosoftUpdates.Failed, tbComputerSummaryForMicrosoftUpdates.Unknown
FROM SUSDB.dbo.tbComputerTarget tbComputerTarget, SUSDB.dbo.tbTargetGroup tbTargetGroup, SUSDB.dbo.tbTargetInTargetGroup tbTargetInTargetGroup, SUSDB.dbo.tbComputerSummaryForMicrosoftUpdates
WHERE tbTargetInTargetGroup.TargetGroupID = tbTargetGroup.TargetGroupID AND tbTargetInTargetGroup.TargetID = tbComputerTarget.TargetID AND tbComputerTarget.TargetID = tbComputerSummaryForMicrosoftUpdates.TargetID AND tbTargetGroup.Name != 'Unassigned Computers'
ORDER BY tbTargetGroup.Name ASC

The above block of code will basically show several essential columns of information about the systems being managed by WSUS, such as name, IP, etc. but most importantly will group them by using the first column on the left as how you've grouped them into computer containers in your WSUS console.  You can of course choose to remove whatever columns you don't need or include other columns from different tables if you want, but the main thing is in the WHERE line where the reference between group names and group GUIDs are established and by creating a relationship between computers and their respective groups.

.

You can copy the outpt into Excel or do wherever else you want to manipulate it further.  I've for example used some additional SQL queries and Excel formulas to show the percentage compliancy which is also not presented in the built-it reports but is visible in the WSUS console itself.

Enjoy,

Armin

Hi,
I'm currently experiencing a strange issue with updates installed on clients with WSUS.
Currently WSUS setting is "3-Auto download and notify for install" so when users poweroff the PC, the "Install Updates and Shut Down" message appear.The problem is that after reboot, the Updates process fails and the installation process enters in a "loop".
If I manually install upadates I have no problems.
The only difference seems to be that by leaving Windows installing updates (WSUS policy), the user is logged off and then the update process starts, while if I manually install updates the user is still logged on during instalaltion.

Since the error is the "classic" 0x80070005,Access Denied it seems to be a permission issue.

Before posting hundred lines of logs could someone tell me which user context is involved during the 2 ways to install updates?

Many thanks and best regards,

Andrea

After installing Server 2012 Standard on ESX 5.1 I completed all available Windows Updates and proceeded to add the WSUS role.  I chose the default WID database and the role addition was seemingly successful.  Unfortunately, the Post-deployment Configuration failed.  A log file had been created in the AppData\Local\Temp folder but at initial glance it seemed to imply that my error was likely due to skipping a step during installation via PowerShell.  However, I didn't install using PowerShell and I set off to surf the Internets for clues on resolving this issue.  I searched about a dozen forums that with similar, but different issues until a comment by Lawrence Garvin (http://social.technet.microsoft.com/profile/lawrence%20garvin/?ws=usercard-inline) convinced me to go back and look at my log. 

2013-07-23 11:03:18  Postinstall started
2013-07-23 11:03:18  Detected role services: Api, UI, WidDatabase, Services
2013-07-23 11:03:18  Start: LoadSettingsFromXml
2013-07-23 11:03:18  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2013-07-23 11:03:18  Value is true
2013-07-23 11:03:18  End: GetConfigValue
2013-07-23 11:03:18  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2013-07-23 11:03:18  Config file did not contain a value "ContentDirectory"
2013-07-23 11:03:18  Microsoft.UpdateServices.Administration.CommandException: A required configuration value was not found in the system. This is usually caused by installing WSUS through PowerShell and not specifying a configuration file. Review the article Managing WSUS Using PowerShell at TechNet Library (http://go.microsoft.com/fwlink/?LinkId=235499) for more information on the recommended steps to perform WSUS installation using PowerShell.
   at Microsoft.UpdateServices.Administration.PostInstall.GetConfigValue(String filename, String item)
   at Microsoft.UpdateServices.Administration.PostInstall.LoadSettingsFromXml()
   at Microsoft.UpdateServices.Administration.PostInstall.Initalize(Parameters parameters)
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: A required configuration value was not found in the system. This is usually caused by installing WSUS through PowerShell and not specifying a configuration file. Review the article Managing WSUS Using PowerShell at TechNet Library (http://go.microsoft.com/fwlink/?LinkId=235499) for more information on the recommended steps to perform WSUS installation using PowerShell.

Upon closer inspection the specifics of my error were right there for me, I just had to look at it long enough to decipher the details.  What I now read is that Post-deployment configuration finds a file called UpdateServices-Services.xml (I found it in Windows\System32\ServerManager\ComponentConfiguration\).  It determines that ContentLocal=True which correctly indicates that my updates are to be stored locally.  It proceeds to inquire about the ContentDirectory, but comes back without a value.  Here are my UpdateServices-Services.xml file contents

<?xml version="1.0" encoding="utf-16"?><INSTANCE CLASSNAME="ServerComponent_UpdateServices_Services"><PROPERTY NAME="ContentDirectory" TYPE="string"></PROPERTY><PROPERTY NAME="ContentLocal" TYPE="boolean"><VALUE>true</VALUE></PROPERTY></INSTANCE>

I can see that the ContentLocal property did indeed have the value true, but the ContentDirectory property did not have a value.  I now needed to figure out if a String value could be specified in the same way a Boolean value was, or if it needed quotes around it, or was supposed to be specified more like an attribute (learned about that somewhere along the way).  I couldn't find any conclusive websites, and I didn't want to just try it for fear of the Post-deployment configuration running with an invalid ContentDirectory.  Once again I returned to my log file and searched for answers at the http://go.microsoft.com/fwlink/?LinkId=235499 that was indicated.  I didn't find any exact matches, but eventually I found a sample .xml file that specified a string value.  It specified it as <VALUE>string</VALUE> with no brackets, so I knew to specify mine as <VALUE>C:\LocalMSUpdateCache</VALUE> and saved it.  My UpdateServices-Services.xml now looks like this:

<?xml version="1.0" encoding="utf-16"?><INSTANCE CLASSNAME="ServerComponent_UpdateServices_Services"><PROPERTY NAME="ContentDirectory" TYPE="string"><VALUE>C:\LocalMSUpdateCache</VALUE></PROPERTY><PROPERTY NAME="ContentLocal" TYPE="boolean"><VALUE>true</VALUE></PROPERTY></INSTANCE>

I returned to Server Manager -> WSUS and re-attempted the Postdeployment configuration.  It completed successfully!

I'm glad that my fix was relatively simple and that Lawrence was particular about the details of the log file. 

1. My exact error isn't always going to be documented

2. Just because the log file looks unintelligible (I have thus far avoided both powershell and xml), doesn't mean it's useless.

Good luck to anyone with a similar issue.  You too may be able to figure it out yourself.

Hi all i have a problem with WSUS.

I have a number of PCs not porting to WSUS and others working fine 

I am receiving an error code 800b0001 when trying to search for updates on these PCs 

Is there any possible solution to solve this issue ??

Hi,

I have written a tool to parse WSUS update file, it parses a single update each time. But my tool takes a huge amount of memory for some updates, as they are large in size. For a update on windows8, the metadata size of a update is 18Mb. I wanted to know if there some maximum size limit on the size of the metadata, for a single update.

Thanks,

Suraj

Hi All,

I've recently migrated WSUS servers and everything has come intact apart from the grouping. The groups have come over but all the computers are showing under 'Unassigned Computers'.

I've manually removed and added a number of computers but it doesn't show any computers.

Thanks

Standard problem with WSUS Cleanup Wizard timing out without removing any unnecessary updates. SBS2K8. WSUS 3. 6000+ unnecessary updates awaiting approval. Huge database. Unresponsive SQL server. Lot of people have this problem:
http://social.technet.microsoft.com/Forums/en-US/9724778f-c1a0-4d24-82e4-8b2d054257d6/wsus-hangs-on-cleanup-wizard-for-unused-updates-then-disconnects-from-console?forum=winserverwsus

Drives are regularly defragged in the background. Not gonna shut down the server and have down time just to fix this.

Tried the reindexing script from
http://technet.microsoft.com/en-us/library/dd939795(WS.10).aspx
, (don't copy the command line, it has weird characters in it, just type it in manually.) and it completes but it didn't improve anything.

Found this:
http://wsus.codeplex.com/releases/view/17612
and it also times out.

Found this comment:
For anyone who is getting Timeout Expired with obsolete updates. I have a solution! Use server name : "
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
" to connect with SQL managment studio. Once connected manually run "
exec spGetObsoleteUpdatesToCleanup
". This will return a list of obsolete ID's. For each one run "
exec spDeleteUpdate @localUpdateID=000000
", where 000000 is the ID. For myself I found the first ID in the list took a full 37 minutes to delete and then after that I could run the cleanup through the GUI as per usual.

by jjdacl on Apr 23 at 12:55 PM 

Found that you actually need to do:
USE SUSDB
GO
exec spGetObsoleteUpdatesToCleanup

And to connect in the first place, I had to hit Options, and select named pipe from the middle pull down. 

First delete took 6 minutes and memory has spiked up to almost 15GB in use out of 16GB physical. But the WSUS console (Update Services) still shows the same number of old updates. Failure? I don't think so: I'm running the cleanup wizard again and so far it isn't timing out... It has run over night, and has made some progress; the bar has moved perhaps 5%. 

So... My take is that the SQL server causes this problem when there is to much data, because the indexes are poorly designed (not because the indexes need to be re-indexed) causing the first query to time out, which causes the cleanup to fail. Once you get past that first deletion, and have everything loaded into memory, the cleanup tool can stay connected long enough to delete each unneeded update.

Next step will be to find a command line method, such as:
http://wsus.codeplex.com/releases/view/17612
and put it into the task scheduler like Microsoft should have done at the beginning to keep this from getting out of hand.

P.S. Lawrence Garvin, please do NOT reply to this; I have no need of your arrogance.

We had WSUS working until we decided to install Trend Micro Control Manager on it. Soon after we realized it broke WSUS. Since then we've uninstalled all traces of both applications as much as possible. Now WSUS won't complete installation. I've searched many different forums topics and couldn't find a solution that matched my particular issue yet. The error log looks fine except for the last portion that looks like this... 

Can anyone help me pinpoint what the problem might be?

Hi,

We have 9 MS Office 2010 updates released in April 14th 2015, that are failing to install on a Windows 7 machine. WindowsUpdate.log file shows and error message as "Windows failed to install the following update with error 0x80070656" , for all the 9 updates.

Tried to restart the system and install updates again, which failed.

Please suggest how to proceed on this.

Regards, Lorin Davis

Dear Exprt,

some of the client not getting patch via SCCM 2007 and when look network trace those client receive HTTP/1.1 500 internal server error and and on Server logs below writen for client IP.

2015-04-29 18:27:22 10.32.41.1 HEAD /selfupdate/WSUS3/x86/Win7SP1/wsus3setup.cab 1504291827 8530 - 192.168.1.45 Windows-Update-Agent 200 0 0 202

need your support to resolve.

Support@Mytechnet.me