MDT 2013 - Passing Deployment Tech's Credentials to a PowerShell AD script?

Hello,
I have a PowerShell script written to add a target machine to a specific AD Group.
This script is set to run as a custom Task Sequence.
Script:
$ADServername = Get-ADComputer $env:COMPUTERNAME
$group = Get-ADGroup -Identity "ADGruopName"
ADD-ADGroupMember -Identity $group -Members $ADServername
The issue is, at the time of this task sequence, the server is logged on and running as the local administrator.
The deployment tech's credentials are held as: "%UserDomain%\%UserID%" "%USerPassword%" in PowerShell throughout the MDT deployment process.
How can I pass those credentials to the script without prompting the user/deployment tech?
Thanks!

If you are using the MDT Powershell Host provider the MDT environment variables will be available as:
$tsenv:UserID
$tsenv:UserDomain
$tsenv:UserPassword
However, if you are just joining a domain, you should use the variables explicitly set aside for joining domains:
$tsenv:DomainAdmin
$tsenv:DomainAdminDomain
$tsenv:DomainAdminPassword
Additionally, MDT already has built-in features for adding computers to specific OU's using: MachineObjectOU.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Similar Messages

Using MDT 2013 for deploying Software from MDT Server to PC Client automatically and silently ?

I have a trouble about deploying software from MDT 2013 server to PC Client , Can we using MDT 2013 for deploying software automatically and silently , that Users/Clients don't have to click "next,next" to install software ?
If you have a solutions to deploying it , please share me about that solutions ?
Thanks.

you can make software silently with boot opción:
with chocolatey opensource.
or make software with switches
here link to help you:
http://blogs.itpro.es/octaviordz/2014/05/29/instalando-aplicaciones-con-chocolatey
http://blogs.itpro.es/octaviordz/2014/06/05/integrando-chocolatey-a-mdt-2013-e-instalando-aplicaciones-de-forma-desatendida-en-windows-8-1/
http://blogs.itpro.es/octaviordz/2014/10/31/probando-chocolatey-en-windows-10
http://blogs.itpro.es/octaviordz/2012/07/10/aplicaciones-desatendidas
MVP Jesús Octavio Rdz http://blogs.itpro.es/octaviordz

MDT 2013 - Litetouch deployment failed, Return Code = -2147467259 0x80004005

I'm attempting to deploy an image that I have recently captured with MDT. I was able to capture the image without any problems and after capturing, it booted up properly. But now when I go to deploy the image using a Standard Task Sequence it
errors out. It does boot into WinPE and gets to the installing operating system portion then spits out the following 8 errors:
(5624):2: Run ImageX: /apply "\\PDC31089\DeploymentShare$\Operating Systems\Win7_BUP_1-31-14\Win7_BUP_1-31-14.wim" 1 C:
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015F8; Source: Unknown)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015F8; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005After I receive the error messages if I attempt to restart the computer and allow it to boot up it just comes up with:"An operating system wasn't found. Try disconnecting any drives that don't contain an operating system"
I have tried the following to resolve this issue:
Create a new deployment share with only network drivers added and the one .WIM that was captured with MDT as well as one Task sequence.
Update to MDT 2013
Update Deployment share and completely regenerate Boot images
Tried starting deployment from within Windows by mapping the drive and executing litetouch.vbs
Also tried starting deployment using USB boot disk
I'm running out of ideas and seem to keep getting the same 8 error messages. It's very aggravating and am hoping that someone can point me in the right direction.
I've included some log files on Skydrive at: https://skydrive.live.com/redir?resid=6375A8F9E8089918%21105

