So I'm using the following in my CustomSettings.ini to specify where SMT.MIG files are transferred during deployments:

It works great; with one caveat. The path specified in CS.ini does not show up in the "Location" section of the Wizard when my Helpdesk team reaches that step. Is there any way to populate that "Location" field (maybe with another CS.ini variable) so they can actually *see* the path where the USMT files will go during a deployment? The field is question is circled in red in the screenshot below:

Any help/advice would be appreciated, thanks!

Hello,

Hoping for some assistance as i cannot seem to figure this out. I've inherited and MDT environment (i normally just use sccm). 

To make a long story short:

When i burn my ISO created from MDT, the DEPLOY folder within contains some customization's in a custom folder. I've been having to copy over an additional folder manually into this deploy folder because i dont know how to automate this.

How does one automatically as part of the process get a folder in the DEPLOY folder within the burned the ISO?

Thanks in advance!

Sean

I have been having an issue with MDT deploying drivers to the Dell Latitude E5450.  I have all of the most recent cab files loaded with the total control method.  It seems as if it does the "Set DriverGroup001" task and does nothing, it also jumps over the "Injecting Drivers" phase.  I have been plugging away at this over and over but it just fails to install all of the drivers.  

Jason Santoro A+ Network+

Not very often but once in a while MDT ends with 6743 error, TPM password missing.

At the desktop, I simply need to click activate Bitlocker and then a key is produced in our AD.

The BIOS is set up the same every time, only this issue is a random thing. It does have the supervisor password
set in the BIOS and we don't even touch anything in TPM in the BIOS.

Just wondering what this is about. I see someone added

TpmOwnerPassword=Pa55w0rd

in their CS.INI but I'd just rather not.

Any ideas would be helpful.

I have one MDT server when i try to install windows 10 through Boot so not appear Task sequence ,But I try to install inside the computer so can install easily and show Task sequence also, media is fine . what can i do to show Task sequence

Why does multicast suck in MDT?  Doesn't anybody use it?

Hi,

I get the following error when deploying windows 7 image to HP z420 workstation:

Failure 5456: Unable to determine destination disk, partition, and/or drive. See BDD.LOG

LiteTouch deployment failed, return code = -2147467259 0x80004005

Failed to run the action: inject drivers

.......

When I deploy this same image with exact same settings to virtual machine or HP Elitebook laptop everything works fine. I have imported all z420 drivers to MDT too.

Any ideas?

Why does multicast suck in MDT/WDS?  Doesn't anybody use it?  It's been unusable since winpe 1607.  Does nobody else have this experience?

Hi, 

I am currently trying to install Windows 10 via MDT on my Hyper-V Server. Unfortunatly, my installation stops during the " Install Operating System " step. MDT gave me these errors :

Could not mount offline registry

FAILURE ( 5624 ): 1450: Rune DISM: /Apply-Image /ImageFile:"\\Path\to\my\install.wim" /index:1 /ApplyDir:D:

Litetouch deployment failed, Return Code = -2147467259 0x80004005

Failed to save environment to (80070057)

Failed to run the action: Install Operating System.

Unknown error (Error: 000015F8; Source: Unknown)

The execution of the group (install) has failed and the execution has been aborted. An action failed.

Operation aborted (Error: 80004004; source: Windows)

Failed to run the last action: Install Operating system. Execution of task sequence failed.

Unknown error (Error: 000015F8; Source: Unknown)

Task Sequence ENgine Failed! Code: enExecutionFail

Task Sequence execution failed with error code 80004005

RegQueryValuExW is unsuccessful for software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTsRegValue() is unsuccessful. 0x80070002

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

I have reseach this, but have found no solution. I hope you can help me

Thanks

Laflèche Chevrette

With or without using MDT to encrypt my basic OS image, I get ADDS schema is not configured to run Bitlocker Drive Encryption.

All of my other images will encrypt during deployment through MDT or manually afterwards. My stand-alone OS image will not encrypt either through MDT or manually. The image is basically an OS with Chrome installing during deployment.

The TS's are set up all the same. I had SkipBitlocker set to NO and have a Wizard screen for encryption. It works for every image but the OS.

Any ideas?

Hi,

