I currently deploy Windows 7 x64 to a variety of different systems using MDT 2012.  All systems that I have in my inventory use intel processors with the exception of one particular HP Laptop.  On all Intel models, if I do not change the SATA mode from AHCI to compatibility/IDE the MDT imaging process hangs up at "Preparing disk 0 partitions"  I have verified that all required storage drivers are present.  Are there any settings or changes that I can make to get around this issue?  Thanks.

-Joe G

Configuration : 

MDT 2013 Update 1 ( I tried with MDT Update 2, but same result )

Hi everebody,

I have a probleme when I try to deploy Windows 10 with an Upgrade task sequence with MDT.

The upgraded blocked a 100%, and the window of end deployment appear, while the task sequence is not finish ! Like that : 

So, Windows 10 is deploy and activate, but the comportement is not normal ; and all my next steps (install application, remove window.old ...) are not execute.

I don't understand what happening, I need help ;) 

Thanks

I am trying to set a network location for the following:

BDEInstallSuppress=NO
BDEWaitForEncryption=False
BDEDriveLetter=S:
BDEDriveSize=2000
BDEInstall=TPM
BDERecoveryKey=AD
BDEKeyLocation=network share

However, it keeps asking me for credentials to connect.. How can I supply those in my customsettings? I already have the following which joins the computers to AD. Service account...

JoinDomain=****
DomainAdmin=domjoin
DomainAdminDomain=****
DomainAdminPassword=*****

Is it using the same credentials?

I need help to automate this last hurdle.

Working in creating images for multiple customers.
Is it better to use a single deployment share or multiple deployment share?

If using single deployment share, how to create separate CustomSettings.ini for each customer?

Read this article for single deployment share: https://social.technet.microsoft.com/Forums/en-US/bbaad90f-888a-403c-9d45-cf3879df53aa/how-best-to-manage-multiple-customers-using-single-mdt-deployment-share?forum=mdt

Hi all, I Made a working Build and Capture TS. Used the default Windows 7 install.wim everything works fine. The Pre-App Windows Updates search and install starts after 3 times within 5min.
(using the latest WUA Version: 7.6.7601.19161). First 150 updates then anonther 90 updates. Capture is fine and after xx hours i have a complete Win7 capture.

Now the problem:

To save time I offline updated the original install.wim with the required prereq (KB3020369) and added the KB3125574 (Win7 SP1 convenience rollup) to the MDT packages. when I use this offline updated install.wim it takes hours to start the The Pre-App Windows Updates search and begining the install of the rest of the updates.

So with original install.wim starting to update image within 3 tries and 5min.

With updated install.wim starting to update image withing 3 tries and many hours and still 123 updates to go. (including .net)

WUA = Latest version

Does anyone have an idea what causes this problem?

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

Logging from working and original install.wim:

Property SMSTSRetryRequested is now =  ZTIWindowsUpdate 13-5-2016 10:25:29 0 (0x0000)
Configuring client to use WSUS server http://XXXX0004.dev.XXX.nl:8530 ZTIWindowsUpdate 13-5-2016 10:25:29 0 (0x0000)
Configuring Windows Update settings (manual update, use server) ZTIWindowsUpdate 13-5-2016 10:25:29 0 (0x0000)
Windows Update Agent verion 6 found, OK to continue ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7601.19161 ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
Microsoft Update Service:  Enabled = False ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0 and Type = 'Software'] ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
Start Search... ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
INSTALL - 57260dfe-227c-45e3-9ffc-2fc77a67f95a - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2656356) - 4 MB ZTIWindowsUpdate 13-5-2016 10:30:33 0 (0x0000)

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

Logging from updated install.wim:

Begin Windows Update. Reboot=[false]  Retry=[true]  Count = 2 ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Property MSIT_WU_Count is now = 3 ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Property SMSTSRebootRequested is now =  ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Property SMSTSRetryRequested is now =  ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Configuring client to use WSUS server http://XXXX0004.dev.XXX.nl:8530 ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Configuring Windows Update settings (manual update, use server) ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Windows Update Agent verion 6 found, OK to continue ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7601.23435 ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
Microsoft Update Service:  Enabled = False ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0 and Type = 'Software'] ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
Start Search... ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
INSTALL - 57260dfe-227c-45e3-9ffc-2fc77a67f95a - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2656356) - 4 MB ZTIWindowsUpdate 18-5-2016 13:52:57 0 (0x0000)
INSTALL - 6502a461-7262-48fc-b567-f8d3c2f82ae6 - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2604115) - 23 MB ZTIWindowsUpdate 18-5-2016 13:52:57 0 (0x0000)
INSTALL - 78f92451-801a-40f5-9582-cb8d1ca993be - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2729452) - 13 MB ZTIWindowsUpdate 18-5-2016 13:52:57 0 (0x0000)

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

