Formatted wsus
Hi,
My former wsus server crashed.
I had no chance to export settings, groups etc....
I installed WSUS 8 as a service from Windows 2012 server.
I did setup the server, and services
now my computers are not visible in the wsus management console.
How to reconnect the clients?
Yes, i used the same servername, same ip as the old one.
i deploy current wsus server settings via group policy.
please have a look on the client log file :
2014-01-30 09:26:53:805
520 f60
WS WARNING: Nws Failure: errorCode=0x803d000d
2014-01-30 09:26:53:814
520 f60
WS WARNING: There was an error communicating with the endpoint at 'http://MSCSRV1/ClientWebService/client.asmx'.
2014-01-30 09:26:53:814
520 f60
WS WARNING: The server returned HTTP status code '404 (0x194)' with text 'Not Found'.
2014-01-30 09:26:53:814
520 f60
WS WARNING: The requested resource was not found.
2014-01-30 09:26:53:814
520 f60
WS WARNING: Web service call failed with hr = 80244019.
2014-01-30 09:26:53:814
520 f60
WS WARNING: Current service auth scheme='None'.
2014-01-30 09:26:53:814
520 f60
WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
2014-01-30 09:26:53:814
520 f60
WS FATAL: OnCallFailure(hrCall, m_error) failed with hr=0x80244019
2014-01-30 09:26:53:817
520 f60
PT WARNING: PTError: 0x80244019
2014-01-30 09:26:53:817
520 f60
PT WARNING: GetConfig_WithRecovery failed: 0x80244019
2014-01-30 09:26:53:817
520 f60
PT WARNING: RefreshConfig failed: 0x80244019
2014-01-30 09:26:53:817
520 f60
PT WARNING: RefreshPTState failed: 0x80244019
2014-01-30 09:26:53:817
520 f60
PT WARNING: Sync of Updates: 0x80244019
2014-01-30 09:26:53:817
520 f60
PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
2014-01-30 09:26:53:817
520 f60
Agent * WARNING: Failed to synchronize, error = 0x80244019
2014-01-30 09:26:53:825
520 f60
Agent * WARNING: Exit code = 0x80244019
Similar Messages
-
WSUS service failure and uninstall error 0x80070643
Hello
I recently had a drive fail in a RAID 1 array on a Windows Server 2008 Standard SP2 domain controller. The drive was replaced and the array successfully rebuilt the drive. Our domain comprises a Win2k8 DC (which WSUS is installed on), a W2k3 DC, a W2k8 Storage
Server and various W2k, Win XP, Vista and W7 clients.
WSUS3 SP2 is installed on this computer and had been working fine. After the drive was rebuilt WSUS stopped working. WSUS is organised as follows:
The drive is divided into 3 partitions. C: contains the program files, D: contains the WSUS database and update files. E: is a system recovery partition.
After the drive was rebuilt I had a problem connecting to the WSUS console. I am logged on using the domain administrator account. I restarted the server last night in the hope that it would solve this issue. After restarting, the problem persists. When
I start Windows Server Update Services from Administrative Tools the centre pane shows a large red X and 'Error: Connection Error'. The option to 'Reset Server Node' results in the same error. The error, available from 'Copy Error to Clipboard' is:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
System.IO.IOException -- The handshake failed due to an unexpected packet format.
Source
System
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **
System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)
The event logs show that the Update Services service started 7mins after the server was restarted. This is immediately followed by an event stating the Windows Update service had started. If fails soon after and is restared automatically twice to try to
recover from the failure. 12 hours after the restart the Update Services service is still not running. It is set to Automatic (Delayed Start). The service is set to logon as 'Network Service'. The service can be manually started, but 'Resert Server Node' again
results in the same error. After 4mins the service will stop. Event 7034 is logged:
Log Name: System
Source: Service Control Manager
Date: 31/08/2011 09:05:50
Event ID: 7034
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Phobos.htlincs.local
Description:
The Update Services service terminated unexpectedly. It has done this 4 time(s).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7034</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-08-31T08:05:50.000Z" />
<EventRecordID>230471</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Phobos.htlincs.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Update Services</Data>
<Data Name="param2">4</Data>
</EventData>
</Event>
IIS and SQL are running fine as far as I am aware. I also have Sophos Enterprise Console installed which uses SQL to store it's data and that is working fine.
After a bit of searching around the 'net I thought the easiest solution would be to uninstall WSUS, leave the database and update files in place and then re-install. I ran the uninstallation procedure from the Server Manager, but because the service is not
running, and even after starting the service, uninstallation fails:
Windows Server Update Services: Removal failed
Error: Attempt to un-install Windows Server Update Services failed with error code 0x80070643. Fatal error during installation
I saw a reference to the online article located here:
http://blogs.technet.com/b/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx but the article states it is out of date and I did not want to make a bad situation worse by following the instructions.
Can anyone help me with this, please. Ideally, I would like to be able to keep the updates as downloading them again will consume a substantial amount of our monthly allowance. However, if the best thing is to remove the entire installation, then I will
ahppily go with that, too.
Thanks.I'm experiencing this issue, but haven't been able to resolve it with the steps in Lawrence's post (and, another thanks from me for another detailed post from Lawrence!)
It's a 2008 box which had a relatively new WSUS install that just stopped working - not sure why. Unable to figure out why it had stopped, I tried to Remove the WSUS role, but that failed with the error above.
During the manual uninstall steps above...
(1) Using Windows Installer Cleanup Utility only showed the Windows Internal Database, not WSUS. I removed
that.
(2) Removed %ProgramFiles%\Update
Services - other resources not present
Reinstall has now failed with this error:
Windows Server Update Services 3.0 SP2 could not install Windows Internal Database. For more information, see the Setup log "C:\Users\NAME~1.ADM\AppData\Local\Temp\WSUSSetup.log".
2012-10-23 20:57:53 Success MWUSSetup Detected that setup was launched through Server Manager
2012-10-23 20:57:54 Success MWUSSetup Validating pre-requisites...
2012-10-23 20:57:54 Error MWUSSetup Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
2012-10-23 20:57:54 Error MWUSSetup WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2012-10-23 20:57:57 Success MWUSSetup Incompatible version of ReportViewer installed. Required ReportViewer version: 9.
2012-10-23 20:57:57 Success MWUSSetup Incompatible version of ReportViewer installed. Required ReportViewer version: 9.
2012-10-23 20:58:25 Success MWUSSetup Initializing installation details
2012-10-23 20:58:25 Success MWUSSetup Skipping Asp.Net install since not running on win2k3...
2012-10-23 20:58:25 Success MWUSSetup Installing wYukon using ocsetup
2012-10-23 20:58:25 Success MWUSSetup Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
2012-10-23 20:58:49 Error MWUSSetup The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
2012-10-23 20:58:49 Error MWUSSetup ExecCmd failed (Error 0x80070643: Fatal error during installation.)
2012-10-23 20:58:49 Error MWUSSetup Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error during installation.)
2012-10-23 20:58:49 Error MWUSSetup CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
2012-10-23 20:58:49 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
Would anyone on the thread have suggestions for what I might be able to do, to wipe the slate clean with the Internal
Database on this box?
The WID is not used for anything else, but there is other production software installed, (using SQL - not relevant, just
mentioning) and reinstalling the OS is not an option. -
Server 2012 R2 cannot update from 2008 R2 WSUS server
Our WSUS server is on a 2008 R2 VM. Updates for all 2008 R2 and lower servers, and Windows 7 clients work fine. I have one Server 2012 R2 in production and it cannot check for updates. It gets 800b0001 as the error code. I can
click on check for updates from Microsoft, then it does reach out to the Internet, download and install updates.
I also tried from my Win 8.1 laptop and I get error 8024402C. Any idea's?I found in another thread the fix.
In regedit go to HKLM\Software\Microsoft\Update Services\Server\Setup and change "wYukonInstalled"
from a 1 to a 0.
Installer succeeds.
However now the Update Services console does not work. I get a connection error.
It's one thing after another with these things. I don't understand why Microsoft can't ever make something simple. IISReset did not cure this either.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
System.IO.IOException -- The handshake failed due to an unexpected packet format.
Source
System
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **
System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools() -
WSUS reinstall on 2012 SCCM server post-installation task fails to run/finish
I had to re-install WSUS on a 2012 R2 SCCM server (Windows 2012), and am running into several issues re-installing. It may help to point out that the SCCM SQL server is remote, so this isn't a WSUS / SQL 2012 issue.
The sticky post at the top of the WSUS forum has helpful troubleshooting information, and I have tried going through this as well as many other threads on this very topic of re-installing WSUS.
1. Roles for WSUS and WID were removed successfully. The WSUS Website was manually deleted from IIS. As this is a SCCM server, removing the IIS role is not an option.
2. I removed the existing WID database files for SUSDB
3. After rebooting, I verified registry keys were gone, system files were cleaned up, and deleted the program files\update services directory
4. This isn't a permission issue, as I have clearly installed this before on this server.
5. Registry keys, system files, and susdb files no longer exist, and the server has rebooted cleanly.
6. I am able to add the WSUS role selecting WID, and this installs WID without any errors. At this point, simply clicking the post installation task fails, generates an empty .tmp file in my %appdata%\temp folder, and exits the MMC.
7. This file is blank. Absolutely empty, so I couldn't really troubleshoot any post installation tasks.
8. Further investigation shows that the 'C:\Program Files\Update Services\Tools\' directory is gone, and isn't being
generated.
9. Ok... DISM /online /Cleanup-Image /Scanhealth didn't return any issues, so I copied the wsusutil out of the windows\WinSxS directory.
10. Yey! wsusutil postinstall runs, but bombs out on the IIS portion. It generated the DB without an issue, but results
in an IIS generation error. So, I installed WSUS on a clean 2012 install, then copied over the program files\updateServices directory to reclaim the missing files.
The log files show --
2013-12-06 10:30:34 Configuring IIS...
2013-12-06 10:30:35 Start: ConfigureWebsite
2013-12-06 10:30:36 Configuring website on port 8530
2013-12-06 10:30:39 System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Microsoft.UpdateServices.Administration.UseCustomWebSite.ExecuteIisCustomAction(String arguments)
at Microsoft.UpdateServices.Administration.UseCustomWebSite.Install(Int32 portNumber)
at Microsoft.UpdateServices.Administration.UseCustomWebSite.InstallAndConfigure(IisConfiguration& iisConfiguration, Int32 newPortNumber)
at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)
at Microsoft.UpdateServices.Administration.PostInstall.Run()
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
... ok - tripple checked that network service has permissions to .net and windows\temp folders.
netstat -a doesn't show anything running on port 8530 ( in case this was some weird port check in use)
Which goes back to the missing directory problem -- further net searches show that this is a reoccurring issue for some OOBE... sfc /verifyonly shows ... nothing.
What is left to be done at this point? The missing folders from the program directory seems to be a problem for some with some users right out of the box. I have read many other threads where users just formatted and started over. Not exactly a solution
- any help out there on this issue? Any suggestions to determine what file is missing, or generating the IIS issues?Part of the post install tasks wanted to download some items including the tools folder.
Can you expand on this please. The WSUS post-install tasks do not download anything, except what is acquired during the initial synchronization with Microsoft.
Because of my group policy the WSUS server was trying to download the updates from itself even though it was not setup yet.
What update(s) was the WSUS server trying to "download"?
In fact, if the WSUS Server was not setup yet (but you already had a GPO in place), then the first issue here was performing deployment steps out of order.
But still.... except for the actual installation binaries for the WSUS Server Role on a WS2008SP2/WS2008R2 system, there's nothing the WSUS server needs to get from either Windows Update or a WSUS server. This scenario is actually discussed hundreds of times
in this forum, but complicating matters, this thread isn't about installing WSUS V3.2 on a WS2008SP2/WS2008R2 system, it's about installing WSUS v65 on a WS2012 system, so I'm a bit confused as to what the actual installation environment is that we're discussing.
I changed the WSUS server to get it's windows updates from Microsoft and then the post install task succeeded.
I'd really like to get some more details about what exactly in the "post-install task" was dependent upon content from WU/WSUS.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
For no reason the MMC for WSUS is not connectiing to the server
All,
I rebooted the WSUS server after a windows update and now I cannot connect to the WSUS server. I get error: connection error. I've reviewed all posts for this issue, but none of them help. This is ridiculous as I finally got it working
and once again, right after an update, it screws up!!! What is going on?
Here's the details of the error when copied to clipboard:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
System.IO.IOException -- The handshake failed due to an unexpected packet format.
Source
System
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **
System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()
It was working perfectly before the update. Please help!!
Lee Feldman
Feldman Consulting Co.
Lee Feldman SMB ConsultantThank you for your input. At least you're not like Lawrence giving poor information.
Hmmmm.. having been working with this product for eight years now, while sometimes I make an erroneous statement, it rarely happens these days.
In this case, it is Yan Li who has given you incomplete information. In addition to the split-server scenario not supporting the
database on a Terminal Services server (which is the information provided by Yan, but not really relevant to this conversation), it is also true that WSUS has
never been supported on a Terminal Services server.
This was posted to the Release Notes, historically, but due to several omissions in the WSUS v3 SP2 Release Notes, does not appear in that document. (That is to say, the SP2 release notes were exclusive to the SP2 feature set, and were not inclusive of the
RTM and SP1 limitations and issues.)
Here is the entry from the
WSUS v3 Service Pack 1 Release Notes:
WSUS 3.0 SP1 is not supported on servers running Terminal Services
Although WSUS 3.0 SP1 may still run on servers running Terminal Services, doing so is not supported or recommended. WSUS 3.0 SP1 will not run on a server running Terminal Services in configurations using remote SQL Server implementations. Because all remote
custom actions (including installation) on a Terminal Services license server will be run as the system account, and the server's system account may not have permissions on the remote SQL Server, the installation may fail.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
SCCM/WSUS issue after importing March CSA patch bundle
Hi, I am having an issue with security patch deployment since Tuesday night. Debugging is ongoing. I am running SCCM 2012 CU2.
Coincidentally, the problem appeared shortly after importing the March XP CSA (Custom Support Agreement) patch bundle into SCCM. From the client end, WUAHandler.log reported continuous failures/retries. On lower-end machines, system performance
became very poor. From the server end, starting up the Windows Server Update Services mmc (yes, I know you're not supposed to be doing anything in here, which I'm not) results in a connection error. The detailed error message is shown further down.
It was difficult to get the client machines to stop "thrashing" per WUAHandler.log. It wasn't until I de-installed/re-installed WSUS and ASP.NET that things quieted down yesterday afternoon. All appeared to be stable until this morning
when I re-added "Windows XP Custom Support" under the SUP Component Properties tab, imported the CSA bundle info, initiated a CAB synchronization from Microsoft, and re-enabled Software Updates on the clients.
Again, I would get the error when starting up the Windows Server Update Services mmc.
I am doing everything again, but this time one step at a time. My working theory is that there is some kind of corruption caused by the CSA import (this worked just fine up until Feb.). A few hours ago, Microsoft published a new CSA
patch bundle because a patch was apparently forgotten. Is it possible that there was some kind of corruption included with the original bundle published on Tuesday?
I will post what I find as a result of my debugging.
Thanks,
Nick.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
System.IO.IOException -- The handshake failed due to an unexpected packet format.
Source
System
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **
System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)Yes, WCM.log showed the same 503 error starting on the Wednesday morning at 2:53am, and I also noticed wsuspool had stopped. My most noticeable symptom was the thrashing of wuahandler.log on the clients, causing poor system performance on machines with 2gb
of memory. Multiple de-installs/re-installs of WSUS failed to clear the issue until we increased the memory setting in IIS.
Nick
WCM.log:
System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String
ServerName, Boolean UseSSL, Int32 PortNumber) $$<SMS_WSUS_CONFIGURATION_MANAGER><03-11-2015 02:53:26.225+240><thread=30872 (0x7898)>
Remote configuration failed on WSUS Server.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-11-2015 02:53:26.226+240><thread=30872 (0x7898)> -
MMC crashes when running WSUS Post Install tasks
After an upgrade from 2008 R2 to 2012 R2 I had issues with WSUS not running. I have removed roles for WSUS, IIS and the WID, renamed the WID directory in C;\Windows to .old, reboot and reinstall but I still have the same issue. When trying to run the post
installation tasks it prompts for the location to store the updates but almost as soon as Run is clicked I receive an error that the microsoft Management Console has stopped working with the following details.
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: mmc.exe
Problem Signature 02: 6.3.9600.16384
Problem Signature 03: 5215ef8f
Problem Signature 04: System
Problem Signature 05: 4.0.30319.34003
Problem Signature 06: 522ec39f
Problem Signature 07: 3fec
Problem Signature 08: 3b8
Problem Signature 09: System.ComponentModel.Win32
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 2057
Additional Information 1: b376
Additional Information 2: b376ba95bedbd518328ed0407772d20c
Additional Information 3: 2cdd
Additional Information 4: 2cdd6573ca3a99b682060228c5ceb1c2
At the same time two errors are logged in the Application log,
ID1026 .NET Runtime
Application: mmc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
Stack:
at System.Diagnostics.Process.StartWithCreateProcess(System.Diagnostics.ProcessStartInfo)
at Microsoft.UpdateServices.UI.SnapIn.Dialogs.PostInstallDialog.RunPostInstall(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
and Event ID 1000 Application Error
Faulting application name: mmc.exe, version: 6.3.9600.16384, time stamp: 0x5215ef8f
Faulting module name: KERNELBASE.dll, version: 6.3.9600.16408, time stamp: 0x523d557d
Exception code: 0xe0434352
Fault offset: 0x000000000000ab78
Faulting process id: 0x196c
Faulting application start time: 0x01d030500ca78295
Faulting application path: C:\Windows\system32\mmc.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 4b72991e-9c43-11e4-80c4-f01fafe08a8b
Faulting package full name:
Faulting package-relative application ID:
I've tried running the .NET verification tool on all versions of .NET and all verify ok. I have also tried uninstalling .Net 3.5 and reinstalling. Unfortunately I can't reinstall .NET4.5 as this is the only DC and I can't have downtime to rebuild from
scratch. Any ideas?
Many thanks,
BazAfter an upgrade from 2008 R2 to 2012 R2
You *cannot* upgrade a WSUS server from WS2008R2 to WS2012R2, so could you please clarify what you actually did do?
Otherwise, given the error messages, I'm inclined to think you really did *Upgrade* the WS2008R2 to WS2012R2 server with the WSUS role installed, and if so, then you're basically going to have to reformat and reinstall WS2012R2 from scratch.
This scenario is plainly documented in the
WS2012R2/WSUS v6 documentation:
New and changed functionality
Warning
Upgrade from any version of Windows Server that supports WSUS 3.2 to Windows Server® 2012 R2 requires that you first uninstall WSUS 3.2.
In Windows Server 2012, upgrading from any version of Windows Server with WSUS 3.2 installed is blocked during the installation process if WSUS 3.2 is detected, and you are prompted to first uninstall Windows Server Update Services prior to upgrading Windows
Server 2012.
However, because of changes in Windows Server 2012 R2, when upgrading from any version of Windows Server and WSUS 3.2 to Windows Server 2012 R2, the installation is not blocked. Failure to uninstall WSUS 3.2 prior to performing a Windows Server 2012 R2 upgrade
will cause the post installation tasks for WSUS in Windows Server 2012 R2 to fail. In this case, the only known corrective measure is to format the hard drive and reinstall Windows Server 2012 R2.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
Control Windows 8.1 and WS2012 R2 "Update 1" and followings through WSUS?
Hello all,
Is there a way of identifying and stop through WSUS the new Updates (Update 1, Update 2 and followings) released for Windows 8.1 and WS 2012 R2?: http://blogs.windows.com/bloggingwindows/2014/04/02/windows-8-1-update-important-refinements-to-the-windows-experience/
As far as i know, the are identified as: "Update for Windows", so its impossible to know these are a set of updates similar to a "small" service pack if you don't check the KB number associated.
Due to my environment specs, I only make available Critical and Security updates through WSUS, so clients do not install set of updates such as service packs, which will jeopardize the environment.
These kind of updates are not classified within Updates, Update rollups or anything else, so is there a way of stopping them or at least make them more visible on WSUS (if this makes sense)?
Thanks in advance.Interesting question.... and I'm seeing a whole litany of problems with the above.
First the answer: You simply don't approve the updates. As for identifying the updates, yeah, it's done by KB number. It will take a nominal amount of effort on your part. It's also identified by a uniquely formatted title:
Windows 8.1 Update (KB2919355)
BUT.. since the update was originally released into theSecurity Updates classification six months ago, if you're automatically approving Security Updates, then it's already long gone and already installed.
Second.... not installing "Update 1" is not a choice. It's a
mandatory update. If you've not installed this update (hard to see how that could have happened), then you've not actually deployed any to those systems since June if you've blocked this update ... the cutoff date for deploying "Update 1".
"Update 2" is not a mandatory update, and being as the cited blog is dated April, 2014, it doesn't cover that update at all. This update was released in August 2014, and is identified only as KB2975719 and has the title
Update for Windows 8.1 (KB2975719). It was published into Critical Updates a month ago, so again, if you're automatically approving Critical Updates.. it's long gone and already installed.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
Friends,
I will format a Windows Server 2008
server running WSUS 3.0, then
I will install Windows Server 2008
again and will install WSUS 3.0 again,
do not want to lose WSUS settings and
folders updates.
If I follow the procedure to do the full
backup and restore WSUS folder
in the new folder after reinstalling
WSUS, WSUS this function normally
as before?
I'll follow this tutorial.
http://technet.microsoft.com/pt-br/library/cc720441%
28v = WS.10% 29.aspx
I await response and thank you!
Ivanildo Teixeira GalvãoI will format a Windows Server 2008 server running WSUS 3.0, then I will install Windows Server 2008 again and will install WSUS 3.0 again , do not want to lose WSUS settings and folders updates.
Can you please elaborate more on what this means and/or why you're doing this?
Fundamentally reinstalling WSUS does not require a backup or restore operation -- unless you're planning on trashing the entire operating system installation -- which brings us back to the *WHY* question.
It sounds to me like you're exploring Disaster Recovery scenarios, and if so, I'd suggest that your proposed scenario is not optimal, and involves an excessive amount of unnecessary work.
More importantly, since you're choosing to do this on Windows Server 2008 (also perhaps worthy of a "Why?" question), you need to be acutely aware of the implications of doing a backup on such a server. In WS2008, backups are VOLUME-based only. Which means,
unless you plan to heavily customize the installation environment to separate the WSUS database and content store from the operating system volume, your backup is going to be a Full System Backup -- in which case, reinstalling WSUS would be pointless, as a
Full System Restore would get you the very same WSUS installation back.
Furthermore, customizing the environment by putting the WSUS database and content store on a separate volume means you don't even have to do a backup/restore at all. Format the C: drive, reinstall Windows Server 2008, reinstall the WSUS Role and point it
at the database and content store that still exists on the other volume.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
Run this from power shell: (Be sure and fill in the appropriate values that are in Text#Upstream WSUS server to cleanup and retrieve downstream servers to cleanup$WsusUpstreamServer = ""$UseSSL = $false$PortNumber = $TrialRun = $false#E-mail Configuration$SMTPServer = ""$FromAddress = ""$Recipients = ""$MessageSubject = "WSUS Server Cleanup."#HTML variables referenced during the script for output formatting$sHTMLCellStyle = "`r`n"$sHTMLHeadingStyle = "`r`n"$sHtmlTableStyle = "`r`n"$sHTMLParagraphStyle = "`r`n"$global:MessageBody = "$sHtmlTableStyle $sHTMLHeadingStyle WSUS Server$sHTMLHeadingStyle Parent WSUS Server$sHTMLHeadingStyle WSUS Version$sHTMLHeadingStyle Start$sHTMLHeadingStyle Finish$sHTMLHeadingStyle Superseded Updates Deleted$sHTMLHeadingStyle Expired Updates Declined$sHTMLHeadingStyle Obsolete Updates Deleted...
My WSUS database is messed up, the application event logs on the WSUS server are filled with the following errors.
Source: MSSQL$SQLEXPRESS
Could not allocate space for object 'dbo.tbChangeTracking'.'c0ChangeTracking' in database 'SUSDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
and this one:
CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.
Any ideas how to fix this? It hangs when I try and delete unneeded updates and then crashes the MMC snapin.
This topic first appeared in the Spiceworks Community -
Running WSUS 3.0 SP2, using Windows Internal Database. OS is Server 2008 R2. I experienced the null .cab file issue. I applied KB2828185. Upon reboot and running wsusutil.exe export 'name'.cab 'name'.log, a general error is produced "<ExportError
Message="Error in the application." /></ExportLog>". No event logs.
RRSUse the correct syntax for the updated wsusutil export functionality.
Failing to specify an export file format will continue to try to build the CAB file by default.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
WSUS 3.0 SP2 on Server 2k8 R2 getting Error 364 and 10032
This is a FRESH installation of Server 2008 R2, installed with SP1 (no updates applied from Windows Update - I want this to happen via WSUS)
WSUS 3.0 SP2 FRESH installation from standalone installer.
Installed KB2720211 to correct the issue of clients being unable to communicate with WSUS server.
WSUS installs fine, synchronizes fine, but a number of updates showing "The Microsoft Software License Terms for this update failed to download"
Many other updates report the download failed with REASON: HTTP 404 The requested URL does not exist on the server.
Throughout the last 2 days of researching and investigating these particular errors, I have performed the following steps:
Verify correct permissions for the drive and folders - no change
wsusutil reset - no change
wsusutil checkhealth - Reports WSUS working correctly
Uninstalled and reinstalled WSUS 3.0 in full
Removed server from any and all firewall and ISA devices, turned off the internal Windows Firewall completely - no change
Reinstalled Server 2008R2 again from scratch, installed WSUS again from scratch - no change
WSUS and Server 2008R2 configurations are identical to a previous installation that was working perfectly, and is NOT using a proxy.In my research on this issue I have encountered a number of posts mentioning this, although none of them specified v3.2.
Given that the patch only applies to WSUS v3.2, to do so would be notably redundant. :-)
Is the KB2734608 applicable to WSUS 3.0 as well?
You seem to be confused by nomenclature.
"WSUS 3.0" == WSUS v3 RTM (released Spring 2007)
"WSUS 3.1" == WSUS v3 SP1 (released Summer 2008)
"WSUS 3.2" == WSUS v3 SP2 (released October 2009)
Nonetheless, the patch only applies to WSUS v3 with Service Pack 2, aka WSUS v3.2.
I am hesitant to say that maybe an upgrade to 3.2 may fix the issue
Since you can only install WSUS v3.2 on a Windows Server 2008 R2 server, this is really a non-issue.
I added the WSUS role within the server manager rather than from the standalone installer.
This was probably a key differentiator. I'm curious why you used the standalone installer to begin with.
I should mention, during the server installation, I also did a full factory reset on the router, and reconfigured it accordingly.
I'm still inclined to believe this had the most significant impact on your download failures.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.
Yea, in looking around further I figured out that the 3.2 was a reference to 3.0 SP2. I went ahead and added that patch and lost the ability to synchronize period. At that point I just wiped everything again and am back up and running.
I used the standalone installer as the server role had originally failed and was unusable in the original installation. I stayed with the standalone installer as I had thought it may have been updated from the version included in the 2k8 R2. I now know otherwise.
I was still able to use the wizard to start with, which allowed the server manager to add the necessary required roles and services, but would ultimately fail in installing the WSUS role. This time it all worked like a charm, so I went with it.
As for the router, it may have been the culprit, although prior to the initial server reformat, the previous WSUS installation was working perfectly, about an hour prior to the completion of the the format and the installation and configuration of the WSUS
server.
Either way, thanks for the help and the clarifications on some of the items for me. -
SCCM 2012 SP1 + WSUS + Server 2012 + SQL Server 2012
Hi all;
I installed SCCM 2012 with Sp1 for my site server and everything is going well.. And than i installed the WSUS role on my Windows Server 2012 and SCCM 2012 SP1 it gave an error message which is "Fatal Error: The schema version of the database is from a newer
version of WSUS than currently installed. You must either patch your WSUS server to at least that version or drop the database." My database server is SQL Server 2012... Do you know any pathc for WSUS or SQL Server 2012 doesnt support WSUS yet???
Thank You...
MCTNormally if you are going to install SCCM 2012 SP1 +Windows 2012 with SQL 2012, Then you better use the SQL 2012 sp1.
also when you are installing the WSUS version 6.2 which come with server 2012 make sure you leave the default settings as it is. it shows in the below article.
also when you are giving the path to save the WSUS contents make sure the drive you going to create the wsus folder and the place where you going to download the updates is having free disk space and its formatted with the NTFS volume. Also the service account
you are using for this configuration should have the admin rights to the location of the wsus folder you going to create,
Thanks
Hasitha -
IE 10 will not install from WSUS
I have the latest WSUS running on Server 2008 R2 and about 300 Win7 x64 PC. I initially blocked IE10 by not approving it. But now I have approved it and it will not install. The status per machine is "not applicable".
I have NOT used any "block IE10" tool at the PC level.
I have NOT used any "block IE10" tool at the group policy level.
All I did was "Not approve" it and then several weeks later "Approve it".
Any ideas?
TRLI am having the exact same issue. It looks like the import is not downloading the files. This is the information I've obtained in my troubleshooting so far.
I am receiving the following errors when installing IE10 through WSUS. I have imported the update from Microsoft's Update Catalog (on 4-11-2013), then approved the update to testing & pilot groups. The following errors occur when the clients
try to install IE10 from WSUS. They do not occur when installing from the internet through Microsoft's servers. From everything I can see through the log files, there are no installation files on the WSUS server. Is there any way to manually
add them, or re-import the update? Perhaps through a SQL query?
Installation Failure: Windows failed to install the following update with error 0x80070643: Internet Explorer 10 for Windows 7.
After importing the update into WSUS, nothing new was synchronized to the server. When right clicking on the IE10 updates, and going to 'File Information', the only files shown with a modified date of 4-11-2013 are ~4kb *.txt files. There are
no executables.
The following are a log excerpt when installing from WSUS, with bolded information to highlight what I believe are problems:
WindowsUpdate.log
2013-04-14 01:00:12:869 1180 c90 AU #############
2013-04-14 01:00:12:869 1180 c90 AU ## START ## AU: Search for updates
2013-04-14 01:00:12:869 1180 c90 AU #########
2013-04-14 01:00:12:869 1180 c90 AU <<## SUBMITTED ## AU: Search for updates [CallId = {58A7FACD-FF0E-49B7-BDF1-656D17B98938}]
2013-04-14 01:00:12:869 1180 4f8 Agent *************
2013-04-14 01:00:12:869 1180 4f8 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-04-14 01:00:12:869 1180 4f8 Agent *********
2013-04-14 01:00:12:869 1180 4f8 Agent * Online = Yes; Ignore download priority = No
2013-04-14 01:00:12:869 1180 4f8 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1
and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2013-04-14 01:00:12:869 1180 4f8 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-04-14 01:00:12:869 1180 4f8 Agent * Search Scope = {Machine}
2013-04-14 01:00:12:869 1180 4f8 Setup Checking for agent SelfUpdate
2013-04-14 01:00:12:885 1180 4f8 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2013-04-14 01:00:12:916 1180 4f8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-04-14 01:00:13:697 1180 4f8 Misc Microsoft signed: Yes
2013-04-14 01:00:17:494 1180 4f8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-04-14 01:00:17:526 1180 4f8 Misc Microsoft signed: Yes
2013-04-14 01:00:17:572 1180 4f8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-04-14 01:00:17:619 1180 4f8 Misc Microsoft signed: Yes
2013-04-14 01:00:17:619 1180 4f8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-04-14 01:00:17:635 1180 4f8 Misc Microsoft signed: Yes
2013-04-14 01:00:17:713 1180 4f8 Setup Determining whether a new setup handler needs to be downloaded
2013-04-14 01:00:17:729 1180 4f8 Setup SelfUpdate handler is not found. It will be downloaded
2013-04-14 01:00:17:729 1180 4f8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
2013-04-14 01:00:17:729 1180 4f8 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
2013-04-14 01:00:17:729 1180 4f8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
2013-04-14 01:00:17:760 1180 4f8 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
2013-04-14 01:00:17:760 1180 4f8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
2013-04-14 01:00:17:807 1180 4f8 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
2013-04-14 01:00:17:807 1180 4f8 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2013-04-14 01:00:18:776 1180 4f8 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2013-04-14 01:00:18:776 1180 4f8 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://*****:8530/ClientWebService/client.asmx
2013-04-14 01:00:19:432 1180 4f8 PT WARNING: Cached cookie has expired or new PID is available
2013-04-14 01:00:19:432 1180 4f8 PT Initializing simple targeting cookie, clientId = a6aa9dc9-dc78-4bcb-b23b-de6d377f3cb2, target group = Testbed, DNS name = ****.****.com
2013-04-14 01:00:19:432 1180 4f8 PT Server URL = http://*****:8530/SimpleAuthWebService/SimpleAuth.asmx
2013-04-14 01:00:27:213 1180 4f8 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2013-04-14 01:00:27:213 1180 4f8 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://*****:8530/ClientWebService/client.asmx
2013-04-14 01:00:28:229 1180 4f8 Agent * Added update {87E13ECB-C669-43BE-9E2A-01E567285031}.203 to search result
2013-04-14 01:00:28:229 1180 4f8 Agent * Found 1 updates and 69 categories in search; evaluated appl. rules of 756 out of 1007 deployed entities
2013-04-14 01:00:28:260 1180 4f8 Agent *********
2013-04-14 01:00:28:260 1180 4f8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-04-14 01:00:28:260 1180 4f8 Agent *************
2013-04-14 01:00:28:291 1180 3f0 AU >>## RESUMED ## AU: Search for updates [CallId = {58A7FACD-FF0E-49B7-BDF1-656D17B98938}]
2013-04-14 01:00:28:291 1180 3f0 AU # 1 updates detected
2013-04-14 01:00:28:291 1180 3f0 AU #########
2013-04-14 01:00:28:291 1180 3f0 AU ## END ## AU: Search for updates [CallId = {58A7FACD-FF0E-49B7-BDF1-656D17B98938}]
2013-04-14 01:00:28:291 1180 3f0 AU #############
***Notice: there is no 'Download' section:***
2013-04-14 01:00:28:307 1180 3f0 AU Successfully wrote event for AU health state:0
2013-04-14 01:00:28:307 1180 3f0 AU Featured notifications is disabled.
2013-04-14 01:00:28:307 1180 3f0 AU AU setting next detection timeout to 2013-04-15 03:52:00
2013-04-14 01:00:28:323 1180 3f0 AU Successfully wrote event for AU health state:0
2013-04-14 01:00:33:229 1180 4f8 Report REPORT EVENT: {94640381-460D-4C10-8325-77979804D8A8} 2013-04-14 01:00:28:229-0600 1
147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows
Update Client successfully detected 1 updates.
2013-04-14 01:00:33:229 1180 4f8 Report REPORT EVENT: {FC1B6FAB-E6F1-40E2-B12C-8C3E192032BD} 2013-04-14 01:00:28:260-0600 1
156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting
client status.
2013-04-14 01:00:33:229 1180 4f8 Report CWERReporter finishing event handling. (00000000)
2013-04-14 01:00:36:260 1180 a58 DnldMgr Preparing update for install, updateId = {497DC29B-53B4-437B-81C1-92F0E5946E4B}.203.
2013-04-14 01:00:36:760 756 804 Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0600) ===========
2013-04-14 01:00:36:760 756 804 Misc = Process: C:\Windows\system32\wuauclt.exe
2013-04-14 01:00:36:760 756 804 Misc = Module: C:\Windows\system32\wuaueng.dll
2013-04-14 01:00:36:760 756 804 Handler :::::::::::::
2013-04-14 01:00:36:760 756 804 Handler :: START :: Handler: Command Line Install
2013-04-14 01:00:36:760 756 804 Handler :::::::::
2013-04-14 01:00:36:760 756 804 Handler : Updates to install = 1
2013-04-14 01:00:42:338 756 804 Handler : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14 01:00:42:338 756 804 Handler :::::::::
2013-04-14 01:00:42:338 756 804 Handler :: END :: Handler: Command Line Install
2013-04-14 01:00:42:338 756 804 Handler :::::::::::::
2013-04-14 01:00:42:370 1180 a58 DnldMgr Preparing update for install, updateId = {4A2D8132-7DA3-4B00-A37C-C004B77BA4CB}.203.
2013-04-14 01:00:42:635 756 804 Handler :::::::::::::
2013-04-14 01:00:42:635 756 804 Handler :: START :: Handler: Command Line Install
2013-04-14 01:00:42:635 756 804 Handler :::::::::
2013-04-14 01:00:42:635 756 804 Handler : Updates to install = 1
2013-04-14 01:00:44:198 756 804 Handler : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14 01:00:44:198 756 804 Handler :::::::::
2013-04-14 01:00:44:198 756 804 Handler :: END :: Handler: Command Line Install
2013-04-14 01:00:44:198 756 804 Handler :::::::::::::
2013-04-14 01:00:44:198 1180 a58 DnldMgr Preparing update for install, updateId = {F50DB706-BA83-4247-800D-89BFE2FBCBBF}.203.
2013-04-14 01:00:44:307 756 804 Handler :::::::::::::
2013-04-14 01:00:44:307 756 804 Handler :: START :: Handler: Command Line Install
2013-04-14 01:00:44:307 756 804 Handler :::::::::
2013-04-14 01:00:44:307 756 804 Handler : Updates to install = 1
2013-04-14 01:00:45:229 756 804 Handler : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14 01:00:45:229 756 804 Handler :::::::::
2013-04-14 01:00:45:229 756 804 Handler :: END :: Handler: Command Line Install
2013-04-14 01:00:45:229 756 804 Handler :::::::::::::
2013-04-14 01:00:45:245 1180 a58 DnldMgr Preparing update for install, updateId = {2C886B27-09D4-4DE3-8BBC-1EB5CD5BC76A}.203.
2013-04-14 01:00:45:276 756 804 Handler :::::::::::::
2013-04-14 01:00:45:276 756 804 Handler :: START :: Handler: Command Line Install
2013-04-14 01:00:45:276 756 804 Handler :::::::::
2013-04-14 01:00:45:276 756 804 Handler : Updates to install = 1
2013-04-14 01:00:45:932 756 804 Handler : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14 01:00:45:932 756 804 Handler :::::::::
2013-04-14 01:00:45:932 756 804 Handler :: END :: Handler: Command Line Install
2013-04-14 01:00:45:932 756 804 Handler :::::::::::::
2013-04-14 01:00:45:948 1180 a58 DnldMgr Preparing update for install, updateId = {516C5430-1639-460B-A8D8-53BA47211610}.203.
2013-04-14 01:00:45:963 756 804 Handler :::::::::::::
2013-04-14 01:00:45:963 756 804 Handler :: START :: Handler: Command Line Install
2013-04-14 01:00:45:963 756 804 Handler :::::::::
2013-04-14 01:00:45:963 756 804 Handler : Updates to install = 1
2013-04-14 01:00:46:463 756 804 Handler : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14 01:00:46:463 756 804 Handler :::::::::
2013-04-14 01:00:46:463 756 804 Handler :: END :: Handler: Command Line Install
2013-04-14 01:00:46:463 756 804 Handler :::::::::::::
2013-04-14 01:00:46:463 1180 a58 DnldMgr Preparing update for install, updateId = {822B837F-FFF0-44A8-9244-1AA8A0D77F7C}.203.
2013-04-14 01:00:47:416 756 804 Handler :::::::::::::
2013-04-14 01:00:47:416 756 804 Handler :: START :: Handler: Command Line Install
2013-04-14 01:00:47:416 756 804 Handler :::::::::
2013-04-14 01:00:47:416 756 804 Handler : Updates to install = 1
2013-04-14 01:01:21:464 756 804 Handler : WARNING: Command line install completed. Return code = 0x00009c47, Result = Failed, Reboot required = false
2013-04-14 01:01:21:464 1180 3f0 AU >>## RESUMED ## AU: Installing update [UpdateId = {87E13ECB-C669-43BE-9E2A-01E567285031}]
2013-04-14 01:01:21:464 756 804 Handler : WARNING: Exit code = 0x8024200B
2013-04-14 01:01:21:464 1180 3f0 AU # WARNING: Install failed, error = 0x80070643 / 0x00009C47
2013-04-14 01:01:21:464 756 804 Handler :::::::::
2013-04-14 01:01:21:464 756 804 Handler :: END :: Handler: Command Line Install
2013-04-14 01:01:21:464 756 804 Handler :::::::::::::
2013-04-14 01:01:21:510 1180 a58 Agent *********
2013-04-14 01:01:21:510 1180 3f0 AU Install call completed.
2013-04-14 01:01:21:510 1180 a58 Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
2013-04-14 01:01:21:510 1180 3f0 AU # WARNING: Install call completed, reboot required = No, error = 0x00000000
2013-04-14 01:01:21:510 1180 a58 Agent *************
2013-04-14 01:01:21:510 1180 3f0 AU #########
2013-04-14 01:01:21:510 1180 3f0 AU ## END ## AU: Installing updates [CallId = {612023CC-6538-4722-9742-5FD88A9CB328}]
2013-04-14 01:01:21:510 1180 3f0 AU #############
2013-04-14 01:01:21:510 1180 3f0 AU Install complete for all calls, reboot NOT needed
2013-04-14 01:01:21:510 1180 3f0 AU Setting AU scheduled install time to 2013-04-15 07:00:00
2013-04-14 01:01:21:510 1180 3f0 AU Successfully wrote event for AU health state:0
2013-04-14 01:01:21:510 1180 3f0 AU Successfully wrote event for AU health state:0
2013-04-14 01:01:21:510 1180 3f0 AU Triggering Offline detection (non-interactive)
2013-04-14 01:01:21:510 1180 c90 AU #############
2013-04-14 01:01:21:510 1180 c90 AU ## START ## AU: Search for updates
2013-04-14 01:01:21:510 1180 c90 AU #########
2013-04-14 01:01:21:526 1180 c90 AU <<## SUBMITTED ## AU: Search for updates [CallId = {4CC39288-6E0C-4F19-ADEC-FAC9B9B68424}]
2013-04-14 01:01:21:526 1180 4f8 Agent *************
2013-04-14 01:01:21:526 1180 4f8 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-04-14 01:01:21:526 1180 4f8 Agent *********
2013-04-14 01:01:21:526 1180 4f8 Agent * Online = No; Ignore download priority = No
2013-04-14 01:01:21:526 1180 4f8 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1
and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2013-04-14 01:01:21:526 1180 4f8 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-04-14 01:01:21:526 1180 4f8 Agent * Search Scope = {Machine}
2013-04-14 01:01:26:698 1180 4f8 Agent * Added update {87E13ECB-C669-43BE-9E2A-01E567285031}.203 to search result
2013-04-14 01:01:26:698 1180 4f8 Agent * Found 1 updates and 69 categories in search; evaluated appl. rules of 617 out of 1007 deployed entities
2013-04-14 01:01:26:698 1180 4f8 Agent *********
2013-04-14 01:01:26:698 1180 4f8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-04-14 01:01:26:698 1180 4f8 Agent *************
2013-04-14 01:01:26:745 1180 3f0 AU >>## RESUMED ## AU: Search for updates [CallId = {4CC39288-6E0C-4F19-ADEC-FAC9B9B68424}]
2013-04-14 01:01:26:745 1180 3f0 AU # 1 updates detected
2013-04-14 01:01:26:745 1180 4f8 Report REPORT EVENT: {F08F242D-B9C4-42EA-94A4-DD77F772F6BA} 2013-04-14 01:01:21:464-0600 1
195 101 {87E13ECB-C669-43BE-9E2A-01E567285031} 203 80070643 AutomaticUpdates Failure Content Install Installation
Failure: Windows failed to install the following update with error 0x80070643: Internet Explorer 10 for Windows 7.
2013-04-14 01:01:26:745 1180 3f0 AU #########
2013-04-14 01:01:26:745 1180 3f0 AU ## END ## AU: Search for updates [CallId = {4CC39288-6E0C-4F19-ADEC-FAC9B9B68424}]
2013-04-14 01:01:26:745 1180 3f0 AU #############
IE10_main.log
00:00.000: ====================================================================
00:00.219: Started: 2013/04/14 (Y/M/D) 01:00:49.057 (local)
00:00.250: Time Format in this log: MM:ss.mmm (minutes:seconds.milliseconds)
00:00.266: Command line: "C:\Windows\SoftwareDistribution\Download\Install\WU-IE10-Windows7-x86.exe" /WSUS
00:00.297: INFO: Setup installer for Internet Explorer: 10.0.9200.16521
00:00.375: INFO: Previous version of Internet Explorer: 9.0.8112.16476
00:00.391: INFO: Checking if iexplore.exe's current version is between 10.0.8100.0...
00:00.422: INFO: ...and 10.1.0.0...
00:00.453: INFO: Maximum version on which to run IEAK branding is: 10.1.0.0...
00:00.485: INFO: iexplore.exe version check success. Install can proceed.
00:00.500: INFO: Operating System: Windows Workstation: 6.1.7601 (Service Pack 1)
00:00.563: INFO: Trying to extract ID: SetupDownloadList.txt (0) as "SetupDownloadList.txt"
00:00.610: INFO: Trying to extract ID: HardwareBlockingList.xml (0) as "HardwareBlockingList.xml"
00:00.641: INFO: Trying to extract ID: 6006 (0) as "IE10-neutral.Extracted.cab"
00:00.813: INFO: Trying to extract ID: 5501 (1033) as "Spelling_en.msu"
00:00.953: INFO: Extracted Spelling dictionary for en to C:\Windows\TEMP\IE14D3E.tmp\Spelling_en.msu.
00:01.016: INFO: Trying to extract ID: 5502 (1033) as "Hyphenation_en.msu"
00:01.047: INFO: Extracted Hyphenation dictionary for en to C:\Windows\TEMP\IE14D3E.tmp\Hyphenation_en.msu.
00:01.094: INFO: Trying to extract ID: 6128 (1033) as "IE10-support.cab"
00:02.219: INFO: Launched program to check hardware: "C:\Windows\TEMP\IE14D3E.tmp\IE10-SUPPORT\IEXPLORE.EXE" /CheckHardware "C:\Windows\TEMP\IE14D3E.tmp\HardwareBlockingList.xml"
00:03.328: INFO: Hardware support check succeeded. Installation will continue.
00:03.406: INFO: Windows 7 operating system detected.
00:03.469: INFO: Service pack major: 1
00:03.516: INFO: Service pack minor: 0
00:03.531: INFO: Service pack name: Service Pack 1
00:03.563: WARNING: Checking version for C:\Windows\System32\api-ms-win-downlevel-user32-l1-1-0.dll. The file does not exist.
00:03.578: INFO: Version Check for (KB2639308) of C:\Windows\System32\Ntoskrnl.exe: 6.1.7601.18113 >= 6.1.7601.17727 (True)
00:03.656: INFO: Version Check for (KB2533623) of C:\Windows\System32\api-ms-win-security-base-l1-1-0.dll: 6.1.7601.18015 >= 6.1.7601.17617 (True)
00:03.688: INFO: Version Check for (KB2731771) of C:\Windows\System32\kernel32.dll: 6.1.7601.18015 >= 6.1.7601.17932 (True)
00:03.750: INFO: Checking for correct version of C:\Windows\Fonts\segoeui.ttf.
00:03.875: INFO: Version Check for (KB2786081) of C:\Windows\System32\taskhost.exe: 6.1.7601.18010 >= 6.1.7601.18010 (True)
00:26.656: INFO: Setup exit code: 0x00009C47 (40007) - Required updates failed to download.
00:26.844: INFO: Scheduling upload to IE SQM server: http://sqm.microsoft.com/sqm/ie/sqmserver.dll
00:31.922: ERROR: SQM Upload failed while uploading "C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files\SQM\iesqmdata_setup0.sqm" with error: 2147500036
00:32.031: INFO: Cleaning up temporary files in: C:\Windows\TEMP\IE14D3E.tmp
00:32.156: INFO: Unable to remove directory C:\Windows\TEMP\IE14D3E.tmp, marking for deletion on reboot.
00:32.281: INFO: Released Internet Explorer Installer Mutex
00:00.000: ====================================================================
The following are excerpts when installing from the Internet:
WindowsUpdate.log
***Truncated information to fit in post***
***Notice: This section is not present when using WSUS***
2013-05-08 10:32:05:573 1148 58c AU ## START ## AU: Download updates
2013-05-08 10:32:05:573 1148 58c AU #########
2013-05-08 10:32:05:573 1148 58c AU # Approved updates = 1
2013-05-08 10:32:05:589 1148 58c AU AU initiated download, updateId = {C0B3230A-BB79-4E44-B771-177BC224FCBF}.203, callId = {AE199656-7E10-4EB7-B24E-BEC6A3A56ABC}
2013-05-08 10:32:05:589 1148 58c AU # Pending download calls = 1
2013-05-08 10:32:05:589 1148 58c AU <<## SUBMITTED ## AU: Download updates
2013-05-08 10:32:05:589 1148 590 DnldMgr *************
2013-05-08 10:32:05:589 1148 590 DnldMgr ** START ** DnldMgr: Downloading updates [CallerId = AutomaticUpdatesWuApp]
2013-05-08 10:32:05:589 1148 590 DnldMgr *********
2013-05-08 10:32:05:589 1148 590 DnldMgr * Call ID = {AE199656-7E10-4EB7-B24E-BEC6A3A56ABC}
2013-05-08 10:32:05:589 1148 590 DnldMgr * Priority = 3, Interactive = 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 1, ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}
2013-05-08 10:32:05:589 1148 590 DnldMgr * Updates to download = 1
2013-05-08 10:32:05:589 1148 590 Agent * Title = Internet Explorer 10 for Windows 7
2013-05-08 10:32:05:589 1148 590 Agent * UpdateId = {C0B3230A-BB79-4E44-B771-177BC224FCBF}.203
2013-05-08 10:32:05:589 1148 590 Agent * Bundles 6 updates:
2013-05-08 10:32:05:589 1148 590 Agent * {F03964C0-E029-4033-9D69-1583A40EB317}.203
2013-05-08 10:32:05:589 1148 590 Agent * {A86D9C79-A43B-4B11-A74B-EA13F21926F2}.203
2013-05-08 10:32:05:589 1148 590 Agent * {B765BC98-D278-46D7-9BE7-23EBA0DB3491}.203
2013-05-08 10:32:05:589 1148 590 Agent * {0DE3BD6A-2848-4791-968E-6DB43BEAC578}.203
2013-05-08 10:32:05:589 1148 590 Agent * {35E2AD10-DAEF-4301-8C15-6BCC080604FA}.203
2013-05-08 10:32:05:589 1148 590 Agent * {4B24E051-669D-44D1-B920-7F123F0D6728}.203
2013-05-08 10:32:05:589 1148 58c AU Getting featured update notifications. fIncludeDismissed = true
2013-05-08 10:32:05:589 1148 58c AU No featured updates available.
2013-05-08 10:32:05:589 1148 590 DnldMgr *********** DnldMgr: New download job [UpdateId = {F03964C0-E029-4033-9D69-1583A40EB317}.203] ***********
2013-05-08 10:32:05:620 1148 590 DnldMgr * All files for update were already downloaded and are valid.
2013-05-08 10:32:05:620 1148 590 DnldMgr *********** DnldMgr: New download job [UpdateId = {A86D9C79-A43B-4B11-A74B-EA13F21926F2}.203] ***********
2013-05-08 10:32:05:745 1148 590 DnldMgr * All files for update were already downloaded and are valid.
2013-05-08 10:32:05:745 1148 590 DnldMgr *********** DnldMgr: New download job [UpdateId = {B765BC98-D278-46D7-9BE7-23EBA0DB3491}.203] ***********
2013-05-08 10:32:05:792 1148 590 DnldMgr * All files for update were already downloaded and are valid.
2013-05-08 10:32:05:792 1148 590 DnldMgr *********** DnldMgr: New download job [UpdateId = {0DE3BD6A-2848-4791-968E-6DB43BEAC578}.203] ***********
2013-05-08 10:32:05:808 1148 590 DnldMgr * All files for update were already downloaded and are valid.
2013-05-08 10:32:05:808 1148 590 DnldMgr *********** DnldMgr: New download job [UpdateId = {35E2AD10-DAEF-4301-8C15-6BCC080604FA}.203] ***********
2013-05-08 10:32:05:823 1148 590 DnldMgr * All files for update were already downloaded and are valid.
2013-05-08 10:32:05:823 1148 590 DnldMgr *********** DnldMgr: New download job [UpdateId = {4B24E051-669D-44D1-B920-7F123F0D6728}.203] ***********
2013-05-08 10:32:06:464 1148 590 DnldMgr * All files for update were already downloaded and are valid.
2013-05-08 10:32:06:464 1148 590 Agent *********
2013-05-08 10:32:06:464 1148 c9c AU >>## RESUMED ## AU: Download update [UpdateId = {C0B3230A-BB79-4E44-B771-177BC224FCBF}, succeeded]
2013-05-08 10:32:06:464 1148 590 Agent ** END ** Agent: Downloading updates [CallerId = AutomaticUpdatesWuApp]
2013-05-08 10:32:06:464 1148 590 Agent *************
2013-05-08 10:32:06:464 1148 c9c AU #########
2013-05-08 10:32:06:480 1148 c9c AU ## END ## AU: Download updates
2013-05-08 10:32:06:480 1148 c9c AU #############
***Truncated information to fit in post***
2013-05-08 10:35:51:050 1148 b98 Agent *************
2013-05-08 10:35:51:050 1148 c9c AU # WARNING: Install call completed, reboot required = Yes, error = 0x00000000
2013-05-08 10:35:51:050 1148 c9c AU #########
2013-05-08 10:35:51:050 1148 c9c AU ## END ## AU: Installing updates [CallId = {434D372F-F4C2-4217-8413-EC8BB8E9B386}]
2013-05-08 10:35:51:050 1148 c9c AU #############
IE10_main.log
***Truncated information to fit in post***
***The following lines are not present when using WSUS****
00:10.594: INFO: IE Setup Language pack included: C:\Windows\TEMP\IE157EF.tmp\IE-Spelling-en.cab
00:10.750: INFO: IE Setup Language pack included: C:\Windows\TEMP\IE157EF.tmp\IE-Hyphenation-en.cab
00:11.016: INFO: Waiting for 0 prerequisite downloads.
00:34.688: INFO: The neutral pack was successfully downloaded from the internet. Installation will continue using the downloaded package.
00:35.579: INFO: No reboot logic message NrApiStart(0), lParam=0x00082650 returned 0x00000000.
00:36.922: INFO: No reboot logic message NrApiScan(1), lParam=0x00000001 returned 0x00000000.
00:36.954: INFO: No reboot logic message NrApiStartInstall(4), lParam=0x00000001 returned 0x00000014.
00:36.985: INFO: Installing with the downloaded package. C:\Windows\TEMP\IE157EF.tmp\IE10-neutral.Downloaded.cab
00:37.047: INFO: Launched package installation: C:\Windows\System32\dism.exe /online /add-package /packagepath:C:\Windows\TEMP\IE157EF.tmp\IE10-neutral.Downloaded.cab /quiet /norestart
01:45.750: INFO: Process exit code 0x00000BC2 (3010) [The requested operation is successful. Changes will not be effective until the system is rebooted. ]
01:45.813: INFO: Setting registry to check if Internet Explorer is the default browser on first run: SUCCESS.
01:45.844: INFO: Preparing to install Spelling_en.msu using C:\Windows\TEMP\IE157EF.tmp\Spelling_en.msu
01:45.922: INFO: Launched package installation: C:\Windows\System32\dism.exe /online /add-package /packagepath:C:\Windows\TEMP\IE157EF.tmp\Spelling_en\Windows6.2-KB2764916-x86.cab /quiet /norestart
02:18.235: INFO: Process exit code 0x00000BC2 (3010) [The requested operation is successful. Changes will not be effective until the system is rebooted. ]
02:18.282: INFO: Preparing to install Hyphenation_en.msu using C:\Windows\TEMP\IE157EF.tmp\Hyphenation_en.msu
02:18.344: INFO: Launched package installation: C:\Windows\System32\dism.exe /online /add-package /packagepath:C:\Windows\TEMP\IE157EF.tmp\Hyphenation_en\Windows6.2-KB2764913-x86.cab /quiet /norestart
02:48.672: INFO: Process exit code 0x00000BC2 (3010) [The requested operation is successful. Changes will not be effective until the system is rebooted. ]
02:48.704: INFO: Preparing to install IE-Spelling-en.cab using C:\Windows\TEMP\IE157EF.tmp\IE-Spelling-en.cab
02:48.735: INFO: Launched package installation: C:\Windows\System32\dism.exe /online /add-package /packagepath:C:\Windows\TEMP\IE157EF.tmp\IE-Spelling-en.cab /quiet /norestart
02:58.079: INFO: Process exit code 0x00000BC2 (3010) [The requested operation is successful. Changes will not be effective until the system is rebooted. ]
02:58.125: INFO: Preparing to install IE-Hyphenation-en.cab using C:\Windows\TEMP\IE157EF.tmp\IE-Hyphenation-en.cab
02:58.172: INFO: Launched package installation: C:\Windows\System32\dism.exe /online /add-package /packagepath:C:\Windows\TEMP\IE157EF.tmp\IE-Hyphenation-en.cab /quiet /norestart
03:06.313: INFO: Process exit code 0x00000BC2 (3010) [The requested operation is successful. Changes will not be effective until the system is rebooted. ]
03:06.344: INFO: No reboot logic message NrApiInstallDone(7), lParam=0x00000bc2 returned 0x00000000.
03:06.375: INFO: No reboot logic message NrApiStartFinish(11), lParam=0x00000000 returned 0x00000000.
03:06.407: INFO: No reboot logic message NrApiFinish(12), lParam=0x00000000 returned 0x00000016.
03:06.454: INFO: Verifying that the Internet Explorer Optional Component is enabled.
03:06.485: INFO: Setup exit code: 0x00000BC2 (3010) - Installation Succeeded. Reboot required.
03:06.641: INFO: Scheduling upload to IE SQM server: http://sqm.microsoft.com/sqm/ie/sqmserver.dll
03:10.188: INFO: SQM Upload returned 403
03:12.485: INFO: Cleaning up temporary files in: C:\Windows\TEMP\IE157EF.tmp
03:12.579: INFO: Unable to remove directory C:\Windows\TEMP\IE157EF.tmp, marking for deletion on reboot.
03:12.672: INFO: Released Internet Explorer Installer Mutex -
WSUS Firewall rules do not use names nor groupnames
Hi everyone,
Today I've been playing around with PowerShell Workflows and the firewall cmdlets on my test environment. (Great stuff, Thanks
Scripting Guys)
After working out a little workflow I noticed that the firewall rules that were made by the WSUS feature installation had no Name nor DisplayGroup, only the DisplayName.
My test environment is made up from tree Server 2012 R2 servers with a domain.
The script I made :
workflow Get-AllFirewalls
Parallel{
InlineScript{
Get-NetFirewallRule -Enabled True -Action Allow |?{
$_.Profile -match "Any|Domain"
} | select Name,DisplayName,direction,DisplayGroup,
@{n='Port';e={($_|Get-NetFirewallPortFilter).LocalPort}},
@{n='Protocol';e={($_|Get-NetFirewallPortFilter).Protocol}},
@{n='Program';e={($_|Get-NetFirewallApplicationFilter).Program}}
$output = Get-AllFirewalls -PSComputerName (Get-ADComputer -Filter 'OperatingSystem -like "Windows Server*"').name
$output |Sort-Object DisplayGroup |Format-Table PSComputerName,Name,DisplayName,Direction,Port,Protocol,Program -GroupBy DisplayGroup -AutoSize
Now this is just for testing and I could get around the fact there are no proper names but I think it's sloppy not to fill the naming attributes.
Am I the only one with these results or is it just WSUS?There are only two rules created, one for HTTP on port 8530 one for HTTPS on port 8531, and the latter isn't even used in most WSUS installations.
There is no Group Name, because this is not a GROUP of rules, it is two individual rules. One is always enabled; the second is optionally enabled WHEN the WSUS Server is configured to use SSL, and it's enabled by an administrative script provided in the
WSUS toolset.
Ergo, a server administrator never has to mess with these two rules at all, so, no, I think it's insignificant that these rules may be missing a couple of generally irrelevant attributes.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.
Maybe you are looking for
-
How do i sync iphone with multiple macs? and few questions
Hi I would appreciate if anyone would help me. 1. I would like to know how to sync my iphone with different macs. I have a macbook 13 and a macbook 15 and would like to use BOTH to be able to transfer data without losing them. (address, apps, photos
-
Lookup Table Name for Sale Order Types
Hello, What's the Lookup table name that contains the "meaning" for the column ORDER_TYPE_ID in the OE_ORDER_HEADERS_ALL table? Thanks, Smita
-
Set type COMM_PR_UNIT is not allowed for product type
Hello all, I am working in SRM 7.0 and when I try to replicate service master (DNL_CUST_SRVMAS) I have this error: Set type COMM_PR_UNIT is not allowed for product type What can I do? I think that is an ABAP problem Thanks in advance Rosa Rodríguez
-
In France with the new IOS7 I don't find the iTunes Radio in the music player. Is it a French specification or what do I do wrong? Thanks for your help
-
StorEdge 3320 supported on Solaris 10 x86?
Hello, I cannot install the SUNWsscs package on my X4200 SunFire that is running Solaris 10 for x86. It says it is not the right package, that the SUNWsscs is only for SPARC systems. Does anyone know the correct package to use to install the CLI? Tha