I have an MDT 8450 deployment share synced to another site with DFS-R using these settings https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/build-a-distributed-environment-for-windows-10-deployment

Everything seems to work on both sites except, when the deployment is run from the remote site, the same task sequence stops at the login screen and requires manual password entry.

What settings would I need to configure to make to enable autologon at the new site?

I remember something about autounattend.xml needing to be edited, but I don't remember the details or how that would work when the deployment share is being synced over dfsr.

Hi all,

i have issues with the post application windows update task sequence.

While os deployment instantly after searching for updates the deployment failed.

I created a new custom task sequence for testing and copied the post application windows updates in there.

I´m using a shared wsus, with https and target groups

I remember in my old company where i worked, i set up mdt with wsus and there it worked just fine. Wsus was there http not https don’t know if that might be the problem.

I followed this:

https://www.peppercrew.nl/index.php/2015/10/add-wsus-target-group-option-to-mdt-deployments-2/ 

used Method 2

When i look in regedit HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate wsus and the right target group are in there, still the task sequence didnt work.

When i do the windows updates normal over settings everything is working.

Does someone had experienced same issues or does anybody have a tip for me?

Any help much appreciated.

I uploaded the logs 

https://uploadfiles.io/oi7hv 

Recently I set up the database for MDT on a separate (existing) MS SQL server that I manage.  The data upload was fine, but I am getting two problems since getting the server attached: 1) When deploying, the computers aren't being named from the database; and 2) the scripts that occur between authentication and the menu takes 20ish minutes!  I'm not totally sure where to start troubleshooting the second problem, but I think the first has to do with how the CS.ini file is setup to handle the naming of the computers.

Of course, I could be totally wrong (probably), and it could be the unattend.xml file that needs work.  Either way, any help in resolving these problems would be greatly appreciated.

Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi There,

My Environment - MDT 8450  - Server 2008R2 - PXE boot using WDS -  Deploying Windows 10 1809 ent.

Its been a long time since I worked on Deployments. Could someone please help me with a bit of clarity.

I am trying to customise the start menu, and research provides many, many different ways of doing it, most them are patch jobs and not acceptable to me. I would very much prefer to make the changes to my base image (source image). And use the unattend file.

So I am reading through this document https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/jj134269(v=win.10)

The problem is that it doesn't stipulate where this xml file should be saved, it is unclear if it should be part of the MDT unattend file or some other separate unattend file in the panther folder. do I just put an unattend file in the root of c:

Then I have one more question which research isn't turning up much useful data on.

In the SIM manager I have the main Task sequence unattend file open.

What replaces OOBE/NetworkLocation?
How do I make sure that Cortana screen doesn't appear at all?

Chad the Dad

Hi,