This is what I did to update the install.wim offline:

Used the original install.wim from the Win7 SP1 sources

(expand not required but I did)
Downloaded the KB3020369 (req) and the rollup KB3125574.

expand -F:* F:\Update\AMD64-all-windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu F:\Update

expand -F:* “F:\Update\Windows6.1-KB3020369-x64.msu” F:\Update

dism /mount-wim /wimfile:C:\install.wim /mountdir:C:\Mount /index:1

dism /image:C:\mount /Add-Package /PackagePath:C:\Update\Windows6.1-KB3020369-x64.cab

dism /image:C:\mount /Add-Package /PackagePath:C:\Update\Windows6.1-KB3125574-v4-x64.cab

dism /unmount-wim /mountdir:C:\mount /commit

After that copied the install.wim back to the OS deployment shares directory I used.

Started the Build Ref Win7 Tasksequence on a VM (2cores 10GBmem)

WUA Version: 7.6.7601.23435 (latest)

MDT 2013 Update 2 - Windows 2012 R2 Server

ZTIWindowsUpdate.log - The Good file : https://onedrive.live.com/redir?resid=749BF03D0E7EF0BB%211611

ZTIWindowsUpdate.log - The wrong file: https://onedrive.live.com/redir?resid=749BF03D0E7EF0BB%211612

Hey Guys,

Even though the language and other locale settings are selected during the Deploy wizard, I still get prompt by windows setup (mini setup) to select them. I assume this must have something to do with my unattend.xml file.

I have tried removing the international section but this had no effect.

BTW... this is for W7 Pro image with injected language packs.

Any thoughts?

Thanks

Dave

hi,

I would like to bootstrap a 2012r2 infrastructure using mdt (already have this in production for windows 7 and 2008r2).

Our deployment shares are in netapp filers, and for several reasons enabling signing is not an option (other production services  stop working).

We are aware of https://support.microsoft.com/en-us/kb/2686098 and, indeed, running the commands specified in there in a 2012r2 host allows connecting to our corporate shares.

We now need to have this behaviour for winpe 5 (what got installed when we deployed the mdt 2013 update 1 and the 'windows assessment and deployment toolkit - windows 10'.

I have modified the winpe.wim file and the boot.wim (in the folder sources) to add the parameter

Dism /Mount-Wim /WimFile:"d:\path\to\winpe.wim" /Index:1 /MountDir:"d:\mount"

REG LOAD HKLM\dism "d:\Mount\Windows\System32\Config\System"

REG ADD HKLM\dism\ControlSet001\Services\LanmanWorkstation\Parameters /v RequireSecureNegotiate /t REG_DWORD /d 0 /f

REG UNLOAD HKLM\dism

Dism /Unmount-Wim /MountDir:"d:\Mount" /Commit

After un-mounting the winpe.wim file and remounting it, I see the new parameter in there, so I know it works. To be sure I modified the startnet.cmd and added the same line before the call to wpeinit

Rebuilding the share detects the changes to the winpe.wim and winpe boots properly. Unfortunately it stops after the first messages and only a gray screen remains. If we press f8, then we see that the share is mapped, but een dir z: gives us 'Access denied'.

The modiefied startnet.cmd has the line we added, so that was changed succesfully, but reg query does not show the lanmanworkstation parameter we added.

I really very much would prefer to use the cifs share on the netapp. If I enable signing on it, the process works, but as I said, other critical process would stop working, so that is not an option. Is there something else I can try?

hello

I have been trying to sysprep a surface pro 4 but get a script error. 

we create thick images doe to the nature of the application we user. 

I am running the litetouch.vbs from the VM which is running windows 10 os

this is the error message I get. 

 

The log file show the following error for the BDD and LiteTouch

windows 2012 server with windows ADK 10

Deployment workbench version is 6.2.5019.0

please help if you can

Hi,

I'm in the process of preparing a windows 10 enterprise reference image. During the prep, I'm removing all of the pre-bundled bloat modern ui apps that seems to install itself during oobe (I mean CandyCrush... Really guys!? :\).

We do this using remove-appxpackage cmdlet.

After the image is sysprepped however, all the crap re installs and does so for each new user that logs on. I'm sure I'm not the only one that doesn't want xbox, twitter, candycrush and all this other stuff on my nice shiny enterprise build.

is there a way to permanently remove these apps and prevent re-installation? would appreciate the benefit of others experiences.

Thanks,

Ben

Hello, I've been struggling with this one on and off for about 6 months now.  The message "a connection to the deployment share could not be made" occurs after the user account (that's supplied during the task sequence) gets locked out.  I haven't the slightest idea why this keeps happening, and it seems to happen intermittently and on all hardware types (desktops/laptops).  The user account is a domain admin account and I've granted explicit NTFS/Share permissions to the deployment share. For whatever reason, the account keeps getting locked out during deployment.

