Archive

Archive for the ‘Configuration Manager’ Category

Upgrade Readiness Integration and ConfigMgr Current Branch 1810 upgrade – beware of inbox flooding

April 16, 2019 Leave a comment

Are you planning to upgrade to Configuration Manager Current Branch 1810 and actively using the Upgrade Readiness integration feature? Then this blog post might save you some headaches later on.

Shortly after upgrading to Configuration Manager Current Branch 1810 last week, a customer reported the volume on the site server rapidly filling up. Further research indicated a large amount of files were dropped in one of the inboxes: %ProgramFiles%\Microsoft Configuration Manager\inboxes\hman.box\CFD

Looking into these files further pointed to a potential issue with the Upgrade Readiness integration, which was enabled in this particular environment.

The dmpdownloader.log indicates the Upgrade Analytics download interval is set to 0 and running continuously.

image

In the meantime Microsoft has published KB4498259 confirming this is a known issue with Current Branch 1810. The fix comes with the 1902 release and in the meantime a workaround is to (continuously) set the download interval in the registry.

More details in the KB article here.

Hope it helps.

Tim

Third Party Software updates not installing during Task Sequence

January 14, 2019 Leave a comment

As of Configuration Manager Current Branch 1806 it is now possibly to natively subscribe to third party software catalogs and deploy third party updates. There is no longer a need for System Center Updates Publisher (SCUP).

Currently there is one shortcoming in the feature: regular deployments of third-party updates are working fine, but when using the Install Software Updates step in an OSD Task Sequence the third-party updates are not installing. This may go unnoticed as the Task Sequence does not error out.

Initial investigation shows this is most likely because of the WSUS signing certificate only being installed on the client when Software Updates client policy lands after the task sequence has completed.  This is logged in the UpdatesDeployment.log :

image

As a result the third-party updates cannot be installed during the task sequence.

From a security perspective most organizations will want their devices fully patched before they leave the deployment bench. Also from an end-user experience perspective the experience is suboptimal when booting your new device for the very first time … just to have it install new updates (and potentially reboot).

Hopefully we will see this fixed in an upcoming release of Configuration Manager – to help speed up the process and make sure this gets some attention, please make sure to vote up this entry on User Voice.

Thanks – and until next time.

Lowlands Unite Belgium Edition–Debrief

October 24, 2017 Leave a comment

Just a quick blog post to share the slides from my new blips on the radar session at Lowlands Unite Belgium last week.

Thanks to those who attended – in case you have any further questions or feedback make sure to leave them in the comments. I will get back to you as soon as possible.

Link to Slideshare.

Also check out this Sway looking back at Lowlands Unite Belgium Edition 2017.

Looking forward to the next edition in 2018!

Tim

Lowlands Unite Belgium Edition Speaker

October 17, 2017 Leave a comment

LLUnite_BEIn two days we are ready to kick off the second leg of Lowlands Unite for this year. The event will take place at Lamot in Mechelen, Belgium.

Similar to the Netherlands edition there will be two tracks: one for EMS / ECM and one for CDM / Security. I will be presenting in the first track.

Based on the current agenda I will be kicking off the day and during my first session I will be flying solo. The objective of the session is to give an overview of the latest and greatest in the world of Configuration Manager. Additionally I will talk about the modern management capabilities that can be considered also.

For my second session in the afternoon I will be joining Kenny Buntinx for a presentation on servicing your workplace (like a boss). Here we will talk about servicing challenges Windows 10 brings into your environment and how you can tackle them.

For this event we will be joined by two international MVP’s: Ronni Pedersen and Mirko Colemberg, plus a special guest from Microsoft in Redmond: David James. David is the director of development of the Configuration Manager team. Belgium is the fourth stop of his European Tour visiting different user groups. This a unique opportunity which you honestly cannot afford to miss.

Interested in joining us? It’s not too late : registration ends in approximately 24 hours and there are still a few seats left. More information and registration here.

Adding languages for Office 365 update downloads in Configuration Manager only adds the first language

October 13, 2017 Leave a comment

During a recent customer visit I was asked to troubleshoot an issue with Office 365 language specific updates. This blog post outlines my findings and the solution.

The customer is running a Current Branch 1706 environment and needs to support Dutch and French languages for Office 365, next to the default English language. As such he wants to ensure all updates for these three languages are properly downloaded. To achieve this the engineer is following the procedure as documented here.

Background

Let’s first have a look at what is documented the TechNet Docs.

Beginning in Configuration Manager Current Branch 1610, you can add support for Configuration Manager to download updates for any languages that are supported by Office 365, regardless of whether they are supported in Configuration Manager.

The documentation contains a detailed procedure on how to add support to download updates for additional languages. This is done through WMI.

Configuring additional Office 365 update languages is a site-wide setting. After you add the languages using the procedure, all Office 365 updates are downloaded in those languages, as well as the languages that you select on the Language Selection page in the Download Software Updates or Deploy Software Updates wizards.

 

 

Initial findings

As the customer did not want to select the additional languages in the Software Updates wizard each month he opted for the site-wide setting and required modifications. As per the outlined procedure the required changes were made in WMI.

Notice in the screenshot below the values are specified exactly as per the screenshot in the TechNet Documentation.

clip_image002

Based on these settings the updates for Dutch and French should be downloaded. English does not have to be specified and is always downloaded. However, when checking the sources in the Software Update Deployment Package, only English and French updates have been provisioned. Dutch is missing.

clip_image004

During a second test the language tags in WMI were switched, so Dutch was first in the list.

clip_image005

After the download completed the Software Update Deployment Package source folder only contains English and Dutch updates. French is missing.

clip_image007

It appears as if only updates for the first language specified are being downloaded.

A few runs later (going through some variants with delimiters etc.) we tested with the following values in WMI

clip_image009

After the download completed we checked the Software Update Deployment Package source folder again – and finally updates for all three languages are properly provisioned.

clip_image011

 

 

Conclusion

The screenshot in the TechNet documentation is misleading as the language tags are separated with a comma and a space. Based on our above findings the language tags should be separated with a comma only, the space should be omitted for this to work when specifying multiple languages.

Side note: the TechNet documentation also mentions Use the following procedure on the software update point at the central administration site or stand-alone primary site. This is not correct as the procedure needs to be executed on the site server, not the SUP.

Hope it saves you some troubleshooting time!

Tim

ConfigMgr 1706 – BgbServer.log expecting more data from client errors

September 29, 2017 2 comments

After upgrading a Configuration Manager Current Branch environment to 1706 you may notice a lot of Expecting more data from client errors in the BgbServer.log .

This log records the activities of the notification server such as client-server communications and pushing tasks to clients. It also records information about online and task status files generation to be sent to the site server.

20170928-BGBServer

Feedback from Microsoft indicates this is related to the client not sending the final packet via TCP channel somehow or when the ccmexec service on the client restarts. The good news is that these events are harmless and are not impacting any functionality.

Logging improvements in future releases should fix this and avoid BgbServer.log from turning red.

Hope it helps!

Tim

*** Update 20/10 ***
I logged a case for this with Microsoft (ID 3141726) which changed status to Resolved just now. Expect this to be fixed in the next CB release.

ITDevConnections – Session Debrief – The right steps to the right upgrade path from ConfigMgr 2012 and Server 2008

October 14, 2016 Leave a comment

As promised a quick debrief on our ITDevConnections session about upgrading your Configuration Manager infrastructure and all related components.

Here are a couple of articles and tools we brought up:

Thank you for attending the session and make sure to leave feedback!

Until next time.

Tim