PXE booting into Windows PE and using Imagex to capture a computer to a WIM file that is saved to a network folder.

The entire process works great and it saves the WIM to the network folder I want just fine, however...

The issue I have is when I'm on my workstation (Windows 7) and I go to mount that WIM file using DISM, I get the following error:

Error: 1340
The inherited access control list (ACL) or access control entry (ACE) could not be built.

Here is a dump of the log file created:

2010-06-15 15:50:51, Info                  DISM   PID=2604 Scratch directory set to 'C:\Users\dockesa\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir

2010-06-15 15:50:51, Info                  DISM   PID=2604 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Getting Provider DISMLogger - CDISMProviderStore::GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Getting Provider DISMLogger - CDISMProviderStore::GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Manager: PID=2604 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Getting Provider DISMLogger - CDISMProviderStore::GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM.EXE: 

2010-06-15 15:50:51, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->

2010-06-15 15:50:51, Info                  DISM   DISM.EXE: 

2010-06-15 15:50:51, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7600, Running architecture=amd64, Number of processors=2

2010-06-15 15:50:51, Info                  DISM   DISM.EXE: Executing command line: "C:\Windows\system32\Dism.exe"  /mount-wim "/wimfile:\\fileserv-e\images\wims\User Backups\Sand_061510.wim" /index:1 /mountdir:c:\tmp

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Loading Provider from location C:\Windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:50:51, Info                  DISM   DISM Provider Store: PID=2604 Loading Provider from location C:\Windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:50:52, Info                  DISM   DISM Provider Store: PID=2604 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2010-06-15 15:50:52, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

2010-06-15 15:50:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager

2010-06-15 15:50:52, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.

2010-06-15 15:50:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager

2010-06-15 15:50:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

2010-06-15 15:50:52, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager

2010-06-15 15:50:52, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.

2010-06-15 15:50:52, Info                  DISM   DISM Provider Store: PID=2604 Getting Provider WimManager - CDISMProviderStore::GetProvider

2010-06-15 15:50:52, Info                  DISM   DISM Provider Store: PID=2604 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2010-06-15 15:51:03, Error                 DISM   DISM WIM Provider: PID=2604 Failed to mount the image. - CWimImageInfo::Mount(hr:0x8007053c)

2010-06-15 15:51:03, Error                 DISM   DISM WIM Provider: PID=2604 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:999 - CWimManager::InternalOpMount(hr:0x8007053c)

2010-06-15 15:51:03, Error                 DISM   DISM WIM Provider: PID=2604 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2247 - CWimManager::InternalCmdMount(hr:0x8007053c)

2010-06-15 15:51:03, Error                 DISM   DISM WIM Provider: PID=2604 Error executing command - CWimManager::InternalExecuteCmd(hr:0x8007053c)

2010-06-15 15:51:03, Error                 DISM   DISM WIM Provider: PID=2604 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:516 - CWimManager::ExecuteCmdLine(hr:0x8007053c)

2010-06-15 15:51:03, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.

2010-06-15 15:51:03, Info                  DISM   DISM.EXE: 

2010-06-15 15:51:03, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

2010-06-15 15:51:03, Info                  DISM   DISM.EXE: 

2010-06-15 15:51:03, Info                  DISM   DISM Image Session: PID=2604 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect

2010-06-15 15:51:03, Info                  DISM   DISM Provider Store: PID=2604 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider

2010-06-15 15:51:03, Info                  DISM   DISM Provider Store: PID=2604 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

2010-06-15 15:51:03, Info                  DISM   DISM Provider Store: PID=2604 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2010-06-15 15:51:03, Info                  DISM   DISM Provider Store: PID=2604 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider

2010-06-15 15:51:03, Info                  DISM   DISM Provider Store: PID=2604 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

I've tried re-imaging the computer, mounting it on a different computer, GImageX, run chkdsk before imaging, turn the /check flag on/off, disabled compression, but nothing seems to make a difference.

A Google search tells me nothing and from the best of my knowledge it looks like it's a Windows permission error??? I'm running as an admin too.

