While MDT is no longer being updated, and does not officially support Windows 11, it's still a great deployment solution and you can in fact deploy any Windows Client and Windows Server OS with it, including Windows 11.
The recommend method to inject drivers during deployment using MDT is called Total Control, which means you have one driver set per OS Family and Computer Model. In this post you learn to set up Modern Driver Management for MDT Lite Touch to create these sets in MDT Lite Touch.
Background
The Modern Driver Management solution from Maurice Daly and Nickolaj Andersen is primarily used for ConfigMgr OSD, but it also has support for importing drivers to MDT Lite Touch deployment shares.
Installation and Configuration
Installing the Modern Driver Management solution is easy. Simply download the Driver Automation Tool.msi from https://github.com/maurice-daly/DriverAutomationTool and install it on your MDT server with the default settings.
Note: For HP, Dell or Microsoft drivers you don't to install anything else, but if you want to support Lenovo models, you also need to install a required .NET component (Visual Studio 2015 Isolated Shell) from this link: https://visualstudio.microsoft.com/vs/older-downloads/isolated-shell. You have to login with either a Microsoft account or a GitHub account to download the setup file.
After installing the Driver Automation Tool (DAT), there are some basic settings you need to change for the MDT integration. In this example, my MDT deployment share was in the E:\MDTProduction folder, and MDT was installed to its default location in C:\Program Files\Microsoft Deployment Toolkit.
1. Using File Explorer, create a folder for the driver downloads, for example E:\Drivers. Then, in the Driver Automation Tool, in the Common Settings tab, type in, or browse to the folder you created.
2. In the Make & Model Selection tab, in Deployment Platform, select MDT. This will enable the MDT Settings tab, which is visible, but its settings are disabled by default.
3. In the MDT Settings tab, click the three dots, and browse to C:\Program Files\Microsoft Deployment Toolkit\Bin, then click Import PS Module.
4. You should now see your deployment share(s) in the lower pane, select your deployment share, and in the Folder Structure drop down list, select how you want the drivers structured. I prefer the OperatingSystemDir\Make\Model option.
5. Exit the tool, and in the C:\Program Files\MSEndpointMgr\Driver Automation Tool\Settings folder, make a backup of the DATSettings.xml file. Should the tool crash (which happens), and you lose any settings, you can just restore that file.

Using the Driver Automation Tool
In this section you find a few samples on how to download drivers for the different vendors.
Add Drivers for HP models
To add drivers for HP models, in the Make & Model Selection tab, select the operating system you want drivers for, including the version, like Windows 10 22H2. Then select the HP manufacturer and click Find Models.
Note: HP are labeling their drivers to which operating system version they support.
Then select one or more models, and select Start Download | Extract | Import. In this example I selected a ZBook Firefly model and an Elite Mini 800 desktop model.

After the Start Download | Extract | Import process is completed, you should see the drivers in the Deployment Workbench.

Add Drivers for Dell models
To add drivers for Dell models, in the Make & Model Selection tab, select the operating system (only) you want drivers for, like Windows 10. Then select the Dell manufacturer and click Find Models.
Note #1: Unlike HP, Dell does not label their drivers to which operating system version they support, only the main OS (Windows 10 / Windows 11). So, you'll basically have to test that in your own environment.
Note #2. A few times the tool failed to extract the Dell packages, so I had to do that manually, and then import the drivers. This seem to be an MDT Lite Touch only issue, when using the tool for ConfigMgr, I haven't seen these issues.
Then select one or more models, and select Start Download | Extract | Import. In this example I selected a Latitude 5320 model and a Latitude 3120 model.

After the Start Download | Extract | Import process is completed, you should see the drivers in the Deployment Workbench.

Add Drivers for Lenovo models
To add drivers for Lenovo models, in the Make & Model Selection tab, select the operating system (only) you want drivers for, like Windows 10. Then select the Lenovo manufacturer and click Find Models.
Note #1: Lenovo, label their drivers to which operating system version they support (for example, Windows 10 22H2), as well as the main OS (Windows 10 / Windows 11). I recommend going for the exact version if possible.
Then select one or more models, and select Start Download | Extract | Import. In this example I selected a ThinkPad X1 Carbon model and a ThinkCentre M70S model.

Add Drivers for Microsoft models
To add drivers for Microsoft models, in the Make & Model Selection tab, select the operating system and version you want drivers for, like Windows 10 21H2. Then select the manufacturer and click Find Models.
Note: Microsoft are labeling their drivers to which operating system version they support, but the latest Windows 10 version listed is currently 21H2 (not 22H2).
Then select one or more models, and select Start Download | Extract | Import. In this example I selected a Surface Laptop 5 model and a Surface Pro 9 model.

After the Start Download | Extract | Import process is completed, you should see the drivers in the Deployment Workbench.
I tried to edit my original comment that is awaiting approval, but got an error saying it's no longer available for editing. I'm going to repost that comment along with my addition. Maybe you can delete or not approve the first one. Hopefully this can help someone. I wasted a lot of time trying to get this working for Lenovo. I am not impressed. =========== The Lenovo part needs some work. I logged in with a Microsoft account, and it takes me to a subscription page with no option for download. This tool is useless to me as all of… Read more »
Hi Matt,
Thank you for providing the links, I'll update the post with better instructions for Lenovo, and I'll reach out to Maurice to see if anything can be done in the DAT tool itself to improve the Lenovo models.
The Lenovo part needs some work. I logged in with a Microsoft account, and it takes me to a subscription page with no option for download. This tool is useless to me as all of my computers are Lenovo, and the DAT software isn't usable without this isolated shell component.
In a large global business, driver management is tricky. This is because, over time, the driver repository requires extremely large amounts of storage. Replicating this amount of data to what may be dissimilar servers with dissimilar storage capacities brings challenges to managing older drivers. How do Deployment Research gurus manage this? For example, imagine a new MDT infrastructure has been setup and drivers have been imported for Windows 10 20H2 for many different computer models. And the data has been replicated to dozens of servers around the world – utilizing DFS-R. Later, new drivers need to be added, not because… Read more »
MDT is not the best platform for that scenario. ConfigMgr, and using drivers as WIM packages, takes care of these issues quite nice. For the PSD extension to MDT – https://github.com/FriendsOfMDT/PSD – We implemented a similar solution using WIM files for the driver packages. Shouldn't be too hard to port over to regular MDT, but since Microsoft stopped any development of MDT for three years now I'm not sure if it's worth the effort. If you would be willing to work with me on it, so I can get some testing help, please reach out to me on LinkedIn: https://www.linkedin.com/in/jarwidmark/