I have this MDT task sequence for setting up SCCM 2012 (I modified hydration kit for that: http://www.deploymentresearch.com/Research/tabid/62/EntryId/149/The-Hydration-Kit-for-System-Center-2012-R2-is-available-for-download.aspx)

Everything works/worked fine but now it doesn't want to allow the autologon, it says "Username or password incorrect".
Where is this autologon password stored? Note: I commented out the autologon in unattend.xml, have set the customsettings.ini, the customsettings.ini for specific server to correct logon info. Changed also the bootstrap.ini

DomainAdmin=Administrator    
DomainAdminDomain=ourdomain
DomainAdminPassword=ourdomainpassword

Please advise,
J.

Jan Hoedt

Hi all.

I have updated my ADK on my MDT to 1809 (along with the new Windows PE Addon).  When I go to update my deployment share, I receive an error that access to the path is denied.  I have verified the permissions to the path and I can access it.  I also tried opening Deployment Workbench as administrator but I get the same error.  This should be a simple fix... Any ideas?  Here is the log:

=== Making sure the deployment share has the latest x86 tools ===

=== Processing LiteTouchPE (x86) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
WIM file mounted.
Set Windows PE system root.
Set Windows PE scratch space.
Added component winpe-hta
Added component winpe-scripting
Added component winpe-wmi
Added component winpe-securestartup
Added component winpe-fmapi
Added component winpe-dismcmdlets
Added component winpe-mdac
Added component winpe-netfx
Added component winpe-powershell
Added component dart8
Injected driver Microsoft Corporation System wstorflt.inf 6.1.7601.17514 (1)
Injected driver Microsoft Display wvmbusvideo.inf 6.1.7601.17514 (1)
Injected driver Microsoft HIDClass wvmbushid.inf 6.1.7601.17514 (1)
Injected driver Microsoft Net wnetvsc.inf 6.1.7601.17514 (1)
Injected driver Microsoft System wdmvsc.inf 6.1.7601.17514 (1)
Injected driver Microsoft System ws3cap.inf 6.1.7601.17514 (1)
Injected driver Microsoft System wvmbus.inf 6.1.7601.17514 (1)
Injected driver Microsoft System wvmic.inf 6.1.7601.17514 (1)
Injected driver Microsoft. SCSIAdapter wstorvsc.inf 6.1.7601.17514 (1)
Injected driver VMware, Inc. Display vm3d.inf 8.15.01.0033
Injected driver VMware, Inc. Display vmx_svga.inf 12.01.08.0000
Injected driver VMware, Inc. Net vmxnet3ndis5.inf 1.5.2.0
Injected driver VMware, Inc. Net vmxnet3ndis6.inf 1.6.7.0
Copy: \\SRV-DTMG-01\mdtbuild$\Control\Bootstrap.ini to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Bootstrap.ini
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x86.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Unattend.xml
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\winpeshl.ini to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Windows\system32\winpeshl.ini
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\LiteTouch.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\LiteTouch.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIBCDUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIBCDUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIDiskUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIDiskUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIDataAccess.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIDataAccess.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIConfigFile.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIConfigFile.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIGather.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIGather.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTIGather.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTIGather.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Wizard.hta to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Wizard.hta
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Credentials_ENU.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Credentials_ENU.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Credentials_scripts.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Credentials_scripts.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WizUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WizUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Wizard.css to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Wizard.css
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Wizard.ico to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Wizard.ico
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\BackButton.jpg to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\BackButton.jpg
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\plusicon.gif to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\plusicon.gif
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\minusico.gif to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\minusico.gif
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Summary_Definition_ENU.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Summary_Definition_ENU.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Summary_scripts.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Summary_scripts.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\LTICleanup.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\LTICleanup.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\BDD_Welcome_ENU.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\BDD_Welcome_ENU.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Choice.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Choice.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Choice.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Choice.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_DeployRoot.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_DeployRoot.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Initialize.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Initialize.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Initialize.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Initialize.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\SelectItem.jpg to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\SelectItem.jpg
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeBanner.jpg to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeBanner.jpg
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\btnout.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\btnout.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\btnover.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\btnover.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\btnsel.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\btnsel.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\LTIGetFolder.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\LTIGetFolder.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\NICSettings_Definition_ENU.xml to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\NICSettings_Definition_ENU.xml
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTINicUtility.vbs to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTINicUtility.vbs
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ZTINicConfig.wsf to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ZTINicConfig.wsf
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\BackButton.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\BackButton.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\FolderIcon.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\FolderIcon.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\ItemIcon1.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\ItemIcon1.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\MinusIcon1.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\MinusIcon1.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\PlusIcon1.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\PlusIcon1.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\SelectItem.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\SelectItem.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\header-image.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\header-image.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\NavBar.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\NavBar.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\Computer.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\Computer.png
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\WelcomeWiz_Background.jpg to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\WelcomeWiz_Background.jpg
Copy: \\SRV-DTMG-01\mdtbuild$\Scripts\DeployWiz_Administrator.png to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Scripts\DeployWiz_Administrator.png
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\BDDRUN.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Windows\system32\BDDRUN.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\WinRERUN.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\WinRERUN.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\CcmCore.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\CcmCore.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\CcmUtilLib.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\CcmUtilLib.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\Smsboot.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\Smsboot.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\SmsCore.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\SmsCore.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsCore.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsCore.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TSEnv.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TSEnv.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsManager.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsManager.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsmBootstrap.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsmBootstrap.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsMessaging.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsMessaging.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsmBootstrap.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsmBootstrap.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TsProgressUI.exe to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TsProgressUI.exe
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\TSResNlc.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\TSResNlc.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\CommonUtils.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\CommonUtils.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\ccmgencert.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\ccmgencert.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\msvcp120.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\msvcp120.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\msvcr120.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\msvcr120.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\00000409\tsres.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\00000409\tsres.dll
Copy: \\SRV-DTMG-01\mdtbuild$\Tools\x86\Microsoft.BDD.Utility.dll to C:\Users\jsmith\AppData\Local\Temp\MDTUpdate.4476\Mount\Deploy\Tools\x86\Microsoft.BDD.Utility.dll
Copying WIM to the deployment share.
Creating an ISO.
Copying ISO to the deployment share.

System.Management.Automation.CmdletInvocationException: Access to the path '\\SRV-DTMG-01\mdtbuild$\Boot\ImageBuildLiteTouchPE_x86.iso' is denied. ---> System.UnauthorizedAccessException: Access to the path '\\SRV-DTMG-01\mdtbuild$\Boot\ImageBuildLiteTouchPE_x86.iso' is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.Delete(String path)
   at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)
   at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

