Archive

Posts Tagged ‘ConfigMgr’

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.

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 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

ConfigMgr 1606 Feature Highlight – Software Center improvements

July 27, 2016 6 comments

Time for another quick feature highlight and this time I would like to focus on the client side of things. With version 1606 the Software Center also has some nice new improvements – lets have a look into what has changed:

1 – Installed Software merged into Installation Status

Prior to version 1606 there was a tab named Installed Software. This tab is no longer visible on the new client. Instead the information related to installed software is merged into the Installation Status tab.

This is what it looks like on a lab Windows 7 client not yet upgraded:

image

And this is what an upgraded Windows 10 client looks like:

image

 

2 – New tabs for Updates and Operating Systems

Prior to 1606 Applications, Updates and Task Sequences were all listed under the Applications tab. This has now been properly split as two new tabs for Updates and Task Sequences have been added.

image

 

3 – Installing multiple updates

Multiple updates can now be selected for installation or by using the Install All button all updates can be installed in one single click.

image

 

4 – Applications List view

In older versions the applications tab only supported a tile view – although this is nice it can be rather annoying in the scenario where you have a large set of applications. As of 1606 you can now toggle between list view and tile view.

An example of the list view from our lab:

image

 

This last one was actually a request I had filed on UserVoice in February and it is really nice to see how fast this made it into the product. This is just one example but it shows the importance and relevance of logging any feature requests and feedback on UserVoice.

Until next time!

Tim

ConfigMgr 1606 Feature Highlight – Updates and Servicing View cleanup

July 25, 2016 Leave a comment

After my earlier post on the 1606 update process I have been exploring some of the new features in this build. A small yet nice change in 1606 is the cleaning up of the Updates and Servicing view.

With this release you will see only the most recently installed update and any new updates that are available for installation. The older entries will no longer be listed.

So after just installing 1606 in our environment it looks like this:

image

And what if we want to know what path this site has followed to come up to this level? Easy – just hit the history button and the answer to that question pops up:

image

Note : this only becomes available after your console has been updated also! If you still run an older version of the console you can simply close and then restart it to trigger the update process.

Until next time!

Tim