Tag Info

New answers tagged

4

Windows server downtime for updates is inevitable. Service downtime is avoidable, however. The key is to realize that downtime needs to be measured by service availability, not the status of individual servers. For your SQL Server instance, your best bet is to implement some form of multi-server instancing. One technique that Microsoft allows in SQL Server ...


0

I used the System Update Readiness Tool and DISM. It worked for me. You can get it here: http://support.microsoft.com/kB/947821


0

Microsoft released a hotfix for this issue. KB2379016: A computer that is running Windows Vista or Windows Server 2008 stops responding and hangs at the "Applying User Settings" stage of the logon process To work around the issue without installing the hotfix, create a DependOnService registry key to modify the behavior of HTTP.sys. This makes HTTP.sys ...


0

I had the same issue on Windows 2008 R2 with WPAD record. To fit it we add fake DNS record to hosts file like 1.1.1.1 WPAD and after restart the update client it stop using proxy. In some cases the Server needs to be rebooted after WPAD block. Cheers, Andrey


0

This appears to be an issue with this month's (December 2014) "Update Rollup 8" Exchange 2010 SP3 update. KB2986475 "Update Rollup 8-v2 For Exchange Server 2010 Service Pack 3" was recently posted to Microsoft Update. Rolling in this update appears to have resolved the issue.


0

Is it trying to add prerequisite features and restart first? I had a similar problem adding the WSUS role which was clashing when it also added the Windows Internal Database. This guy mentions the error, but my solution was different. Instead of changing group policy, I had to actually provide the WID account access to the WID directory: $WIDService = ...


0

This was solved by deleting an old dependent update that wasn't needed any more. – Ericrobert just now edit


0

Removing Exchange 2010 SP3 Rollup 8 worked for me. Strangely only Outlook 2013 running on Windows 7 (32-bits) had problems with sending mails out. Outlook 2013 on Windows 8.1 (64-bits) was running fine. With Rollup 8 removed all Outlook clients are running normally again.


0

While not specifically related to seeing this error code while running a Software Update Deployment Evaluation Cycle, other users have reported success using CCMCLEAN from the SMS 2003 toolkit to completely remove the ConfigMgr client and then re-install the client to resolve the same error code during the initial client installation. Please note that this ...


0

For configuration and scripting of Windows Update from command line, we are using WuInstall (http://www.wuinstall.com), check the documentation, it allows you to script Windows Updates in many different ways and you can trigger updates at any time via script - we use it also to re-install and patch our Windows servers (calling it via psexec makes it feasible ...


0

Open the SCCM Console, Assets and Compliance and Devices Right-click the computer receiving the error and select Install Client In the Installation Options for the Client Push, make sure to check the Uninstall existing Configuration Manager client before the client is installed checkbox


1

Is the experience common across all clients, or only a selection of clients? -If all clients, I would check the content status of your update packages -If only some clients, I would look at your boundary group configuration. I wasn't able to find much info on that particular error, as I'm sure you were not as well. CMTrace.exe (you should definitely be ...


1

In WindowsITPro blog they say that this update created a problem with the MAPI RPC component. Other mail services (OWA, ActiveSync, etc.) should work properly, because they don't use the faulty component. The update has been removed from "Microsoft updates". As they strongly suggest, you better test all updates before applying them to avoid such ...


1

You may find it more effective and convenient to set the appropriate WSUS server using Group Policy; you can create a Group Policy Object with the settings under Computer Configuration > Administrative Templates > Windows Components > Windows Update, primarily Specify intranet Microsoft update service location , but also any other options within the ...


3

There are 4 registry keys that will let you know if there are pending updates. HopelessN00b was on the right track, though you have to go up one level to see the keys. HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update The keys you want are: UpdatesAvailableForDownloadLogon - Updates pending download(important updates) ...


0

To report the current update status to the WSUS you run (from the client's command line): wuauclt /reportnow This will report the machine to the WSUS including the currently installed updates. Note that this will not search for new updates. To trigger a search you run: wuauclt /detectnow


0

You need to stop and start the service WUAUSERV to manually trigger the updates. Command line on a local machine: net stop wuauserv net start wuauserv Command line on a remote machine: sc \\<hostname remotemachine> stop wuauserv sc \\<hostname remotemachine> start wuauserv Edit: From a central machine you can force it on all clients from a ...


4

I am not sure if it is possible to find the number of pending important updates. But in HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\UAS there is a Key called UpdateCount that will give you the total number of pending updates.


0

Unfortunately, even if "download only" Windows Update still "checks" things, particularly at startup. What seems to be happening here is it is finding problems in the process of doing so. Unfortunately, the problem that seems to match most closely based on the errors in the log above is this one: ...


0

for me it was in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate\DisableWindowsUpdateAccess I set it to 0


1

You may do better to build a Powershell DSC to enforce this policy, and apply that to the newly built server instances. Based on my readings of http://technet.microsoft.com/en-us/library/dd939844(v=ws.10).aspx, it looks like you could solve this with: WindowsAutoUpdate Policy { Node localhost { Registry EnableSilentUpdates { ...



Top 50 recent answers are included