When trying to create a Task Sequence in MDT to Install a Windows 2019 feature, Windows 2019 server is not listed in drop down menu.  Has anyone encountered this problem?

I have installed the latest ADK v10.1.17763.1

Does MDT 6.3.8450.1000 support Windows 2019 roles and features deployments?

Thanks

Hi,

I use MDT 6.3.8450.1000 the latest version I can find. Just for testing I added Server 2019 1809. I was testing to capture a image. I kicked of an TS after boot, and the OS was installed, but I was end up with the MDT "Task Sequence" again inside the deployed Server 2019.

So I have not find anything about a new MDT for Server 2019 1809 support? 

/SaiTech

Hi - I'm wondering if anyone else has seen this behaviour and, if so, how they've gotten around it.

I have Deployment Workbench organised into folders representing different releases of our image - our current image is based on 1709 and I'm starting work on a new image based on 1809, so I now have 2 sets of folders within each category - one for the 1709 image and one for the 1809 image.

I've successfully imported the Jan '19 security package for Win10 1809, but when I try and import the Jan '19 Flashsecurity package for Win10 1809 the import wizard gives me the following:

Not copying existing package C:\Users\nt084\AppData\Local\Temp\MSUexpand\Windows10.0-KB4480979-x64.cab

Copying existing item Package_for_KB4480979 neutral amd64 10.0.1.0 from DS006:\Packages\1709 to DS006:\Packages\1809.

This is, I assume, because I've previously imported the 1709 specific Jan '19 Flash package.

If I try and build my 1809 image with the 1709 Flash package, the build understandably fails with a DISM error.

So my question is this - how do I import and manage the monthly Flash packages for both my current build and new build within the same Deployment Share? Looking forward to hearing from you - and if I need to provide more detail just let me know!

So we're switch from KACE to MDT and I am now modifying ourenvironment to run WDS/MDT (this will be important later

I would like to see if someone can review my work (based off of Johan's "Deployment Fudamentals - Vol 6" book. I have followed his instructions (and listed below) but I cannot seem to get the device to send the Bitlocker TPM recover key to AD.

DC Settings:

Features added:

1. Bitlocker Drive Encryption Administration Utility
2. Bitlocker Drive Encryption Tools
3. Bitlocker Recovery Password Viewer
4. Create a GPO with the following settings:
5. Choose how Bitlocker- protected operating system drives can be recovered:
   1. a) Allow data recovery agent
   2. Do not enable Bitlocker until recovery information is stored in AD DS for OS drives
6. Configure TPM platform validation profile for BIOS-Based firmware configuration
7. Configure TPM platform validation profile for (Windows Vista, Windows Server 2008, Windows 7 Windows Server 2008 R2)
8. Configure TPM platform validation profile for native UEFI Firmware configurations
   1. Enabled Turn on TPM Backup to AD DS
   2. Ran the Add-TPMSelfWriteACE.vbs script located at:http://go.microsoft.com/fwlink/?LinkId=167133

MDT Settings:

1. Added rules to the customsetting.ini under default:
   1. BDEInstall=TPM
   2. BDERecoveryKey=AD
   3. In the TS I want trun, I added the following TS
   4. In state Restore group, before Enable Bitlocker action add a new group with the following settings:
      1. Name: Bitlocker
      2. Option: Add a TS condition with the following settings:

(1) Variable: BDEInstallSuppress

(2) Condition: not equals

(3) Value: YES

1. In the Bitlocker group, add a Run Command Line action with the following settings:
   1. Name Check TPM Status
   2. Command line: cscript.exe “%ScriptRoot%ZTICheckforTPM_v2.wsf” ßThat script does not exist in the location it’s asking for. Could be a problems?
   3. In the State Restore group, select the Enable BitLocker action and move it after the Check TPM Status action. Then configure the options for the Enable BitLocker action with the following settings:
   4. Add an if statement set to All Conditions
   5. Selectif all condition are true, add a Task Sequence Variable condition with the following settings:

(1) Variable: TPMReady

(2) Condition: equals

(3) Value: TRUE

1. Select Task sequence variableTMPReady equals TRUE and add a Task Sequence Variable condition with the following settings:

(1) Variable: TPMActivated

(2) Condition: equals

(3) Value: TRUE

1. In the State Restore group, after the Apply Local GPO Package action, add a Run Command Line action with the following settings:
   1. Name: Remove BDE Recovery File
   2. Command line: PowerShell.exe –executionPolicy Bypass –File “%SCRIPTROOT%\Remove-BDERecoveryFile.ps1”

(1) Options / Continue on error: Selected

There are not errors reported when the image finished. The device does join to the domain and goes to the correct testing OU I have created. 

Currently with KACE, I run this powershell script as a Post-Installation task (equivalent what a TS is for running an installation or command-line in MDT) with the following code:

Initialize-Tpm
BdeHdCfg.exe -target %SystemDrive% shrink -quiet –restart
manage-bde.exe -protectors -add c: -recoverypassword=AD
manage-bde -on C: -rp -used 

to kick off the bitlocker encryption. It will add the Recovery key to AD then asks the for the device to reboot to start the encryption (which I run another Post-Installation task to reboot) and works fine. However, if I run this powershell script in MDT, it adds the key to AD but when the device reboots, it requires me to enter the recovery key. The key that was provided to AD does not work.

I'm stuck and at a loss.

Specs: DC = Server 2012r2

MDT/WDS Server 2016 with: MDT 2013u2 build: 8450

OS: Win 10 Pro x64 1703

"Start BitLocker" was the PS file I was running as a test but is currently disabled along with pausing the encryption TS.

Please note in the rules, I have tried with the JUST the highlighted and also with the extra rules.

End Result.

     Need some assistance from all the MDT gurus out there. I am trying to Image a Dell Latitude 5580 and a 7480 with MDT 2013 (v6.3.8450.1000) and ADK (v10.1.16299.15) but after it gets to the STATERESTORE phase it just stops at a CMD prompt. If I restart the laptop the TS continues and completes without any errors. I've tried to recreate the TS and used the Windows 10 RTM instead of our customized .wim but with the same results. I've tried the TS with an older computer (Latitude E6440) and also on a Hyper-V VM and the TS works just fine with them. Also, I have tried to update the BIOS but that did not stop the TS stall at the CMD prompt. Also when at the CMD prompt I can still ping the MDT deployment share. Any advice would be greatly appreciated!

BDD.log on Google Drive

Hello,

