System Center Operations Manager (SCOM) Console Crash

scom-gsx-solutions

** UPDATE**
(October 19, 2016)
A fix for the SCOM console crash issue as previously blogged below has been released. See the following KB320006 article to obtain the hotfix.

***************************************************************************************************

**Posted on October 18, 2016**

There is a widespread report of System Center Operations Manager (SCOM) 2012 R2 / 2016 console crashes due to some bugs in October 2016 Cummulative Updates, in particular with the following patches: KB3194798 / KB3192392 / KB3185330 / KB3185331.

The product team has acknowledged the issue on their blog post and is said to be working on releasing a fix soon. The current recommendation is to uninstall the problematic patches as a temporary workaround. According to the blog post, an announcement will be made on the SCOM Team blog when a fix has been made available. So, keep a close eye on it.

Links related to this post:

SCOM Product Team Console Issue Ackowledgement
TechNet Discussion
SCOM Product Team Blog
Microsoft Tech Community Discussion

Follow (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share:

How To Reset WSUS Server

3d human try to press a button

Sometimes, for various reasons, one must perform a WSUS reset function to make the WSUS server happy again. The reset process forces a resync of each update in the WSUS server with Microsoft services. This task can take a long time to complete as each update will be re-evaluated and re-downloaded, so be patient.

Here’s the command to run from an administrator command prompt::
%SystemDrive%\Program Files\Update Services\Tools\WsusUtil.exe reset

Follow (@Hoorge) on Twitter and join Tech Konnect on Facebook to stay current on technology related matters.

Please like & share:

Repair Windows Update Agent

Windows-Update

Every now and then, you may discover a computer system that is unable to detect or install available software updates from Microsoft or from your internal Windows Server Update Services (WSUS) repository. You’ll find an error such as 8007000E generated and often times running the Windows Update Troubleshooter FixIt tool is sufficient to fix Windows Update errors, but sometimes a manual approach that requires the deletion of the SoftwareDistribution content and re-registering the Windows Update components is needed, and this can be a tedious task. By using a script, this repair task can be automated.

Here are some batch scripts to help  fix a broken Windows Update Agent on a computer system. The scripts can also be run on a remote system using the ‘psexec‘ tool, which is part of the Sysinternals Suite from Microsoft. Copy and paste the content of your desired batch file below into Notepad and save the file with the “.bat” file extension, for example: repair_wua.bat .

Version 1:

Version 2:

Here’s another Windows Update Agent Reset script available on Technet.
The Windows Update Troubleshooter is available here.

Follow me on Twitter (@Hoorge) and join Tech Konnect on Facebook to stay current on technology related matters.

Please like & share:

KB3035131 March 2015 – LogonUI.exe Error

We have discovered an issue with one of the patches from March 2015, KB3035131 against our Windows 8.1 systems in VMware VDI. Upon installation of this patch, Windows 8.1 systems are unusable as they are presented with a LogonUI.exe error on startup as seen below. In order to get the systems in working condition, the only resolution at this point is to revert to a previous snapshot and disable the 3035131 patch from installing on these Windows 8.1 systems.

memory_error_2015-03-13

There’s not much info on the Internet regarding this particular issue, or at least one that I can find, however there are some mentions of the use of StartIsBack or Classic Shell, but we are not using them. It will be interesting to know if others have encountered a similar experience, what are the known causes, and if there’s a fix to rectify this issue.

 

Please like & share: