MDT 2013 and SMB 3.0

Hello,
I'm building an MDT environment using NAS boxes for deployment shares. The question is:
When running MDT on Server 2012 R2, would the NAS box need full support for SMB 3.0 for the deployment?
Thanks in advance
Brian.

No SMB 2 support will work.
SMB 3 will be faster but not a must.

Similar Messages

MDT 2013 and Windows Embedded Standard 7

Hi Guys
I'm currently working on a Windows Embedded 7 Standard build and deployment.
Looking at the support Matrix and the video from Johan, it looks like:
MDT 2010 has support with the hacked LTIAPPLY script
MDT 2012 onwards support Embedded POS Ready - no mention of Standard.
Can you clarify:
If WES7 is supported in MDT 2013.
Is there a set of specific task sequence steps I should use for deploying WES7? I will still need to run the standard pre-install to clean disk, gather vars etc.
I have written some post build scripts, which configures the FBWF state and installs final apps, which i'll run at the State Restore phase.
Many Thanks
Ian Fraser

Can you share your experience with MDT 2013 and Windows 7 Embedded? Are you deploying the SCCM client to the clients? Any scripts you can post would be helpful.

MDT 2013 and RES Automation Manager

Hi,
In one of the first step of MDT I'm using a simple script that asks for the country code (e.g. NL), which I would like to store in an environment variable, which I can later on read into RES Automation Manager. But it seems that after MDT is finished and
Windows starts up, the environment variable is gone. Are there any other ways to accomplish this? I'm using it to install language specific applications from RES AM, after MDT is finished. The Windows language settings itself I set with the
CustomSettings.ini, that is based on the same simple script
[Settings]
Priority=ByCountry, CountryAbbr,Model,Default
Properties=CountryAbbr, CountryOU,CustomProperty
[ByCountry]
UserExit=ZTIGetCountry.vbs
CountryAbbr=#GetCountryCode()#
[NL]
CountryOU=NL
CountryOrRegion=31
InputLocale=0409:00020409
KeyboardLocale=nl-US
UserLocale=nl-NL
UILanguage=nl-NL
TimeZoneName=W. Europe Standard Time
ZTIGetCountryCode.vbs
Function UserExit(sType, sWhen, sDetail, bSkip)
oLogging.CreateEntry "entered UserExit ", LogTypeInfo
UserExit = Success
End Function
Function GetCountryCode()
Set objShell = CreateObject("WScript.Shell")
Set objEnv = objShell.Environment("SYSTEM")
GetCountryCode = InputBox("Fill in Country Code (NL DE DA FR PT); If default, use None")
objEnv("MDT_Language") = GetCountryCode
Set objShell = Nothing
Set objEnv = Nothing
End Function
Any idea what I can do else??
Thanks,
Mario

Hi, this looks quite similar to my blog post I did some time ago:
MDT 2012 LTI Deployment, Regional and Locale settings based on #chars of Hostname
The trick in your specific case is to either, not reboot your machine, or to set the installation of RES Automation Manager right after the reboot.
Basically MDT clean's up it's act after it is finished. This also means the environment variables which are stored in a .dat file in the C:\MININT folder are removed after MDT has finished.
So either you need to find a way to perform your RES AM job, during the MDT task sequence, or set or dump the environment variables to a file are temporarily variable which RES AM can use.
Here are some articles that will help you get further:
MDT and RES Automation Manager – Let’s come together (in Sweet Harmony)
Creating custom variables in MDT 2013
Finding All References to MDT Variables in a Deployment Share: VariableDocumentor
v1.0
Dumping Task Sequence Variables
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

MDT 2013 and WES7

Hi,
I would like to know if anyone has succesfully deployed a WES7 or WES8 image using MDT 2013 litetouch. There seems to be support for doing this with WEP7 (POSready) but what about the Standard version?
I can make use of the startnet.cmd and imagex tool from a Windows PE, but it would be nice if MDT could be used to deploy images and apps to WES7 (or WES8)
BR
Morten

Hi,
I would like to know if anyone has succesfully deployed a WES7 or WES8 image using MDT 2013 litetouch. There seems to be support for doing this with WEP7 (POSready) but what about the Standard version?
I can make use of the startnet.cmd and imagex tool from a Windows PE, but it would be nice if MDT could be used to deploy images and apps to WES7 (or WES8)
BR
Morten

MDT 2013 and USMT 5

