You are browsing the archive for Troubleshooting.

Avatar of timdk

by timdk

ConfigMgr 1606–Unable to modify language configuration

12:30 am in Configuration Manager by timdk

A customer of mine recently reported they could no longer add any client or server languages to their Configuration Manager 1606 site.

When running the setup wizard the option to modify language configuration is greyed out.



I have blogged full details on the cause and how to resolve the issue on my personal blog.

Hope it helps!


Avatar of timdk

by timdk

Configuration Manager 1511 – Client hangs on initializing during OSD

3:49 pm in Configuration Manager, Troubleshooting by timdk

A customer that recently upgraded to Configuration Manager 1511 CB ran into an issue with deploying newly captured OS images. The task sequence is hanging on client initialization and fails eventually. Images captured before the upgrade could still be deployed without any issues.

This blog post details how we resolved this.


When deploying an OS image captured using a Build and Capture task sequence in Configuration Manager 1511 the client hangs on the client initialization step. In the smsts.log we see an entry Waiting for the CCMExec service to be fully operational . After that there is one more entry referring to loading TSRES.DLL .




This is a known bug in Configuration Manager 1511 which is logged on Connect (ID 2153746).

Feedback on the connect item indicates this will be fixed in an upcoming update to the Configuration Manager current branch. The workaround for now is to not include the client in the image.

Note : in 1602 Technical Preview this issue has already been fixed.



There is another way to work around this if you do not want to pursue the alternative not to include the client in the image.

For this you would need to modify the Build and Capture task sequence to include two additional steps:

  • Step 1 : run ccmrepair
  • Step 2 : reboot the system
    An example is shown in the screenshot below.


When deploying the newly captured image using the modified task sequence the client will no longer hang on initializing.

Once the next update of Configuraiton Manager CB is implemented in your environment these two steps can be removed again.

Hope it helps!


Avatar of timdk

by timdk

Update for Windows Update Client addresses ConfigMgr 2012 Update Scan Issue – Windowsupdate.log Error 8007000E

10:40 am in Configuration Manager by timdk

Exclamation-iconYesterday Microsoft has released an update for the Windows Update client. This relates to the issue with Windows 7 and Software Updates which I blogged about a few weeks ago.

This is the KB article: Windows Update Client for Windows 7 : June 2015

Interesting: the KB Article mentions this update does not only address the out-of-memory issue but also contains general improvements made to support upgrades to a later version of windows.

If you have Windows 7 x86 clients in your environment the best approach would be to release this update in your environment as soon as possible. Important : you need to install the hardening update KB2938066 on your WSUS servers prior to releasing this update!

Hope it helps!


Avatar of timdk

by timdk

ConfigMgr R2 SP1 upgrade does not clean up previous Cumulative Update entries in Control Panel > Programs and Features

2:09 pm in Configuration Manager by timdk

Hi All,

Just a quick blog post on a small anomaly with Configuration Manager R2 Service Pack 1.


When upgrading an existing Configuration Manager site it seems the Installed Updates entries related to prior Cumulative Updates are not properly cleaned up. After upgrading a site the end result for Installed Updates looks like this:


The above example is based on a site that was up to Cumulative Update 5 – but the same happens with earlier released Cumulative Updates.

Although this is not really an issue and more cosmetics, it is something that could have been handled more properly by the Service Pack installer. A scenario where this potentially may cause unwanted effects is when using this information in your queries (collections, etc.).


The entries displayed are read from the registry. The screenshot below shows the entry in the registry for the particular cumulative update:


I used the following steps to clean this up:

  1. Start the Registry Editor (regedit.exe)
  2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall .
  3. Locate the key for CU5 (see screenshot) and take a backup (right-click > export).
  4. Delete the key for CU5.
  5. All done – the entry is no longer displayed.

Note that this cleans up the cosmetics part only – any other leftovers (if any) from Cumulative Updates (and alike) will still remain on the system.

Until next time!


Avatar of timdk

by timdk

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

12:36 am in Configuration Manager, Troubleshooting by timdk

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:


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.


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!


Avatar of timdk

by timdk

UDM: Conditional Access – Saving of Access Rules to Exchange has failed (error: A2CE0100)

8:05 pm in Configuration Manager, Enterprise Mobility Management, Microsoft Intune by timdk

A few days ago we have been working on extending our hybrid demo environment. We made some changes required to demonstrate conditional access with Exchange online. Details on how we set things up will follow shortly in another post.

Once the basics were in place we implemented a policy that would block a user to access their mailbox when using an unmanaged device.

The policy was properly deployed to a collection which included my demo user, however I noticed my demo user could still sync his mail on an iPhone 5 which was not enrolled. Even after an hour or two this condition remained unchanged so something was wrong.

Initial investigation did not show anything out of the ordinary in the Configuration Manager console. However in the Intune console I noticed an entry in the Alerts node:

Saving of Access Rules to Exchange has failed

Microsoft Intune was unable to set the requested mobile device access rules or related settings in Exchange due to the following error: A2CE0100



Unfortunately the “View Troubleshooting Information” link is broken. So is the one on the top right in the console and the right-click one. As such it was hard to find any further details on this specific error.

I made a few attempts to get things working, including the following:
– Modifying the compliance policy (increasing the revision number)
– Removing and adding the user from and to the target collection
– Removing and recreating the deployment of the compliance policy

I can confirm none of the above resolves the issue. The policy still did not get applied.

In the end to get things working again what I had to do was to delete the compliance policy,  recreate it from scratch, and deploy it again.