The machines I'm imaging are Windows XP SP3 machines and it happens to almost all that I encounter.

Any thoughts or ideas?  Thanks!

Hi,

I am using MDT 2010 Update 1 and I am having a little issue the %WDSServer% variable to beeing resolved in the customsettings.ini.

---------------------

[Settings]
Priority=UserID, GetComputerNameByNetbootGuid, Default
Properties=MyCustomProperty


[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES


[GetComputerNameByNetbootGuid]
WebService=http://%WDSServer%/MDT_GetNamefromGuid/gethostnamenetbootguid.asmx/gethostnamefromnetbootguid
Parameters=UUID
UUID=netbootGUID
OSDComputerName=string

--------------------------

In the web service call the %WDSServer% is not getting resolved and thus fails.

Does anybody has an idea how i can use %WDSServer% for the web service?

Thanks and regards,

Dominik

When the UDI Task Sequence finishes, a final "Deployment Complete" window is shown with three tabs (Welcome, Deployment Summary and Applications Installed) and a Start Windows button at the bottom. When I click on the "Applications Installed" tab, all applications have a yellow warning indicating "Install State Unknown" even though every application installs successfully without any errors in the logs. Also there is no SuccessOrFailureCode shown when expanding each application. These same applications install fine via normal deployments (post imaging) and using standard Task Sequences (Install Application step).  

Hi everybody,

I need help to activate the TPM with MDT on a Dell laptop there's different procedure with Dell CTTK.

I have followed this procedure : 

<malware link removed>

I have generated the scripts but I don't know what I have to do with it, If I execute manually the 2 SCE files it doesn't work the TPM is not activate

Thank you

Posted this in the Windows 10 install forums and didn't get any bites. Hoping maybe someone here has ran into something similar and can help. 

Ive been putting the final touches on our Windows 10 deployment using MDT 2013 Update 1. One of the last items I can't figure out is how to completely disable windows smart screen and adjust DPI. 

I sysprepped my image using OOBE and set up all my copy profile settings. During this, I disabled Smart Screen from Settings > Privacy. When I was finished and I started building out the rest of the image in my VM, I disabled it during Windows Welcome as well. We are testing several devices including Surface Books. One of the startup items for Surface Books is SurfaceDTX.exe which is more or less just an application that pops up and tells you if its ok to detach the screen or not. Despite disabling everything above, when we deploy Windows 10 to a Surface Book and log in to a domain user account we immediately get a pop up that SurfaceDTX.exe is being checked by Smart Screen and Smart Screen can't connect to Microsoft right now. We DO have Smart Screen blocked at checkpoint here - not my call, thats info security's decision. 

I should add this is just one example - I have had other instances where other applications provide the same error during everyday use so just disabling SurfaceDTX.exe is not an option. We also don't want people trying to rip the tablet off before its ok. So what am I missing?

The other issue is that when imaging the Surface Book the display settings are always set to 300% zoom after a user logs in. I can go into display settings and turn scaling off and its fine. Just an annoyance that I would like to automate a fix for. 

Thanks!!!

Let me first explain how i work.

I have VM's where i install windows/updates and some programs.

Then i take a clone of that machine and i run the capture windows through the litescript, and i create a custom .wim file

Then i import the new wim file in MDT and change my tasksequence that it installs the new wim file.

Then i delete the cloned VM as it is sysprepped.

When there are a lot of updates, i start my vm, update windows and make changes if necessary.

Then i clone it again and create a custom wim file

then i import it again in mdt and change my tasksequence.

This always worked, untill my latest updated wim file

When i assign my latest wim file in the tasksequence it hangs on 54% completion and becomes unresponsive in the mdt monitoring.

When i look at the computer where i wanted to deploy the image, the OS has been installed, but it didnt join the domain(which is the next step) and the local admin account is disabled for some reason.

When i assign my previous wim file to the tasksequence everything works again. the installation is 100% complete, it is in the domain, local admin acount is enabled, and all other programs i install with the tasksequence is without fault.

So i am guessing something is wrong with my wim file or i did something wrong in the VM i updated, bu ti have no idea, what i did different then all other times.

Afternoon all, I hope everyone is well.......

I have come across an issue that I hope some delightful person can help me resolve.

Though we have access to Win10 Ent - I have only tentatively played around creating images using it and then mostly in SCCM.

I normally create the images using MDT,  just easier , less fuss.

So I deployed Windows 10 Enterprise x64 to a bare metal PC using MDT3012 U2. My tech installed all the required software and updates. then we created a new task sequence to sysprep and capture the image which will then be imported into SCCM.

However though the process starts off well when it gets to doing the sysprep it just stops without bringing up the sysprep dialogue box.

I can find no logs or anything in event viewer.............I thought initially that maybe during the customisation of the image something was broken.

So I again deployed a base Windows 10 Enterprise x64 image to another bare metal PC - then pretty much initiated a sysprep and capture - it failed in the same way.

So I initiated a standard task and successfully captured the image but without syspreping. Lastly I manually kicked off the sysprep process directly from within its folder on the PC - that worked too.

So though all the components work individually I can not get them to work in unison under a sysprep and capture task.

Any help is really really appreciated....

EDIT - critics aside, it is now working.

Hi everyone,

I'm having some problems setting tasksequence variables in PowerShell. After a reboot the variable is gone. I'm using this approach in a Powershell script during deployment. E.G.:

$TSenv:CustomVariable='Some Value'

The variable is now usable throughout the script. However, I make use of the SMSTSRebootRequested and SMSTSRetryRequested variables to reboot and retry the script depending on some conditions and after the reboot the variable is either gone or has no value. I check for the existence of the variable at the beginning of the script, like so:

If($TSEnv:CustomVariable){<Run second run script>}else{<Run first run script>
    If ($RebootRequired)
    {
    $TSEnv:CustomVariable='Some Value'
    $TSenv:SMSTSRebootRequested= $true$TSenv:SMSTSRetryRequested= $truereturn"Continue after reboot."
}}

Can anyone explain why this doesn't work? I have MDT 2013 U1 and I'm not using SCCM.

Dear all,

I'm having a problem while trying to customize my Windows 7 installation.

I would like to add a customized Desktop Wallpaper to my Windows 7 images by using MDT but I did not find an easy way to do that.

One would be via group policy but we would like to avoid that. I was thinking, instead, that we could insert some kind of script in the task sequence that copies our Desktop image on the machine (C:\Windows\Web\Wallpaper) and then sets it as the default Desktop Wallpaper for all users.

Do you guys have any idea on how to achieve this result? So far I have found strange solutions but I would like to receive some other help in order to tidy up my mind and see if the thing is feasible.

Thanks in advance for your help!

Daniele Malerba

I was wondering if anybody run into this issue and could point me in the right direction.

I have been using MDT for over 4 years and last week was the first time that I have ever seen this "FAILURE ( 7706 ): ERROR! Drive D: was not found!" message. I'm running a MDT 2013 deployment server with AIK 8.1 and this error occured while imaging a Surface Pro 3.

We successfully imaged about  +10 Surface's with this MDT build however they all had 128GB SSD's and and 4GB of RAM this one that failed has a 256GB SSD and 8GB of RAM and the issue was replicated on another Surface with the exact same specs.

So far I have;

1) Tried another Surface Pro 3 of the same SKU and it had the exact same issue.

