A few days ago, we experienced performance issues when querying a ConfigMgr DB view. A very simple query: “SELECT Name, MachineID, IsActive, AADDeviceID FROM v_CombinedDeviceResources WHERE CoManaged = ‘1’” could take up to a minute to complete. Since we already knew that “v_CombinedDeviceResources” is the source from where the Device view in the ConfigMgr console…
Author: Johan
BitLocker Administration Service in MEMCM
Starting in ConfigMgr Current branch 1910 integrated BitLocker management (MBAM) is supported. This is all well and fine except one detail; it does not include the Administration Service Endpoint available in MBAM standalone. This endpoint is, most cases, crucial if you are using any kind of automation, management system, custom helpdesk tool or such. This…
Distribute Drivers at Mach speed
This is a report from the “Onevinn utility research kitchen” where we have spent a few days contemplating and testing driver distribution during OSD. Driver distribution appears to be the talk of the town and new solutions keep popping up at a high rate. Most of these solutions target bandwidth utilization and involves distributing compressed…
How to provision a modern application during OSD
This solution is not universal; complex applications with tons of dependencies or that is bound to user profiles will not work, but it covers the most basic needs of installing for example driver related applications, like the one in this example. A customer of ours have a great number of machines with Nvidia graphics adapters…
TSBackground for ConfigMgr
Do not miss this eye candy, TSBackground for ConfigMgr, that also adds security to your deployments. We are all familiar with the ConfigMgr standard TSProgresUI, which makes a great job but perhaps is not so aesthetically appealing. TSBackground is the successor of “OSDBackground” that we published a couple of years ago. This new version addresses…
Apply native Driver packages dynamically using Driver Manager
Another great tool and post by my colleague Johan Schrewelius! A while ago we had a customer whose Task Sequence suddenly exceeded the maximum allowed size, mainly because of a vast number of “Apply Driver Package” steps. To remediate the issue, we looked at several different solutions to apply driver packages dynamically. It turned out…