Archive

Archive for the ‘Troubleshooting’ Category

Update on the ConfigMgr 2012 Update Scan Issue – Windowsupdate.log Error 8007000E

April 16, 2015 1 comment

Last week Kim blogged about an issue with Windows 7 and Software Updates that some of his customers had been reporting.

Kim had already outlined the issue and the symptoms, plus also provided a few workarounds which may help in resolving it. Through this post I wanted to inform you that now Microsoft has published a blog post that:

a) gives some more details on the root cause of the problem

b) outlines some possible workarounds and

c) most importantly : states a hotfix is in the pipeline which will be available in (late) Q2

You can find the full details here.

I ran into the same issue at one of my customers last week and have been working with Microsoft support to get this resolved. Below you can read some findings and experiences from the past days.

The workaround to Move wuauserv (Windows Update Agent) to its own SVCHost.exe instance did not prove to be very successful. Although we saw the scan job succeeding on a few clients at first, after a few additional scans the issue returned.

Next step was cleaning up WSUS. First we needed to verify what we could potentially clean up using the script provided by Microsoft:

image

To get things back on the rails in the end the only successful method was to run WSUS cleanup script to decline all superseded updates. Running the script with the –DeclineLastLevelOnly switch was not sufficient.

Important: Before running this cleanup script make sure to identify if any of the updates are still needed! It could be a superseding update has not yet been released due to your internal approval and/or release processes!

And while you are checking that also note that the script output may be misleading. Set the LastLevel column filter to False if you are actually looking for the Last Level Superseded Updates.

clip_image001

Running the script itself took around 15 minutes.

Note: if you are running multiple SUPS in your environment you should only run this on one SUP – the one with Windows Update set as synchronization source.

Hope it helps!

Tim

Advertisements

Outlook for iOS badge count not showing

February 2, 2015 3 comments

Earlier this week Microsoft has released the Outlook for iOS application. I have been using the application for the past few days and I personally find it a major improvement compared to the default mail application.

One thing I noticed straight away was that the badge counter indicating the number of unread emails did not display for the Outlook application. The counter did work fine for my old email app. As I am not using any other notifications (sound or display) for email I found this is a feature I quite heavily rely on when quickly checking for new mails. I needed to get this resolved.

First step I did for troubleshooting was to check the settings menu in the application to see if anything was hinting toward this option. There is a badge count setting, but other than switching between the Focused and All inboxes there are no other options to set.

2015-02-02 16.38.23

 

When digging further into this I found that the key to solve this problem is in the notification settings for the application (in the general phone settings). Here I had to enable the Allow Notifications option first to reveal further options. The badge app icon is the one that I needed to enable.

2015-02-02 16.37.59

 

The immediate result:

OutlookIOSBadge

Simple fix for a simple issue. Why the Allow Notifications setting was disabled by default remains an unanswered question. A few of my friends installed the application as well and for them the badge count was enabled immediately.

I hope this may help you save some troubleshooting time in case you are also missing the badge count on your Outlook for iOS application.

Until next time!

Tim