I've had MDT 2012 set up and working fine (with USMT 4.0), and have been utilizing the USMT via batch file to copy profiles and transfer them manually in some cases. I'm needing to move some people to Win 8.1 and between computers with 8.1, so I updated
to MDT 2013. As I figured, it broke everything I had going. After putting back the USMT files where they were, the batch files no longer work as they must be "run as administrators". I added my domain admin account as a local admin,
and even tried a plain local admin account. No go. For the life of me, I have no idea what the hang up is. Below is the batch file, what am I missing since this used to work fine? I also cannot simply run the scanstate.exe, and it flashes
a cmd prompt and closes before I can see what it's doing.
if exist "c:\usmt" then Goto SkipUSMT
echo d | xcopy \\server\folder\deployment\usmt\amd64 c:\usmt
cd /d c:\usmt\
set /P Input=Computer Name?
scanstate \\server\folder\deployment\captures\%Input% /i:migdocs.xml /i:migapp.xml /v:13 /uel:90
:SkipUSMT

Gives me nothing more than what I had:
2014-11-06 15:02:05, Info [0x000000] SCANSTATE.EXE Version 6.3.9600.17237[gle=0x000000b7]
2014-11-06 15:02:05, Info [0x000000] USMT Started at 2014/11/06:15:02:05.262
2014-11-06 15:02:05, Info [0x000000] Command line: scanstate \\SERVER\folder\captures\Computer /l:Scan.log /i:migdocs.xml /i:migapp.xml /v:13 /uel:90
2014-11-06 15:02:05, Info [0x000000] Failed.
2014-11-06 15:02:05, Info [0x000000] Administrator privileges are required to run this tool.
2014-11-06 15:02:05, Info [0x000000] USMT Completed at 2014/11/06:15:02:05.263
2014-11-06 15:02:05, Info [0x000000] Entering MigShutdown method
2014-11-06 15:02:05, Info [0x000000] Leaving MigShutdown method
2014-11-06 15:02:05, Info [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------
2014-11-06 15:02:05, Info [0x000000] * USMT error code 34:
2014-11-06 15:02:05, Info [0x000000] +-----------------------------------------------------------------------------------------
2014-11-06 15:02:05, Info [0x000000] | Administrator privileges are required to run this tool.
2014-11-06 15:02:05, Info [0x000000] +-----------------------------------------------------------------------------------------

Problem with ztisetbackground.wsf in MDT 2013 and Windows 8.1

Has anyone found a way to get ztisetbackground.wsf to work with a Windows 8.1 build after the WinPE phase? It works fine with Windows 7 builds.
Ad(Thanks)vance!
JJ

Unfortunately not. Doesn't look like it will be fixed in the upcoming release of MDT 2013 Update 1 based on the following post...
http://blogs.technet.com/b/mniehaus/archive/2015/03/03/mdt-2013-update-1-preview-what-s-changed.aspx.

MDT 2013 and the D: directory

I'm new to MDT since upgrading from 2012 to 2012 R2 and I'm not finding the specific logic in the OSD Task Sequence that keeps setting our OS drives to "D".
Where is it, can I change it, and what is the reasoning behind this drive choice?

OSDPreserveDriveLetter was already set to False.
Also it does not matter which captured OS image I use. Ever since I starting MDT this issue has appeared.
I have been reusing an older Windows 7 image and also captured a Windows 8.1 image straight off the media; both deploy with the OS on the D: drive.

MDT 2013 and locationserver.xml prompting for credentials

I have multiple locations we are sharing our DeploymentShare so we are using a LocationServer.xml file to pull from one of those locations. We have everything working except that we can not get rid of the credentials prompts.
Does anyone have a solution for that ?
Thanks
Don

Hi,
Have you replicated all the system folders in the Public Folder to the Exchange 2013 server, especially for the EFORMS REGISTRY folder since the Outlook will try to access this
folder when loading and Organization Forms templates.
Happy New Year!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

MDT 2013 and HP Elite 8300 CMT don't work

Hi!
I've got a Problem with booting into PE 5.0 on HP 8300 CMT with MDT2013
I always get Boot error: 0xc000000e, Info: unexpected error
I have allready injected all drivers (storage, NIC, graphics) but it doesn't work.
Problem exists with Litetouch-Partition and even when booting from USB-Stick (which perfectly works on Prodesk 400)
Any clues?

It is not clear to me if you are getting this problem when booting up WinPE, or after the OS is placed on the local hard disk, and booting into
Are you booting into uEFI mode or CSM mode? Crack open your bdd.log file after booting into WInPE, and search for isuefi.
Additionally, did you modify the diskpartitioning layout for your task sequence? If so you may have not set things up right, create a new task sequence with the partition set to 100% (the default).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

HP Client WinPE Driver Packs and MDT 2013

Just today I noticed that HP had a couple of WinPE driver Packs for download on their site for WinPE 3.0 and 4.0. I'm using MDT 2013 to deploy Win 7 x64 for now, perhaps Win 8.1 out in the future. What version of WinPE does MDT make for Boot Images? Which
driver pack would be best for MDT 2013 and Win 7 deployment? WinPE 3.0?
Orange County District Attorney

Just found my answer in a great post at
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Just in time!
Orange County District Attorney

For %TaskSequenceID% no longer working in MDT 2013.

I've used the blogs by Michael Niehaus to get MDT 2010 and MDT 2012 LTI deployment wizard application selection profiles working.
I'm now running MDT 2013 and when following the instructions here:
http://blogs.technet.com/b/mniehaus/archive/2012/09/04/revisiting-lti-deployment-wizard-application-selection-profiles.aspx, the MDT Wizard Displays the error: "No task sequences are available (TaskSequences.xml does not exist, is empty, or is inaccessible)."

Updating the deployment share seems to have resolved the issue.

MDT 2013 won't capture 8.1 image, does not boot to PE to capture

I am doing this with Server 2012 R2 and MDT 2013, and the reference machines are VMs
I initially created a deployment share for creating windows 7 and windows 8.1 reference images and capturing and deployment worked ok. After getting into some more details i customized the deployment share customsettings to make things easier and created
a separate capture share for capturing new reference images. I updated permissions on the share so my service account has access to it.
In this share i imported the windows 8.1 os files and copied the sysprep and capture task sequence i used to capture my first reference image [from the original deployment share], but when running the task sequence it reboots and just goes back into windows,
instead of windows PE to capture the image.
I copied a windows 7 capture sequence to the capture share, imported the windows 7 files and updated the task, and it rebooted into PE without a problem and copied an image. so I don't believe I have any permissions/customsettings problems with the new share.
Im not seeing any errors jump out at me in the bdd.log but I'm new-ish to going over the logs and using MDT to start with so I may be missing the obvious. I am using SMS trace and dont see any red/yellow highlites either.
In windows 7 i did have the vm in audit mode when i mapped the share as an admin and started the task sequence. In windows 8.1 i am not in audit mode [after doing some research and learning more about using MDT it did not seem necessary]
After comparing a run of the windows 7 task to windows 8 i see the boot.wim copied to the win 7 vm, but i dont see it on the win 8 vm. There is a partition created, i cant see data in it when i show hidden files.
rules for the capture share
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
Heres the last part of bdd.log. New here so I can't post a link yet, didnt know if i should post the whole thing here or not to start with.
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property PHASE is now = CUSTOM]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[--------- Script Start ---------]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[LTICopyScripts processing completed successfully.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[Creating startup folder item to run LiteTouch.wsf once the shell is loaded.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\LiteTouch.lnk" created.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property BootPE is now = ]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:32:24.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="E:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = E: C:]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[No task sequence is in progress.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Phase = CUSTOM]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentType = CUSTOM]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property ResourceDrive is now = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceDrive = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[SMS Task Sequencer already found on C:\MININT\Tools\X64]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Thanks for your reply.
The pc is not in the domain when i run litetouch. It was joined after install, then i run some local gpos/scripts against it, install all of the shared printers from servers, then i put it back in a workgroup, login as the local administrator, delete the
domain profiles and guids in the registry, briefly connected back to a domain server [not with a mapped drive] to copy a couple of files, rebooted into the local admin account an ran litetouch.
After running litetouch.wsf the first time in the windows 8.1 pro vm [no changes, but manual connection] it rebooted without sysprepping or taking an image
I deleted the task sequence and created another one with "sysprep and capture" as the sequence. i made no changes to the task sequence. did all of the above, ran litetouch, and it just reboots. sysprep does not run and windows pe does not load.
if i run sysprep and boot into audit mode [as a test, since my windows 7 vm snapshot was in audit mode when it runs litetouch.wsf], then run litetouch, sysprep works, then it DID capture an image, but after that image was capture and the VM rebooted, i got
this error when loading windows 8
"windows could not complete the installation. To install windows on this computer, restart the installation" and if i hit ok it will reboot and error out again.
Haven't had any issues with that VM until now.
I reverted to my snapshot and just ran sysprep oobe w/ generalize to see how it would react
it failed, setuperr.log shows SYSPRP failed to remove apps for the current user. some searching gives me information on that and makes me think its related to adding/deleting user profiles? i dont actually use or update the apps at all, i have a deploy task
that removed most of them and customizes the start screen and those seem to work without issue.
found this as my reference: http://support.microsoft.com/kb/2769827/en-nz
Sysprep has an additional provider that is added in Windows 8 to clean appx packages and generalize the image. The provider will only work if the Appx package is a per-user package or an all-user provisioned package.
and
Resolution
The correct way of removing the package is to remove the package for the user running sysprep and also remove the provisioning. This can be done using the following Powershell cmdlets:
Import-Module Appx
Import-Module Dism
Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation
if i run that i get a lot of
[unknown user]: installed
Do I just need to revise my process and start from scratch? or at least just never actually join the domain and user other profiles? thats a convenience thing so its not a big deal, really.
I have an image made in a similar way that works, but doesnt have quite all the updates/changes i wanted. It captured [at the time] fine and installs without issue
Heres an overview of what I do [i am open to some revisions on this]
-deploy windows 8 base install from MDT
-join domain, login with service account [just makes getting to some things easier]
-install office 2010 pro plus w/ sp2 [i do understand that these can be set as an MDT app but the install takes a while and i dont like waiting on it if i dont have to]
-install windows updates [no WSUs server currently, on my future to-do list, not my decision right now and i do understand the benefits of having one]
-connect to servers and install all network printers [we have so many that i dont want to wait on the drivers when we do a big roll out soon]
-install oracle software [i can get it to automate in windows 7, not 8, so i dont want to manually deal with it post-install]
-install adobe reader/java [i do understand that these can be set as an MDT app]
-leave domain, reboot, login as local admin
-clean domain profiles/registry guids
-make some local gpoedits [we dont have 8.1 enterprise and just want the start screen locked down]
-install our AV network agent
-lite touch.
any advice is appreciated

MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

First, let me give you some context:
Framework: MDT 2013 with MS SDK 7.1
Task Sequence: Standard Client TS with sysprep and capture.
Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

I have this issue intermittently as well. For us, it coincided with the deployment of IP phones, which meant PoE switches all around. However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
boot.
As this issue has been intermittent, I've backburnered it. When it does happen, I just wait for the lease to arrive then rerun the wizard.
Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on. Basically, what Keith Garner said. They also disabled PortFast awhile back to see if that made any difference, and it did
not.

MDT 2013 Windows 8.1 application install with reboot problem

Hello!
I have a problem with an application install on Windows 8.1. I'm trying to install two applications and have activated "Reboot the computer after installting this application" for the first application. After rebooting the deployment window does
not show up agagin. BDD.log shows, that the deployment starts after the reboot but seems to hang, before the UI shows.
I tried to install this two applications under Windows 7, which works without any problems.
Here is the BDD.log for the failed deployment: http://pastebin.com/PbUH1LUq
Can anyone confirm this problem with MDT 2013 and Windows 8.1? Any ideas how to fix this?
Additional information: Further testing showed, that this problem just occurs, if the application install gets started separately after deploying the OS. If the applications are installed in one deployment together with the OS, everything works fine.

I did the same install on Windows 7, which worked without any problems. Here is the log file: http://pastebin.com/Qgn2PzyC
To make it clear:
If I run a Lite Touch Install task sequence to install Windows 8.1 and install the two applications within this LTI, everything works fine. The computer reboots after installing the first application and the deployment goes on and finishes successfully after
the reboot.
If I first install Windows 7 or Windows 8.1 via LTI and then (after LTI successfully finished) start a separate application install (using a custom task sequence with only one "Install Application" task in it), everything works fine with Windows
7 (installation continues and finishes after the reboot) but fails with Windows 8.1.
In Windows 8.1 the computer reboots after installing the first application, but after rebooting, the installation does not start again.
Keith, as you said, my environment is corrupted, I created an new fresh deployment share, just added the two test applications and the custom task sequence and tried again. Same result, Windows 7 works fine, Windows 8.1 fails by not starting the installation
after the reboot.