2) Successfully imaged this Surface with Windows 10 and with the Windows 8.1 Pro Surface Pro 3 recover image from Microsoft using USB media.

3) Updated my deployment share to MDT 2013 Update 1 and AIK 10 and tried both the original MDT 2013 standard deployment Task Sequence and the updated MDT 2013 standard deployment Task Sequence both modified for Surface Pro 3 (Driver Firmware, patches etc...)

4) Updated the Surface Pro 3 driver set with the very latest drivers but I noticed that even the latest drivers still uses the Intel ahci 8 driver from 2013 that the worked fine on the other 128GB SSD 4GB RAM Surface Pro 3 SKU's that we imaged before.

When looking at the BDD.log I can see that SSD drive is successfully cleared of any existing partition but it fails to create any partitions and after it fails in WinPE if you manually run Diskpart no drives seems to be available even though driver for the storage controller should still be loaded.

I have done a lot of research and I have found similar issues but none of the solution suggested has solved this issue and I'm running out of things to try.

Here are some of the Logs Files, let me know if any others are required;

https://onedrive.live.com/redir?resid=3fd6cdd8cde1b711!114&authkey=!APd0_2xdY_3izhQ&ithint=file%2cLOG
https://onedrive.live.com/redir?resid=3fd6cdd8cde1b711!115&authkey=!AIQSsEoJ0LBvCZE&ithint=file%2clog
https://onedrive.live.com/redir?resid=3fd6cdd8cde1b711!116&authkey=!AD6FuNbGaKVTpW4&ithint=file%2clog