(i'm not native english speaker)

I have a "stupid" question about drivers.

I'm deploying MDT in my enterprise and we have this situation about drivers :

- We have laptops and desktop computers

- several marks and several models

I managed to add in my MDT deployment share all the drivers i need for each model of computer in our environment.

After some researches i saw that, in my O.S deployment task sequence, i could use some kind of WMI request to check the mark/model of the deploying computer. And depending of the wmi result, i could inject the correct driver group.

(for example, if i deploy a toshiba tecra, the task sequence does the wmi request, sees that the computer is a toshiba tecra and so, injects the correct driver group containing toshiba tecra A50 drivers)

But, after some work, i saw that, in the task sequence, i can choose the Driver selection profile.

By default it is set to "All Drivers" and you have 2 buttons "Install only matching drivers from the selection profile" and "Install all drivers from the selection profile"

So i have the following question :

Don't you think it is much easier to do the following :

- Instead of using wmi request etc... and assuming the fact that i injected all drivers i need for all my different computers

- I keep this option by default, so i keep using the "All drivers" selection profile and the option "Install only matching drivers from the selection profile"

- That should mean that, whatever computer I deploy, mdt should be able to "install only matching drivers from the selection profile" so i don't have to worry anymore about drivers with complicated driver rules etc... => mdt will automatically install needed drivers

What do you think about that ?

Sorry if i am not clear english is not my mother tongue.

thanks.

regards.

Benjamin.

I am trying to push HP SSM via deployment workbench and I keep getting the following error:

Application HP System Software Manager returned an unexpected return code: 1

I have tried everything in the book but keep getting the same error above. 

I have a batch file which is called in the quiet install command named SSMsetup.cmd and within that batch file i have the following:

SSM.exe %~dp0 /accept /noreboot

Can anyone shed any light on this and point me in the right direction 

planning W10 deployment...

I would like to know if there is an article/blog with a list of suggestions about making W10 in production really "athletic", instead of leaving it "fat" and heavy as it comes out of box.

I guess it should be a list of GPOs, like disable OneDrive, Tiles, Cortana all the "mining" settings for user interactions and experience and etc...

How you tweak W10 deployment? May be some script during deployment that makes W10 as neat as possible.

Thx.

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Suddenly when i have deployed a image to a client with mdt2013 after several restarts windows logs in automatically with administrator user and comes with the task sequence window again. I can shut it off cource but where is that defined that this screen appears again?

Normally after deployment and restarts off the client a script runs that runs a batch file and cleans the leftovers from MDT on the client, then a screen appears: finished successfully but that is now gone…

freddie

Hi all, here is my situation. I am working on an offline media for our Win10 deployment. Everything is working great, but our security team has put a road block on the process. They do not like the password in the customsettings.ini file which I can respect since it is in clear text. Yes I know about the wizard that will prompt for that if not configured in the INI file. The thing is, these devices would not be able to join the domain at the early point of the process, so I already moved it to later in the process by removing the domain join option from the unattend.xml file, disabling the recover step from the TS, and then using a script to join the domain. All this works fine, except for the password in the script. There is also a step that displays a message box so it causes the process to pause so that the users can configure the vpn client, that way during the domain join step, the device can reach the network for authentication. Once they complete the vpn connection, and click OK on the message box, the process continues. Again, as is, all this works great, just have to get past the password issue. I would love to either:

1. move the popup wizard that prompts for the domain credentials to further down
2. create a way for a popup to happen maybe from a script, that will allow the users to enter credentials so I won't have to put it in the script. 

I figure some kind of input box that would mask the entry, then once they click OK to confirm, the password from the input field would pass thru and allow the machine to authenticate. I hope I was able to clearly explain what I am trying to achieve and need help with

We sacrificed so you can enjoy a good night's sleep. Airborne Ranger all the way!!!

All of my applications are missing? 

I checked and the applications.xml file is in the Control folder and looks correct and is still populated with all my applications.

I Updated the Deployment Share but all my applications missing from Applications folder

So I created a new application and it is displayed in the Applications folder and I see an entry for it at the end of my applications.xml file so it is reading the file.

But why aren't my other applications being displayed and how do I get them back?

Today MDT team of Microsoft gave news about this new version of MDT all information in this link https://docs.microsoft.com/en-us/sccm/mdt/release-notes

Download in this link https://www.microsoft.com/en-us/download/details.aspx?id=54259

Hi there,

I have problems with automatic domain join using the Windows Deployment Toolkit. Everytime I configure anything it won't work. The NetSetup.txt* put out errors like these:

*["C:\Windows\debug\NetSetup.LOG"]

01/26/2019 17:34:22:651 NetpGetComputerObjectDn: Cracking DNS domain name contoso.corp/ into Netbios on \\WDT-W16SRV1.contoso.corp
01/26/2019 17:34:22:651 NetpGetComputerObjectDn: Crack results:     name = CONTOSO\
01/26/2019 17:34:22:651 NetpGetComputerObjectDn: Cracking account name CONTOSO\WDT-WZ3$ on \\WDT-W16SRV1.contoso.corp
01/26/2019 17:34:22:651 NetpGetComputerObjectDn: Crack results:     Account does not exist
01/26/2019 17:34:22:651 NetpGetComputerObjectDn: ldap_compare_s failed: 0x1 0x6e
01/26/2019 17:34:22:651 NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x6e
01/26/2019 17:34:22:651 NetpProvisionComputerAccount: LDAP creation failed: 0x6e
01/26/2019 17:34:22:651 NetpProvisionComputerAccount: Cannot retry downlevel, specifying OU is not supported
01/26/2019 17:34:22:651 ldap_unbind status: 0x0

..

01/26/2019 17:34:32:682 NetpDisableIDNEncoding: no domain dns available - IDN encoding will NOT be disabled
01/26/2019 17:34:32:682 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0

..

01/26/2019 18:08:41:095 NetpDsGetDcName: trying to find DC in domain 'contoso.corp', flags: 0x40001010

Have anybody any idea? Thanks a lot.

Best regards, crazyyzarc