Here's a copy of the bdd.log:

https://drive.google.com/file/d/0B5G9Zwc89uMCSDk2OHprcjQ3bm8/view?usp=sharing

I'd really appreciate if someone could offer some insight as to why this happens.  We use a vanilla task sequence and cherry pick applications that reside on a file share.  We've generally had good success using this method as maintaining thick images is too much work/maintenance.

In this case, the target machine is a Dell Latitude E6530 and I am deploying Windows 8.1.  This message seems to always occur after the OS has deployed/windows updates have finished and some other part of the task sequence is trying to take place.

Any help is appreciated.  Thanks!

On my companies deployment server, we sometimes lose connection to the deployment server after a reboot. The drive will be mapped but when you click it it will say "Access is denied". It usually happens after a reboot for updates, and my current reoccuring computer is a physical test computer with an SSD.

I did some research and saw that it tries to map it with the built-in Adminstrator account when this happens. Normally it maps under the username/password that is used to login to the server at winPE. We do not store a username/password in customsettings.ini or bootstrap.ini, but we do pre-fill in the Domain.

The workaround is to disconnect, re-map the drive, and restart the deployment which it skips half of it from already being done, but this is a nuisance and logistical headache when working with many users deploying computers.

I have tried this (https://4sysops.com/archives/resolving-a-connection-to-the-deployment-share-could-not-be-madeerrors-in-mdt/) but it has not made a difference.

Any suggestions on figuring this out? Maybe it is fixed in Update 2?

One log line I notice is: <![LOG[Unable to connect to share: The network path was not found.
( 0x80070035 ) , trying to connect without username. ]LOG]!><time="15:54:56.000+000" date="05-19-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Also our deployment share does not accept anonymous login attempts due to another share on the server specified having it turned on. If you try to connect to share without entering a username/password via map network drive it will not let you in.

Hi,

I have a Windows Server 2008 R2 with MDT 2013U2.

I make an update of my image boot WinPE for Windows 10 and new tasks sequence.

When I want to deploy a workstation in Windows 7 the process failed. I think it's an error because of the UEFI BIOS but I don't understand why it's not working while before all is it ok !!

In my task sequence the disk type is set to GPT.

The smsts.log file :

<![LOG[Failed to run the action: Install Operating System. 
Unknown error (Error: 000015EF; Source: Unknown)]LOG]!><time="03:27:00.479+000" date="05-18-2016" component="TSManager" context="" type="3" thread="1380" file="instruction.cxx:3101">
<![LOG[Sending status message . . .]LOG]!><time="03:27:00.479+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="utility.cxx:292">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="03:27:00.479+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="utility.cxx:302">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=5615]LOG]!><time="03:27:00.479+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="03:27:00.479+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="03:27:00.479+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="executionenv.cxx:807">
<![LOG[Let the parent group (Install) decides whether to continue execution]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="instruction.cxx:3210">
<![LOG[The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="3" thread="1380" file="instruction.cxx:2424">
<![LOG[Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015EF; Source: Unknown)]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="3" thread="1380" file="engine.cxx:214">
<![LOG[Sending status message . . .]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="utility.cxx:292">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="utility.cxx:302">
<![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="tsmanager.cpp:767">
<![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="3" thread="1380" file="tsmanager.cpp:767">
<![LOG[****************************************************************************]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="tsmanager.cpp:789">
<![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="3" thread="1380" file="tsmanager.cpp:790">
<![LOG[Cleaning Up. Removing Authenticator]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="tsmanager.cpp:578">
<![LOG[Cleaning up task sequence folder]LOG]!><time="03:27:00.495+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="utils.cpp:1404">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="03:27:00.636+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="resolvesource.cpp:508">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="03:27:00.636+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="03:27:00.636+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="environmentlib.cpp:869">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="03:27:00.636+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="commandline.cpp:229">
<![LOG[Set command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister]LOG]!><time="03:27:00.636+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister]LOG]!><time="03:27:00.636+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="commandline.cpp:805">
<![LOG[==========[ TsProgressUI started in process 1176 ]==========]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TsProgressUI" context="" type="1" thread="1188" file="winmain.cpp:327">
<![LOG[Command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TsProgressUI" context="" type="0" thread="1188" file="winmain.cpp:330">
<![LOG[Unregistering COM classes]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TsProgressUI" context="" type="1" thread="1188" file="winmain.cpp:202">
<![LOG[Unregistering class objects]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TsProgressUI" context="" type="1" thread="1188" file="winmain.cpp:503">
<![LOG[Shutdown complete.]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TsProgressUI" context="" type="1" thread="1188" file="winmain.cpp:520">
<![LOG[Process completed with exit code 0]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="commandline.cpp:1102">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="utils.cpp:1963">
<![LOG[g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,657)]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="tsmanager.cpp:657">
<![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="3" thread="1380" file="tsmanager.cpp:689">
<![LOG[Sending error status message]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="tsmanager.cpp:690">
<![LOG[In non SMS staqndalone mode.Ignoring SendStatusMessage request]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="tsmanager.cpp:1541">
<![LOG[Finalizing logging from process 1348]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="tslogging.cpp:1578">
<![LOG[Successfully finalized logs to C:\SMSTSLog]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="1" thread="1380" file="tslogging.cpp:1635">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="03:27:00.667+000" date="05-18-2016" component="TSManager" context="" type="0" thread="1380" file="tslogging.cpp:578">

And BDD.log :

<![LOG[  Console > 
]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DiskPart successfully formatted the volume.]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Disk ###  Status         Size     Free     Dyn  Gpt]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   --------  -------------  -------  -------  ---  ---]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > * Disk 0    Online          465 GB      0 B        *]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Read-only              : No]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Hidden                 : No]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > No Default Drive Letter: No]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Shadow Copy            : No]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Offline                : No]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > BitLocker Encrypted    : No]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Installable            : Yes]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Volume Capacity        :  232 GB]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Volume Free Space      :  232 GB]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Partition 2]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Hidden  : No]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Required: No]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Attrib  : 0000000000000000]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Offset in Bytes: 250052870144]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume ###  Ltr  Label        Fs     Type        Size     Status     Info]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   ----------  ---  -----------  -----  ----------  -------  ---------  --------]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > * Volume 4     C   Data         NTFS   Partition    232 GB  Healthy            ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Partition ###  Type              Size     Offset]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   -------------  ----------------  -------  -------]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Partition 1    Primary            232 GB  1024 KB]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > * Partition 2    Primary            232 GB   232 GB]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume ###  Ltr  Label        Fs     Type        Size     Status     Info]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   ----------  ---  -----------  -----  ----------  -------  ---------  --------]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume 0     E                       DVD-ROM         0 B  No Media           ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume 1     V   OSDisk       NTFS   Partition    232 GB  Healthy            ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > * Volume 4     C   Data         NTFS   Partition    232 GB  Healthy            ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Leaving DiskPart...]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Return code from command = 0]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found: DestinationOSVariable: V:]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDTargetDriveCache is now = V:]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDisk is now = V:]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Set the Tag variable: TargetPartitionIdentifier]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property TargetPartitionIdentifier is now = ]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property TargetPartitionIdentifier is now = SELECT * FROM Win32_LogicalDisk WHERE Size = '250051817472' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'F8D39FF7']LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[New ZTIDiskPartition : \\MININT-S630LVG\root\cimv2:Win32_LogicalDisk.DeviceID="V:"    \\MININT-S630LVG\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property DestinationDisk is now = 0]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property DestinationPartition is now = 1]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[DestinationDisk: 0]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Assume this disk is the destination Disk, and verify.]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[TargetPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '250051817472' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'F8D39FF7']LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Search for Drive: TargetPartitionIdentifier  SELECT * FROM Win32_LogicalDisk WHERE Size = '250051817472' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'F8D39FF7']LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found Drive: V:]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDTargetDriveCache is now = V:]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDisk is now = V:]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Target Drive Letter Found: V:]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found OS Drive: V   0]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[New ZTIDiskPartition : \\MININT-S630LVG\root\cimv2:Win32_LogicalDisk.DeviceID="V:"    \\MININT-S630LVG\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Check Disk [0] <> [0] OK to skip.]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[####### NOTE:  If this is one of the  last lines in your BDD.log file, check V: for the most up to date bdd.log!!!]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[ZTIDiskpart processing completed successfully.]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Event 41001 sent: ZTIDiskpart processing completed successfully.]LOG]!><time="03:17:16.000+000" date="05-18-2016" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">

Thanks for your help

Regards

The last year, with my first upgrade task sequence in MDT 2013 Update 1 : after the "upgrade OS" the applications were installed like that : (on the pc's administrator session)

Error: Unable to connect to UNC path - When try to make a capture using a USB Media

Hello, I prepared a Media (Advanced Configuration-Media) to make an offline deployment, in the same task I want to capture an image, but when I chose to save the capture in "D:\Deploy\Captures" (or any D:\) path, the "Unable to connect to UNC path" appears.

I think that I must configure something in the Bootstrap.ini of the Media, due this media will be used in offline location, I try only adding the path 
[Default]
DeployRoot=D:\Deploy 

but the error continues.

Any help will be appreciated.

---

Edilberto Martinez

So I am sure everyone is familiar with the way that MDT 2013 creates an Administrator account to capture and deploy images. 

My problem is that I could never figure out a way to have MDT convert the admin account it creates to a standard account. We need this for legacy reasons. I actually tried capturing a reference image with the 2 local accounts in it that I needed, one was a manually created admin account and one was a manually created standard account, but no matter what I did MDT always creates an administrator account to do what it needs to do. I tried to have it use the admin account I had already created but I had no luck with it. It seemed very stubborn.

FYI these are local accounts that I need. The computers we image are not joined to any domain. We need one admin account and one standard account. Has anyone had any luck doing what I am trying to do?

Thanks

Hello. I've setup a task sequence using the MDT template, and trying to do the baremetal scenario. I've configured the wizard with a domain (using both DNS and Netbios name) and some OU, the wizard is setup to validate user credentials.

The error message I receive in the UDI Wizard is: User Credentials are Invalid

Also in the OSDSetupWizard.log I've found a line that says:

Validate Domain Join Credentials
Failed to get DC  with code (54b): The Specified name either does not exists or could not be contacted

A ping to the domain dns name and a DC goes Ok.
Infrastructure: Single Site SCCM 2007 R3, plus MDT 2010 Update 1 installed before R3, MDT Extensions  there, Boot image created with MDT for this as well.

Any help on this will be great.

Hi folks.  Basically what I want to do is have the machines I deploy use the WSUS server on my network during deployment for the update steps in the task sequence but after everything is done I want them to use Windows Update from the internet going forward after initial MDT installation.  How do I do this?  Thanks.

Hi All

Following in the footsteps of the Windows 8.1 PoC Hydration Kit which I have used successfully post the 2-day EMS training I have downloaded the recently released version updated for Azure and on-premises.

Unlike the earlier version, I did not find the FormInstaller.exe, the InstallForm.bat or the LabCustomizer.XSN, so not sure how the new version should work if these files are no longer part of the kit.  Is it a case where the files from the previous version are compatible?   Also, the files available in the LabDefinitions folder - REF-AZ-EMS.xml and REF-OP-EMS.xml respectively, appear partially complete, could you confirm the state? 

Similarly, the Guides folder does not contain any doco.

Are these files available? Appreciate the help, cheers, jp... 

I have finally got bitlocker to work with my MDT TS. My issue now is that once MDT completes and Bitlocker is done of both my C and D drive and i click on Finish (my finish action is set to Restart), the system restarts and now it is asking for the Bitlocker Recovery Password. This now happens every time the system gets restarted.

Have i missed something out to get the OS to autounlock upon restart?

Below is my TS. Reference for the Bitlocker part in my TS, https://blogs.technet.microsoft.com/deploymentguys/2009/10/09/how-to-configure-bitlocker-on-additional-drives-in-a-mdt-2010-deployment/ 

Below is my CS.ini

BDEInstallSuppress=NO
BDEWaitForEncryption=TRUE
BDEDriveLetter=S:
BDEDriveSize=500
BDEInstall=TPMKey
BDERecoveryKey=AD
BDEKeyLocation=\\mynetwork location
TpmOwnerPassword=mypassword

In our lab environment we are running Windows 7 Pro clients with valid OEM licenses. We are using MDT Standard client upgrade task sequence to upgrade these devices to Windows 10 Pro. We followed the steps from the following pagehttps://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit. The upgrade goes well however the computers are unable to activate and we get an error stating “No key management service (KMS) could be contacted.”  The Windows 10 ISO we imported to MDT was downloaded from Microsoft Licensing Service Center. 

We created a second upgrade task sequence and placed our WIN 10 MAC key and we ended up with the same error as the first test

Please advise!