Archive

Archive for the ‘System Center Configuration Manager’ Category

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

Advertisements

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

ConfigMgr 1606 – Unable to modify language configuration

September 1, 2016 Leave a comment

When running Configuration Manager current branch 1606 you might run into a situation where you cannot modify the language configuration of a site. The option is simply greyed out, preventing you from adding any client or server languages.

image

The reason to why this is happening can be found in the ConfigMgrSetupWizard.log (hat tip to fellow MVP Roger Zander for pointing this out). Here we see an entry indicating that setup detected that client piloting is enabled for the site and as a result the modify language configuration option will be disabled.

image

So if we want to make any language modifications we need to promote the pre-production client to production first. This can be done in the administration workspace in the updates and servicing node.

image

Once the previous step is completed we can run the Setup Wizard again and in Site Maintenance the modify language configuration option is no longer greyed out. Adding client and server languages is possible.

image

 

Conclusion: you cannot change the language settings as long as the pre-production package has not been promoted.

The underlying reason for this is that we cannot apply language pack MSP files for the newer client to an older client version. When in piloting mode the new binaries have been updated everywhere, except for the client folder for production. Adding new client language packs would copy the newer language pack MSP files from cd.latest to the client folder that still has an older client version. These language pack files are not compatible with that older client – and as a result would be deleted.

Hope it helps!

Tim

ConfigMgr 1606 Feature Highlight – Pre-release features consent

August 2, 2016 Leave a comment

Time for another feature highlight in Configuration Manager Current Branch (CB) 1606. For this post we will focus on the pre-release feature consent which is required as of update 1606.

As you will learn later in this post this just requires you to tick one single checkbox but before doing so there are some important things (and consequences) to take into account.

What are pre-release features?

As stated by Microsoft : Pre-release features are included in the product for early testing in a production environment, but should not be considered production ready. Also – according to the docs -  there is no guarantee these features will be stamped production ready – there is a chance they never evolve beyond the pre-release state.

In the updates and servicing node the feature type column will indicate whether a feature is pre-release or not.

image

Note 1: yes – I did also notice the anomaly with the Conditional Access for Managed PC’s feature. Not sure why the name indicates pre-release and the feature type says release.

Note 2: the Windows Store for Business Integration feature is listed as a release feature but you cannot enable it. Bottom line: it behaves like a pre-release feature so you can only enable it if you have giving consent to pre-release features.

 

How to give consent to use pre-release features?

Giving consent is done through the hierarchy settings as shown in the screenshot below.

Important: this is a one time action which cannot be undone. Once enabled the entire section of the dialog box is greyed out – you can not uncheck the box.

image

Once you have given consent you can enable pre-release features in 1606  from within the Updates and Servicing node. For future releases this can then also be done through the wizard when you are actually installing the update

What happens if we do not give consent?

When installing an update in the future, the pre-release features will be visible in the Updates and Servicing Wizard but will be greyed out. They cannot be enabled.

Once the update is installed the pre-release features will be visible as well – but we cannot turn them on until consent has been given in the hierarchy settings. This is shown in the screenshot below.

image

 

That’s it for this feature highlight – up to you to decide whether or not to enable this in your production environments.

Until next time!

Tim