MDT 2013 Fails to Format or Partition disk on Surface Pro 3

I have been trying to image a Surface Pro 3 using MDT 2013 and have been unable to get past the Format and Partition portion of the deployment. At first I would get an error that it was unable to format or partition the drive and then after that it
just reboots after trying for so long. I am able to image any other device with the same task sequence and have no issue just having an issue with the Surface Pro 3. Any help would be great.
Thanks in advance.
I am getting the error FAILURE (5210)
ZTI Error - Unhandled error returned by ZTIDISKPART: Object required (424)

I think our problem is also hardware failure although without re-imaging a working surface pro 3 I can't be sure.
I tried what imfusio suggested in this thread.
https://social.technet.microsoft.com/Forums/en-US/d31384bc-4e96-4a5b-a400-637bd6006d81/failure-5456-unable-to-determine-destination-disk-partition-and-or-drive-surface-pro-3?forum=mdt
Unfortunately the deployment failed with the same ZTI Error - Unhandled error returned by ZTIDISKPART:
Object required (424)
I then rebooted into WinPE and ran diskpart, I could see the two volumes (EFI and OSDisk). I then tried to format the OS disk volume using diskpart. I got a paramater is incorrect error and the disk was no longer visible with a 'list disk' command. So it's
like the format is putting the disk offline. I'm going to try restore one of these surfaces, apply all firmware updates then re-image. If that doesn't work I'm out of ideas.

MDT 2013 and SMB 3.0

Similar Messages

Maybe you are looking for