I have created a TS that installs Windows 10 Pro (1909), a few apps and enables BitLocker; however, the BitLocker step fails. The drive shows up as encrypted, but with an exclamation triangle. The BitLocker Control Panel applet states "Bitlocker waiting for activation". manage-bde -status shows the drive as encrypted:

The TS step is the default "Enable Bitlocker" one as follows:

And my customsettings.ini contains the following BitLocker related parameters:

SkipBitLocker=NO
SkipSummary=YES
SkipFinalSummary=NO

' Bitlocker Configuration
BDEInstallSuppress=NO
BDEWaitForEncryption=False
BDEDriveLetter=S:
BDEDriveSize=3000
BDEInstall=TPM
BDERecoveryKey=AD
OSDBitLockerWaitForEncryption=TRUE

AD has been configured to store BitLocker recovery keys (not tested as deployment wit BitLocker won't work!!)

Deployment shows an error in the final step stating "verify %OSSKU% is defined.", but I don't think this is related to BitLocker (not sure what this is about as no logs, but happy to ignore as it's not causing any issues)

A GPO has been configured with the following settings:

• Choose how Bitlocker- protected operating system drives can be recovered:
• Allow data recovery agent
• Do not enable Bitlocker until recovery information is stored in AD DS for OS drives
• Configure TPM platform validation profile for BIOS-Based firmware configuration
• Configure TPM platform validation profile for (Windows Vista, Windows Server 2008, Windows 7 Windows Server 2008 R2)
• Configure TPM platform validation profile for native UEFI Firmware configurations
  

I also ran the Add-TPMSelfWriteACE.vbs script located at: http://go.microsoft.com/fwlink/?LinkId=167133

I added a Command Line with the following "powershell.exe -command "& {(Get-WMIObject -Namespace root/cimv2/Security/MicrosoftTPM -class Win32_TPM).SetPhysicalPresenceRequest(10)}" after reading https://social.technet.microsoft.com/Forums/azure/en-US/af57538f-a0b9-4418-a626-be29af0991b3/bitlocker-not-activating-when-imaging-with-mdt?forum=mdt, but this does not work.

Now I'm completely stuck!

Has anyone ever added a device to an SCCM collection from an MDT OSD task sequence? When I try to do so the step fails with:

"Import-Module : Could not load file or assembly 'file://\\<SITE SERVER>\d$\Program Files\Microsoft Configuration Manager\AdminConsole\bin\AdminUI.PS.TypeAdapter.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)"

This same Powershell script works fine in an SCCM task sequence. (Our MDT is wholly separate from SCCM.) The destination is reachable from the computer (i.e. - I can browse that folder in File Explorer); the account used to execute the step has the requisite rights on the SCCM server. It's Win10 1803. Being MDT, the step runs with the local administrator logged on but the step itself is run as a domain account that has permission to manipulate SCCM collections.

One difference between the 2 scenarios is that MDT OSD devices are on a different network than devices running this script via an SCCM task sequence. Could it be that a port is being blocked? What port is being used when Powershell tries to import that module?

The script:

Skip

Hi,

I am currently trying to install Microsoft .Net Framework 4.8 with my MDT serveur on a Windows 10 image. Unfortuntly, it does not work. I ran the file on my machine. The installation wizard ended with the error : ".NET Framework 4.8 or later is already installed on this computer". I found that Microsoft .NET Framework 4.5 is installed by default, but is not activated. Do you know if there is a way to install it? Should I write a script that uninstall the Framework installed on the computer and then install the correct Framework? 

I use the command "ndp48-x86-x64-allos-enu.exe /q /norestart" to silently install the Framework

I install Windows 10 Education version 10.0.18363. I don't update the machine in my task sequence (It's a lab enviroment).

Thank's

Laflèche Chevrette

I am upgrading customsettings.ini and try to deploy the OS based on the hardware model, but it seems that the script can't read the TS ID. I also read the log and don't know where is the root of issue.

CustomSetting.ini

[Settings]

Priority=Models,Default,

Properties=ShortModel,MyCustomProperty

[Models]

ShortModel=#Right(Replace(Replace(oEnvironment.Item("Model")," ",""),"-",""),5)#
Subsection=PPT-%ShortModel%