I came across this post recently. I am having the same string of errors suddenly when I try to deploy any image from my MDT 2013 server now. Previous images now fail to install soon after the Inject Drivers task sequence at the Install Operating System sequence.
Each time I try to deploy an image(have tried several each with different task sequences), I get the same 7 errors.
The errors produced are:
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Incorrect Function (Error: 00000001; Source: Windows)
The execution of the group (Install) has failed and the execution has been
aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Operating System. Execution of task
sequence failed.
Incorrect Function
(Error: 00000001;
Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
My HD size is 146GB with about 71GB being free.
The BDD.log file is too large to post here apparently. Here are the
last bits of it.
<![LOG[Assume this disk is the destination Disk, and verify.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart"
context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[TargetPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '499577253888' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'CA3BC8A9']LOG]!><time="11:36:58.000+000" date="09-26-2014"
component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Search for Drive: TargetPartitionIdentifier SELECT * FROM Win32_LogicalDisk WHERE Size = '499577253888' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'CA3BC8A9']LOG]!><time="11:36:58.000+000" date="09-26-2014"
component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found Drive: C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDisk is now = C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Target Drive Letter Found: C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found OS Drive: C 0]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[New ZTIDiskPartition : \\MININT-I3DUVLI\root\cimv2:Win32_LogicalDisk.DeviceID="C:" \\MININT-I3DUVLI\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="11:36:58.000+000"
date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Check Disk [0] <> [0] OK to skip.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[####### NOTE: If this is one of the last lines in your BDD.log file, check C: for the most up to date bdd.log!!!]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart"
context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[ZTIDiskpart processing completed successfully.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Event 41001 sent: ZTIDiskpart processing completed successfully.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread=""
file="ZTIDiskpart">

MDT 2013, Deploying Windows 8.1 on Surface and Dell Venue Tablets

I'm having numerous issues with Capturing Images and Deploying to Windows 8.1 Tablets. We are currently using Surface Pro 1, 2, and Dell Venue 11 Pro tablets. I am using a Windows Server 2012 computer with MDT 2013 installed. I can't get the tablets
to:
1-sysprep and capture using MDT 2013
2-Deploy a Task Sequence with a WIM and other applications attached. (I've tried using the simple standard task seq option with no luck)
3-I found another way to get a WIM (using imagex) but when i deploy task sequence it ignores my selection of applications to install outside the WIM and only installs the WIM (WIM 14gb = Win 8.1 Ent, Office 2013 x32, MS Updates)
Any help would be greatly appreciated. Everything is being performed within the LAN and with USB 2.0 thumbdrives for media.

Hi altimav8,
Are you trying to find out how to deploy Surface Pro method? Before capture the Surface pro image please download the latest drivers for the surface and made sure that they
were the only drivers that were going to be deployed. There have a specific MDT deploy support forum more about the MDT deploy related issue you can ask in MDT support forum.
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The related guide:
Surface Pro - Enterprise Deployment Quick Start Guide
http://download.microsoft.com/download/2/0/7/2073C22F-2F31-4F4A-8059-E54C91C564A9/Surface%20Pro%20-%20Enterprise%20Deployment%20Quick%20Start%20Guide.pdf
Thanks for your understanding and support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Deploy Office 365 Pro Plus using MDT 2013

Hello,
I'm currently evaluating O365 E3 and am specifically looking into what my options are for deploying Office 2013 Pro Plus when rolling out a new PC image. Currently I use MDT 2013 to deploy the image to new PCs and install Office 2010 along with other
applications. Can I use C2R with a config file pointing to a local repository of the installation files with MDT 2013?

Hi
This blog post by Rens will help you:
http://renshollanders.nl/2014/02/office-365-automatic-deployment-of-office-365-with-mdt/

MDT 2013, WDS, Server 2012 R2 multicasting not working rc = -1073740940

Hi,
I have been reading all over the internet and not able to find an issue that we are having. We have setup MDT 2013 and WDS on a Server 2012 R2 server. Unicast has been working fine for us and we have the PXE boot working great too. We have
recently tried setting up Multicast. Every time we try and deploy an image we receive the following error when the client tries to run the multicast. I have pulled this error from the ltiapply.log on the client. The error is:
Multicast transfer could not be completed, rc = -1073740940, falling back to using \\mdtserver\deploymentshare\operating systems. We have also made sure we have IGMP enabled on all our switching and VLan's. We have tested with mcast.exe
and Wireshark and the packets are hitting the machine for multicast but we always seem to get this error. Any help would be great.
Thanks,

MDT logs the output from the wdsmcast.exe command itself within the bdd.log file.
A quick scan reveals:
Multicast transfer to directory: C:\MININT\Operating Systems\BaseWin7x64_6_17_2014
<Message containing password has been suppressed>
Command has been started (process ID 776)
Console >
Console > Windows Deployment Services Multicast Client [Version 6.3.9600.17029]
Console > Copyright (c) Microsoft Corporation. All rights reserved.
Console >
Console >
Console > Operation Failed. [0x80070523].
Console >
Console > The name provided is not a properly formed account name.
Console >
Console >
Return code from command = -1073740940
"Not a properly formed account name"?!?!? What?
MDT will pass the user account credentials to the wdsmcast.exe command using the USERID value.
SO... What is UserID set to?
Property USERID is now = vdl-mdt\helpdesk ZTIGather 7/29/2014 8:27:55 AM 0 (0x0000)
Whoops! UserID should not contain the domain name, instead it should just contain the user name.
USERID=Helpdesk
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2013 Windows 8.1 Task sequence Stops After first Reboot. login

Hi There,
The issue I am having is that After the OS gets laid down, and the Windows 8.1 computer reboots, The task sequence does not continue. It fails everytime. There are not any obvious errors that happen in the process that I can see in the logs. But I have
customized this process quite a bit and I could use some help. We are deploying potentionally to over 30,000 computers.
The test machine I have been using is the Surface pro 2.
The interesting part is after a failure is if I start the process over again , boots into PE, then run diskpart manually from command prompt to Clean Disk 0, and then reboot and start the MDT task sequence, it will deploy fine.
I also have a custom step that copies the TS media from the stick to a Recovery partition I create. The user can launch a -re-image or MDT refresh from an Icon/script, which will unhide this "recovery partition", and kick off a lite touch refresh.
This works succesfully everytime. We have remote locations with very slow links, so MDT over the network or MDT integrated with SCCM is not an option at this time. So this is the solution.
I am attempting to use MDT 2013 to deploy Windows 8.1 Offline, and using GPT partitions.
I am using a custom Format and partiition Step, that call the CustomDiskpart.txt script from %deployroot%\Scripts.
I am also using a Split image, as multi partitioned EFI/NTFS USB sticks are not a possibility for us , also, the USB sticks capable of this are seen by MDT as a "fixed drive" anyways. Which can cause issues in itself. So the LTIAPPLY.wsf has
been edited to search and apply ther split .swm files. This works well.
After the Task sequence failure I have tried launching the Litetouch scripts from the C:\MINNINT folder manually to continue the sequence, but it doesnt do anything.
I don't want to always be running Diskpart manually before imaging a new OEM computer. I needa second pair of eyes on this.
Thank You in advance!

Hi,
Thanks Again for taking a look.
I checked the sysprep log in the image and they look fine. No errors.
As requested here are some logs. Let me know if I can provide anything else.
BDD.log
litetouch.log
SMSTS.log
Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine.

MDT 2013: WinPE Screen Resolution for Tablets not adapted

Hello guys,
I'm using MDT 2013 to deploy Windows 8.1 on tablets.
So, after generated the boot image including the right drivers inside, I boot up my tablets through WinPE (Boot on LAN).
Once WinPE initiated, I'm now in the Deployment Welcome Screen with a very low resolution. The welcome screen filled the entire screen. Worse, the next window is bigger than the screen.
So my question is, how to handle with this behaviour?
Thanks guys in advance for your help,

Hi,
Thanks for your help.
I've read few posts about injecting an Unattend.xml file in the boot image including this link you mentionned.
I'm not sure to be right but what I did is the following:
1) create a file called Unattend.xml with the following content:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
</component>
</settings>
</unattend>
2) put it in my "extrafolder" in order to be imported when I create the boot image through MDT.
3) once created, checked that the Unattend.xml file is in the root of my boot image wim file
4) import the new boot image into WDS
So, I've tested the new boot image in at least 3 different kind of computers (tablet, laptop and desktop), the result is the same: the machines restart automatically when they try to load the MDT Welcome environment.
What's wrong?