When synching mail on the iPhone 5 a few minutes later, the policy kicked in.


Although the problem was solved and we now have a working demo scenario; in the end I have no idea what went wrong initially and how I could have been troubleshooting this in a more optimized way. Whatever it was it does not seem to resolve itself. Also the repeat count of the alert not increasing indicates the system itself does not do any retries.

I definitely see a few areas for improvement here:

  • Fixing the link to the troubleshooting information so the admin can troubleshoot properly and in a most optimized way.
  • Exposing Intune alerts to the Configuration Manager Console so the admin does not have to look in multiple locations.
  • Having the system retry the action “Saving of Access Rules” at least a few times. In case the alert repeat counter increases the admin can further look into a blocking issue. Otherwise there may have just been a glitch and the issue would have resolved itself.

If you are ever facing the same issue, I hope this article will save you some troubleshooting time!


Avatar of timdk

by timdk

ConfigMgr 2012 R2 Initial Updates Sync Fails: Failed to set Subscriptions on the WSUS Server

12:31 am in Configuration Manager by timdk

Recently I encountered an issue in my lab during the initial Software Updates synchronization. The sync failed and as a result no updates were available in Configuration Manager. This blog post describes the issue and how to resolve it.

The Issue

When examining the wsyncmgr.log the following entry is logged:

  • Sync failed: WSUS update source not found on site PS1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource


As indicated in the previous error log, more information was to be found in the WCM.log. This is a screenshot of that log file:


This particular entry was indicating something was failing with the Subscriptions:

  • Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error

The entry logged just before that one points us further into the right direction:

  • Subscription contains categories unknown to WSUS and SUP has no upstream server.~  Please either unsubscribe the unknown categories or import into WSUS an upstream package containing them.


The WCM.log entries refer to specific categories that are unknown – but do not specify any further details. I suspected there was an issue with the classifications and products that were enabled by default in the Software Update component configuration.

To work around this issue I followed these steps:

  1. Go to the Software Update Component properties and deselect all Products and Classifications which are enabled out-of-the-box.
  2. Force the Software Update Synchronization to run. Monitor the WCM.log and WsyncMgr.log to validate the synchronization is now running successfully. Note that no updates will be synchronized at this point, but the products and classifications catalog will be synched as part of the process.
  3. Enable the required Products and Classifications that were disabled previously, and run the synchronization again.
    Once I went through these steps the synchronization was working fine again:



Hope it helps!


Avatar of timdk

by timdk

Troubleshooting – How to pinpoint a problematic software update based on UpdatesDeployment.log entries

1:59 pm in Configuration Manager by timdk

Recently a customer of mine bumped into an issue when applying software updates during a Task Sequence. The first symptom that was noticed was that the task sequence was taking forever to complete. Looking further into this it turned out the task sequence  step during which the updates were applied was running for a very long time.

Further investigation of the log files was required and an entry in the UpdatesDeployment log is pointing us into the right direction.


The status ciStateError indicates there is a problem with this specific update. Further looking up the error code 87d00669 indicates there might a problem with the content. The real challenge now is to find which update it actually is that is causing this problem. All we have on it right now is the ModelName (Site_ / SUM_) without any further information.

We figured that using the Get-CMSoftwareUpdate cmdlet would be the quickest and easiest way to gather some more information and tried the following command:


Unfortunately this is not the case. The command itself seems to take forever to run and on top of that we ended up with a warning indicating the result exceeded the maximum size. Using Set-CMQueryResultMaximum we could probably overcome this … but as we don’t have an hour or more to wait for results we need another solution.

In comes WMI. Using PowerShell to query WMI is really easy, but alternatively you could also use WBEMTest or a 3rd party utility. We’ll go for the Powershell approach and  need the following information:

  • The namespace in WMI (using site_ABC where ABC is the site code)
  • The hostname of the SMS Provider
  • The actual WMI Query

The actual command is shown in the screenshot below. The result is returned in a second and we immediately have the required information of our problematic Software Update.


Hope this saves you some troubleshooting time in the future!



Avatar of timdk

by timdk

ConfigMgr 2012 R2 – Replication Issues after upgrading CAS

10:48 pm in Configuration Manager by timdk

Microsoft has just released more information and a resolution for a problem scenario in an SP1 CU2 or CU3 environment where child primary sites were entering maintenance mode after the Central Administration Site (CAS) had been upgraded to Configuration Manager 2012 R2.

Resolution Summary:

  • This issue has been resolved for all new System Center 2012 R2 Configuration Manager upgrades as of November 14, 2013. New installations or upgrades will download updated setup prerequisite files.
  • Customers that are working with site servers not connected directly to the Internet should use the Configuration Manager Setup Downloader.
  • Existing hierarchies that have already upgraded the central administration site but cannot upgrade child primary site(s) can be repaired by running a SQL script against the site database at the child primary site(s).

More details about the issue and the SQL script to fix existing hierarchies can be found here.

Avatar of timdk

by timdk

Configuration Manager 2012 Agent installation fails on a Management Point with CU3 installed

7:07 pm in Configuration Manager by timdk

When attempting to install the Configuration Manager 2012 client on a site system hosting the management point (MP) role and that site system has CU3 installed, the installation will fail.

To work around this issue you would have to:

  1. Uninstall the MP role first.
  2. Install the Configuration Manager client
  3. Reinstall the MP role.

More details are documented in the following KB article:

Hope this saves you some troubleshooting time!