[PPT-E5270]

TaskSequenceID=013

OSDComputername=1-L-%SerialNumber%
MachineObjectOU=OU=Laptop,OU=1_Computer,OU=Computer,DC=Word-CN,DC=Local
WSUSServer=http://10.219.40.88:8530
SLShare=\\10.219.40.88\MDTLogs
SLShareDynamicLogging=\\10.219.40.88\MDTLogs\%ComputerName%

[666-E7250]

TaskSequenceID=013


[Default]
; Adjust default monitor resolution automatically
BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1

OSInstall=YES
SkipBDDWelcome=YES
SkipCapture=NO
SkipTaskSequence=YES
;TaskSequenceID=012
SkipDeploymentType=YES
DeploymentType=NEWCOMPUTER
SkipAdminPassword=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
;SkipComputerName=YES

SkipComputerName=NO
;OSDComputerName=666-1-

SkipPackageDisplay=YES
SkipProductKey=YES
SkipDomainMembership=YES
JoinDomain=Word-CN.Local
DomainAdmin=1user01
DomainAdminDomain=Word-CN.Local
DomainAdminPassword=%%%%%%%%%%%%%

SkipComputerBackup=YES
SkipBitLocker=YES
SkipFinalSummary=YES
SkipTimeZone=YES

TimeZoneName=China Standard Time
SkipLocaleSelection=YES

InputLocale=zh-CN
SystemLocale=zh-CN
UserLocale=zh-CN
KeyboardLocale=zh-CN
PrepareWinRE = YES
SkipUserData=YES
UserDataLocation=NONE
SkipSummary=NO
FinishAction=REBOOT
EventService=http://666-1-MDT1:9800

BDD.log, at the bottom of BDD.log, I found the TS.ini path is incorrect, but I don't know how to correct my customsetting.ini

[Reading \\10.219.40.88\MDTShare$\Control\\TS.XML]LOG]

It SHOULD BE 

Reading \\10.219.40.88\MDTShare$\Control\012\TS.XML]LOG]

Link to review BDD Log

We are receiving the errors below when running a task sequence to upgrade Windows 7 to Windows 10 1909. These inf files under c:\windows\inf are pointing to graphic drivers. I've updated to the latest drivers on the test workstation but still failing. Any thoughts on how to get around this issue?

Hello. My environment is SCCM 2012 SP1 with MDT 2012 Update 1 integrated. We will be moving to R2 and MDT 2013 in the near future. I have a question about the summary page. I have built several custom pages for my deployments. I have noticed that one of the pages display it's selected value on the summary screen but the other two do not. For example, I have a custom page that asked the builder to pick an application suite. When the builder gets to the summary page, the friendly display name for the application suite and their selected value is present. I have another page that asks for the location of the machine. When the builder gets to the summary pages, neither the friendly display name or selected value are present. Both custom pages, use combo boxes with friendly display names configured in the settings of each page.

Everything else works well otherwise but I would like for the builders to see the values they picked on the summary page. Is there something I am missing on my custom pages that is preventing it from appearing in the summary page?

Thank you for the assistance.

We are finding that the USMT does not migrate the default setting for printers when the profile is taken from a Windows 7 (64-bit) machine and restored on Windows 10 1803 & 1909 (64-bit). These are network printers and the printers migrate but the default setting does not.

The default setting migrates fine from Windows 7 to Windows 7. I have used USMT 10.0.14393.0 and 10.0.18362.1.

Is this a known issue/just the way it works going from Win7 to Win10?

Skip

Hello

I need your help

I've been trying to do some scripting that can automate computer naming during MDT deployment process. the structure of our computer name include many factors so i have to do so. the scripts checks the AD if the name already exists or not before giving the next available and incremented name (0100, 0102, 0103). After that i'm using 2 text files to write the last increment  which is going to be a starting point. I am able to do the script and i included the functions within the script DEPLOYWIZ_COMPUTERNAME. i then call the function that generate name within the initializecomputername function. It work great when i am on the server hosting MDT DS but when i try it on other hosts, it gives the error i mentioned in the title. I suspect this is due to some kind of permission since the 2 files to be written are accessed over the network but i need your help to clarify the issue.