Thanks in advanced.

Before I upgraded to MDT 2013 U1 from Vanilla MDT 2013, I had successfully modified the "DeployWiz_SelectTS.vbs" which essentially reran the ZTIGather.wsf.

After upgrading to MDT 2013 U1 and then U2, this has now broken.

Has anyone figured out how to have customsettings based off of Task Sequences?

Here is the reference that I used to make it work in the past.

https://social.technet.microsoft.com/Forums/en-US/e17a1952-d1f7-41ef-8231-0d6fcc41882e/mdt-2012-settings-per-task-sequence?forum=mdt

Hello everyone,

We have 2 OS : french and english.

Within a Taskseq, we have 2  Operating systems: English and French. In MDT/Database/Computer we give a Role to each Computer. This Role is given as Options: UserLocale equals the keyboard layout. So if it's fr-ma, then it should install the French Os. And that goes wrong. It will always install the English OS. It is normal, cause the unattend.xml is default English OS.  What is the best way to do. Read in some papers it is not good to have 2 Os in your TS. Who has some tips. tanx Rik

Hi,

Is there any way I can update to windows 10 and remove the store apps.

My tasks in the post processing section don`t get run and I get the final summary straight after its updated the OS before reboot.

Hello Everyone,

I'm trying to capture Windows 10 image through MDT 2013 Update 1.
I added a suspend action to install update/customize the desktop/etc... Everything went perfectly fine I customize the desktop etc while I was doing windows update computer wasn't responding I restarted the computer and suspend action resumed by itself and it captured the image, again without any problem. (0 errors, 2 warnings)

I was doing the same thing (mentioned above) with windows 7 and suspend action DO NOT get resumed by itself until I click on the icon it doesn't matter how many time I restart.

I want to know is there anything which has changed or needs to be configured so the suspend action doesn't get resumed.

Kind Regards,

Farooq

Hello,

Problem:

MDT 2012 Update Rollup 8 (6.3.8330) failed to deploy using the default server task sequence (server.xml) to a computer using a BIOS (MBR disk) if the disk is greater than 2TB in size.  The deployment will fail during the "Installing Operating System" phase.  When, after the failure, I looked in the DISM.LOG file (Press F8 at the error window to launch a CMD prompt, view / copy C:\Windows\Logs\DISM\dism.log) I saw errors including the following:

2016-01-21 13:58:27, Error                 DISM   DISM WIM Provider: PID=1200 [CreateDestinationFileEx:(3324) -> SetFileSize failed] C:\Windows\assembly\NativeImages_v4.0.30319_32\System.ServiceModel\673e962beaf835de9a3660ea255d2a5e\System.ServiceModel.ni.dll (HRESULT=0x80070070) - CWimManager::WimProviderMsgLogCallback

[1200] [0x80070070] RestoreFileNodeList:(2122): There is not enough space on the disk.

[1200] [0xc144012e]

2016-01-21 13:58:27, Error                 DISM   DISM WIM Provider: PID=1200 C:\Windows\assembly\NativeImages_v4.0.30319_32\System.ServiceModel\673e962beaf835de9a3660ea255d2a5e\System.ServiceModel.ni.dll (HRESULT=0x80070070) - CWimManager::WimProviderMsgLogCallback

[1200] [0x80070070] RestoreFilesCallback:(3638): There is not enough space on the disk.

[1200] [0x80070070] EnumImageDataEntries:(1047): There is not enough space on the disk.

[1200] [0x80070070] GetImageErrorCode:(2833): There is not enough space on the disk.

[1200] [0x80070070] GetImageErrorCode:(2833): There is not enough space on the disk.

[1200] [0x80070070] ImageWorkerThread:(187): There is not enough space on the disk.

[1200] [0x80070070] ImageWorkerThread:(187): There is not enough space on the disk.

[1200] [0x80070070] RestoreAllData:(985): There is not enough space on the disk.

[1200] [0x80070070] WIMApplyImageInternal:(704): There is not enough space on the disk.

When in the CMD prompt I ran DISKPART, and:

LIST DISK

SELECT DISK 0

LIST PARTITION

LIST VOLUME

I saw there were only two partitions.  The C: drive was only 500MB, followed by the Recovery partition which was about 2TB.  This was although according to the default server task sequence the System Reserved partition should be 500MB, followed by the Windows partition C: which should be 99% of the remaining available space, followed by the Recovery partition.

Cause:

As far as I can tell, Windows only supports addressing MBR disks up to 2TB in size.  The MDT scripts do not take this limitation into account, and using the defaults in the server.xml task sequence will try and create a partition larger than 2TB, which fails.

Solution:

In the following script:

\\wds\DeploymentShare$\Scripts\ZTIDiskpart.wsf

On line 408 I replaced the following:

        '//----------------------------------------------------------------------------

        '//  Create Partitions from Table

        '//----------------------------------------------------------------------------



        iRemainingSize = oDisk.oWMI.Size / 1024 /1024

        iExtendedRemainingSize = 0



        '

        ' Enumerate through all partition entries

        '

with:

        '//----------------------------------------------------------------------------

        '//  Create Partitions from Table

        '//----------------------------------------------------------------------------



        iRemainingSize = oDisk.oWMI.Size / 1024 /1024

        If not isUEFI and iRemainingSize > 2 * 1024 * 1024 then

            ' The maximum addressable size of an MBR disk is 2TB

            iRemainingSize = 2 * 1024 * 1024

        End if

        iExtendedRemainingSize = 0



        '

        ' Enumerate through all partition entries

        '

to cap the size that MDT attempts to partition in an MBR disk to 2TB.

I would appreciate guidance, or if appropriate this fix being included in a future version of MDT.

Thank you,

Matt

Hi y'all,

I have had MDT working in my company for the last 6 months with no issue, but today a problem started with it. MDT installs the OS but does not continue installing after it gets to the log on screen. If I restart it, it will auto log in and finish though, which is really weird for me. 

When it gets to the log on screen where it gets stuck, I can log in with any credentials and it will work, and the deployment will continue and finish. But I am trying to avoid that so it does it automatically without me having to log in o restart the computer. I have not made any changes to it, I was the one who created it and I am the one in charge of maintaining it.

Any help about it would be really appreciated. Thanks in advance. 

Hello,

I am working on upgrading existing windows 7 clients to Windows 10 (1511) using the MDT upgrade sequence.

My goal is to migrate the default browser choice from windows 7 to 10 in each individual upgrade.

Most of the user configuration is retained after the upgrade, but the default browser reverts back to edge.

1.       Is this a known issue / default behavior?
2.       If this is the default, what is the easiest way to migrate the user's default browser choice?

I understand that it is possible to script a check for default browse as part of the upgrade prep, and then import default app settings (using dism.exe) according to that choice in the post-install stage, but I feel there must be a simpler way that I am missing.

Thanks,

S.

Hi folks,

Do we've any example/samples that can illustrate how to use a custom SQL query against MDT database via CustomSettings.ini priority sections i.e LSettings, Locations etc.

I'd want to call out certain values using MDT database table joins.

thanks..