IT Diary (Dec 2020)

How long are Status Messages being kept before the Maintenance Task “Delete Aged Status Messages” removes them?

Maintenance Tasks that delete aged data allow you to set the time for which the specific information shall be kept (Delete data that has been inactive for … days). Why is Delete Aged Status Messages the exception?

If you look at the database table StatusMessages, you find a column DeleteTime.

The Maintenance Task triggers a Stored Procedure called sp_DeleteAgedStatusMessages that does the cleanup job. To determine what to remove it checks DeleteTime.

So the last question is how long Status Messages are being stored. The answer is 30 days, but the exception are messages that were created by user inactions with the console (Component: Microsoft.ConfigurationManagement.exe). They might be audit-relevant and have a lifetime of 180 days. To validate, run

select Component, Time, DeleteTime, DATEDIFF(DAY, Time, DeleteTime) as DiffInDays from StatusMessages

Windows Store for Business synchronization in ConfigMgr fails

Problem: The WSfB synchronization fails and in the WsfbSyncWorker.log you find these entries in a 30 min interval:

Failed authenticate with the Windows Store for Business.

Exception: [Microsoft.ConfigurationManagement.ApplicatonManagement.Wsfb.Sync.WsfbAuthenticationException: Object reference not set to an instance of an object.

Cause: The cause is probably that you didn’t activate the connection in the Store for Business portal. To do so, log in to and
open Manage->Settings->Distribute. Click on Add Management tool and select the App that you created earlier in ConfigMgr when configuring the MSfB in Azure Services. Finally, press activate, relax and wait for the next sync.

Task sequence has failed with the error code 0x800705aa

This means you have “insufficient system resources”. If you are using Hyper-V, increase the minimum memory value (512 MB by default)