I'am giving below a glimpse of the code

Dim counter
         
    Function FileToOpen()
        Dim file
        Dim tp
        tp = oUtility.ComputerName

        If tp =  "BD0BKLPS" then
        file = "laptop.txt"
        Else
            file = "desktop.txt"
        End If
        
        FileToOpen = file
    End Function
        

        Function TestComputerName(str)
        Dim strComputer
        Dim strDomain
            strComputer = str
            strDomain = "TDO"

            'Constants for the NameTranslate object.

            Const ADS_NAME_INITTYPE_GC = 3
            Const ADS_NAME_TYPE_NT4 = 3
            Const ADS_NAME_TYPE_1779 = 1

            ' Use the NameTranslate object to convert the NetBIOS name to the
            ' Distinguished Name.
            Set objTrans = CreateObject("NameTranslate")

            ' Initialize NameTranslate by locating the Global Catalog.
            objTrans.Init ADS_NAME_INITTYPE_GC, ""
            ' Use the Set method to specify the NT format of the object name.

            ' Append "$" to the end of the NetBIOS name of the computer.

            ' Trap error if computer object does not exist.

            On Error Resume Next
            objTrans.Set ADS_NAME_TYPE_NT4, strDomain & "\" & strComputer & "$"

            If (Err.Number = 0) Then
            On Error GoTo 0
            'Msgbox "Computer object exists in AD."
            TestComputerName = 0

            Else
            On Error GoTo 0
            'Msgbox "Computer object does not exist in AD."
            TestComputerName = 1
            End If
            ' Use the Get method to retrieve the RPC 1779 Distinguished Name.
            'strUserDN = objTrans.Get(ADS_NAME_TYPE_1779)
            'Msgbox strUserDN
            ' With this you can bind with the LDAP provider, if desired.
            'strUserDN = objTrans.Get(ADS_NAME_TYPE_1779)

            ' More on this with the below link
            'https://www.rlmueller.net/NameTranslateFAQ.htm
        
        End Function




        Function GenPCName(ct)
            pctype = oUtility.ComputerName
            dim rst
            rst = 0
           
            counter = ct

            Rem while loops as long a free name is not found
            Do Until (rst = 1)
                counter = counter + 1
                if len(counter) <=3 then
                    counter = "0"&counter
                End if

                dim tempName
                tempName = pctype&counter
                Rem Msgbox tempName

                rst = TestComputerName(tempName)
                
                'Msgbox tempName
                
            Loop

            GenPCName = tempName
           

        End Function


rem the below code is used inside the initializecomputername function       

       Set obj = CreateObject("Scripting.FileSystemObject")
        Const rd = 1
        Dim fileName
        fileName=FileToOpen()
        Set obj1 = obj.OpenTextFile("\\SERVER_NAME\PCNAMING\"+fileName,rd)
        Dim cnt
        cnt = obj1.ReadAll
        obj1.close
        

        Dim pcName 
        pcName = GenPCName(cnt)
     
        

        Set obj = CreateObject("Scripting.FileSystemObject")
        Const wr = 2
        
        Set obj2 = obj.OpenTextFile("\\SERVER_NAME\PCNAMING"+fileName,wr)
        obj2.WriteLine(counter)
        obj2.close
       
        
        OSDComputerName.Value = pcName

Hi,

We have a weird issue where some specific HP models , specifically the G1 and G2's are deleting the contents of the Boot partition on our external build drives.

We have created a script that creates two partitions (D: / E:) on an external SSD drive, The D: contains the Boot folders etc and E: contains the contents of the Deploy folder (basically the MDT share).

This has been working well for all of our machines generally, but these older HP machines for whatever reason seem to strip the SSD of the Boot folder entirely. This is despite the partition being set to Read-Only and the HP models above the only models that this behavior seems to occur on.

Has anyone come across this before?

Has anyone had success installing McAfee Endpoint Security Platform with MDT? I keep getting a failure with a return code of 16030. This is a code being returned by McAfee itself. The McAfee site is not helpful it only states "The installation wizard was interrupted before Endpoint Security was installed. Your previous software was uninstalled, but no other changes were made to your system." For that code. BDD.log only states McAfee returned an unexpected return code: 16030.