MDT 2013 - Create New User

Hello,
I've recently setup MDT 2013 to deploy some customized images that we deploy to student laptops, that were sysprep-ed and captured with ImageX. I've uploaded the custom image WIM files to MDT, and setup a task sequence. Almost everything works,
thanks to Microsoft documentation and searches of this forum for various questions I've had, however I'm stuck on two items:
1.) MDT forces an administrator account to be created during the process. That's not such a huge issue, but I'd like to disable the administrator account at the end of the task sequence. I'm not sure where/what to add to do this.
2.) We would like the machine, after imaging, to deploy the generic Windows Welcome, as if it had just been purchased from the OEM. This way when the student receives the imaged laptop, they can create their own personal account. These laptops are
not bound to AD. Right now, when the task sequence finishes the systems are logged in as an administrator. Again, I'm not sure what code to add to the task sequence (and where) to accomplish this.
Any information or links on what I'm looking for would be greatly appreciated. I'm sure that both these items are possible, but I'm not using the proper terminology on my searches to find the information I'm looking for. Thanks!

I question the usage of MDT in this scenario. I also question your premise that your users should go into OOBE Setup.
MDT is designed to assist IT departments in getting windows up on machines in a End to End scenario.
MDT prompts which Task Sequence, Language/Locale/TImezone, Applications, drivers, and User Data Migration Status. Once the TAsk Sequence has started, MDT should be as automated as possible. No prompts, no user interaction.
What you are asking for is the opposite, you want user interaction during deployment, and rather than customizing each deployment, the image is pre-configured. (Unless you have different *types* of machines that require driver loading via MDT).
IN your case I would recommend just slapping an install.Wim up on a WDS server, and custom crafting an unattend.xml file to prompt each user for user accounts. (as long as you don't have to worry about drivers).
The other solution is to prompt the user for their new user account from the MDT wizard, and slam that into the machine during the task sequence (and removal of the Administrator account with net user administrator /active:no )
I actually created a powershell script to accomplish this:
http://keithga.wordpress.com/2013/09/24/microsoft-account-automation-in-windows-8/
This alternative solution is MDT 400 level work. Scripting required. :^(
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

MDT 2013 Wizard page not skipping

Hi all,
I am trying to reduce the amount of user intervention required for MDT 2013 to deploy a Windows 7 SP1 32 bit system from a Windows Server 2008 Standard box and I'm progressing well however, I've discovered that a wizard page won't skip. Specifically the
one that asks you to confirm time, time zone and date settings which appears right before MDT progresses to installing applications.
Here are the rules I have configured for my deployment share:
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
EventService=http://x.x.x.x
SkipLocaleSelection=YES
SkipTimeZone=YES
KeyboardLocale=0809:00000809
UserLocale=en-AU
UILanguage=en-US
TimeZone=255
TimeZoneName=AUS Eastern Standard Time
From what I've read, if you use a Skip wizard page option, there are prerequisite settings you must configure such as the keyboardlocale, userlocale etc and I've also gone through the MDT help topics andd found a table that contains these settings however
what I've found, is that although MDT will set the correct keyboard location and time zone settings, it still asks me to confirm it before proceeding to the installation of applications.
Am I missing anything? Does the order of the rules matter? Not sure what else to do.
Thanks in advance for any advice.

Yea, that should work, code snippet from DeployWiz_Definition_ENU.xml is:
<Pane id="SelectLanguageUI" reference="DeployWiz_LanguageUI.xml">
<Condition><![CDATA[ UCase(Property("SkipLocaleSelection")) <> "YES" or UCase(Property("SkipTimeZone"))<>"YES" ]]> </Condition>
<Condition><![CDATA[ Property("DeploymentType")<>"REPLACE" and Property("DeploymentType")<>"CUSTOM" and Property("DeploymentType") <> "StateRestore" ]]> </Condition>
</Pane>
IF you are still having problems, please copy your bdd.log file to a public share like OneDrive, and post the link here.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

KeyboardLocale and SystemLocale during UDI Wizard (MDT 2013)

Hi
We're using SCCM 2012 R2 integrated with MDT 2013
we deploy Windows 7 with Task Sequence process with UDI Wizard
we have 2 main problems regarding the Language Settings
1. in the wizard we define UserLocale, KeyboardLocale and UILanguage, OSDTimeZone
what about SystemLocale ? which is very basic to set, but there is no built-in combobox for it.
the only workaround I can come up with is to build a custom page with that setting but it is hard to create a combobox with all the available languages, even when editing the XML directly and not via the UI.
2. if I set the KeyboardLocale to Hebrew for example in the Wizard, the SMS environment variable is set to 0409:0000040d
this causes the deployment to end with Hebrew installed with US keyboard layout. which is wrong!
I expect the value to be 040d:0000040d (Hebrew keyboard with Hebrew layout)
which brings me to another question... how can I define multi keyboards? because my actual goal is to have English as my default keyboard language and to have Hebrew as a secondary keyboard.
it is not Hebrew in particular. we deploy Windows in 20 different sites worldwide and English should be always be the default language and we want to add another local additional language
I added a script that modifies the keyboardlocale and converts it from 0409:00000### to 0409:00000409;0###:00000###, but I feel like it is too much for this little setting that should be so basic...
any help will be appreciated. thanks
Tamir Levy

Hi,
Here is video for your reference.
Configuring MDT 2012 UDI Replace Computer Scenario
http://technet.microsoft.com/en-us/video/configuring-mdt-2012-udi-replace-computer-scenario
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WINPE User & Keyboard Locale with MDT 2013 & Windows 8.1

Hi
I'm using MDT 2013 to deploy win8.1 (ADK 8.1 installed and so on) but I'm having trouble to set the keyboard layout when the Wizard (hta) is loaded.
We are serving multiple countries so different keyboard settings need to be pushed for our operators when they go through the Wizard in boot.wim/PE phase.
I opened up the boot.wim file that is generated when you update the deloyment share and generate the litetouch boot iso.
In there I see that a basic unnattend.xml is being used which specifies the 0409:0000409 (en-US) locale.
I was under the impression that if we made different Task sequences with their own unnattend.xml we could set the WINPE locale in the WINPE phase via the amd64_xxxx_WINPE_Neutral_xxxx component but it doesn't seem to work that way.
I know you can provide a locale in bootstrap.ini but that's a general setting for
all deployments ...
Anyone any ideas?
My next step would be to add skipbdewelcome screen in bootstrap.ini and then have some sections in the customsettings.ini (bound to gateway or site or whatever) to set LOCALEs in there ....
jgs

Hi,
Sorry for my dilatory reply. According to your description, I doubt whether your Unattened.xml file was set correctly.
To set default InputLocale during deployment, the correct format should like this:
<InputLocale>0409:00010409</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UserLocale>en-us</UserLocale>
From:
http://technet.microsoft.com/en-us/library/cc749191(v=ws.10).aspx
In addition, here is another thread which is similar with your problem, may be helpful with your question:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/9af61b5c-6407-44b9-87c4-a4044a94729c/change-regional-settings-keyboard-layout-and-locale-in-task-sequence?forum=configmgrosd
Roger Lu
TechNet Community Support

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 deploying OS from USB Flashdrive failed - need to click OK everytime

We are using MDT 2013 with ADK 8.1 and deploying Windows 7 x64 using media (USB Flashdrive). We can successfully deploy Windows 7 x64b using ethernet cabel but not via USB-Flashdrive. This problem appears on all our HP EliteBook
Series, old as new computers series. We can boot into WinPE 64 bit and start the proper task sequence, all image is applied then after restart, after the logon screen appears there is an error saying that cannot find "USB media?".
But after clicking "OK" it works fine until next reboot, same thing again, but the drive is recognized!
I downloaded all USB drivers from HP website that holds USB 2.0 and 3.0 and drivers that contains open driver files like .inf and .dll files and injected them with the "Profile" that contains all drivers and packages.
It seems like it needs a timeout because of the script is trying to early to find the USB-flashdrive.
Any ideas?
Sorry for language, but you get the Point.
Best regards

Hi,
I would like you to clarify following questions with me:
1. Did you keep the USB plugged in during the restarting?
2. Have you make any task sequence to install applications after log in? If so, have them been installed properly?
Then, please help to collect a boot trace to let me know the details:
How to collect a good boot trace on Windows 7
http://blogs.technet.com/b/jeff_stokes/archive/2012/09/17/how-to-collect-a-good-boot-trace-on-windows-7.aspx
Please upload them to a file sharing service like Onedrive or "Rapidshare" and put a link to them in your reply.
Kate Li
TechNet Community Support

MDT 2013 - Passing Deployment Tech's Credentials to a PowerShell AD script?

Similar Messages

Maybe you are looking for