Working MDT 2013.
Empty new MDT 2013 in nearby building. I saw somewhere in MDT settings an option allowing to copy the content from one MDT to another... Would it make a "mirror"? So after copying DS content a new one will provide seamless deployment experience?
Or additional measures should be taken?
Thx.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
Hi
New to MDT side of things.
Is it possible to capture an existing working machine (eg. Surface Pro 3), and then re-deploy to another Surface pro 3?
I assume the process will be to sysprep, then capture to WIM, then redeploy? Will MDT do that without too much pain?
I don't need to build a reference machine from scratch using MDT.
Thanks,
DM
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)
We are using MDT2010 and now MDT2013 for years now. I must make a new deploymentshare for 64 bit Windows 7 but cannot find in my documentation where to put the MAK key in MDT for later activation when Windows 7 is deployed.
I have looked in MDT where i have put the MAK key but cannot find it anywhere, not in custom settings / bootstrap.ini, any task sequence etc.
Searching the Internet the MAk key must be put when importing a operating system into MDt but i have never done that. After deploying Windows 7 to a client i activate the system at once, the MAk product key is somewhere stored, i have done that myself but do not know where.....
Is there some standard point where i must put the MAK key in MDT, when syprepping and capture task sequence or in a deployment task sequence or in the customsettings.ini / bootstrap.ini within the capture deployment or deploymentshare?
This is neccessairy because i want to capture and deploy a new Windows 7 but now 64 bit in MDT so the key must be put somewhere..
It can be put in the virtual machine that is goiing to be captured. After installing WIndows in the VM put in the product key, but maybe this key is lost when importing and deploying thru MDT...
It can be somewhere in the sysprep and capture task sequence although i cannot find it
In the deployments task sequence cannot find them here also
Int he rules.ini or bootstrap.ini of the captureshare or deploymentshare but here also not found..
freddie
I created USB WinPE key using x64 boot image.
It worked 2 times. I connected to MDT share and deployed images on Lenovo E455 that uses Realtek driver.
MDT server and computers are on the same LAN. (new office with no vLANs)
What is weird that now I am trying to boot the same machine and get:
"A connection to the deployment share could not be made. Cannot reach deploy root.
Possible cause network routing error or network configuration error. "
Don't think USB key is a problem.
When F8, I get APIPA...
Any driver was not imported to boot images. It is fresh MDT2013
In Out of box created DriverGroup001. Updated DS but don't think it could affect boot images.
And as mentioned it worked find I booted the machine. All my Out of box were installed correctly.
What could happen with the Boot image?
Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
Hello
I have the above
I want to sysPrep and capture this windows 8.1 machne that has a UEFI boot.
When i run //MDT2013Server/PAth to deployment share/ scripts/Litetouch.vbs
The machine sysPreps and then re-starts to do the capture, but then stops with the message of lossing connection to the deployment share.
I have been into the bios to see if i can chnage the boot to legacy bios and not UEFI but im unable to chnage this.
SO how do i capture the UEFI boot machines?
Thanks
Mark
Environment: MDT 2013 to deploy Windows 7 Enterprise SP1
Dear all,
I try to deploy a golden image on a Lenovo T450s but when "Setup is installing devices" step is running, it takes HOURS where it should takes some minutes normally.
The golden image is deployed on others models of machine without issues.
So I guess it's something related with drivers of my T450s.
I opened and check the setupapi.app.log in C:\Windows\inf and I can read the following at the end of the file:
! cci: !NCI: Op=BIND, Layer=NDIS, Upper=Tcpip6 Lower=\Device\{12C305D7-0A57-4C63-A965-6F5A0B1FE255}, Error=00000019
I have no idea of what this mean.
Opening the file setupapi.dev.log I can see some sections with an exist status. The first section with an ERROR is the [Setup online Device Install (Hardware initiated) - pci\ven_8086&dev_9cb1&subsys_503417aa&rev_03\3&1d1156d0&0&a0] section and refers to USB 3.0 Controller. It starts at 09:49:04 and ends at 09:54:10 with [Exit status: FAILURE(0x000005b4)].
Then the next Section start 2015/04/29 09:49:05.197 and end 2015/04/29 10:19:13.303 with [Exit status: FAILURE(0x000005b4)] etc...
So do you guys know what all this mean and how to find a solution to avoid this step to take so long?
Thank you,
See below error...
Do you have any items for me to start with troubleshooting?
Made selection profile, setup media, did the OEM prestage task and dumped it to the drive... and on boot I start up the machine and it can't find the deploy folder... it is there on the disk I can see it in command prompt.
I am working to familiarize myself with MDT and I keep getting stuck at the same point. I seem to be setting up my deployment share, importing the OS (Win 7 x64 Enterprise), importing drivers, and a few applications, adding a task sequence, and updating my deployment share, all without error.
I'm then creating creating a bootable PE usb flash drive and copying the LiteTouchPE_x64.wim file into the \Sources folder and renaming it boot.wim.
I am able to boot from the flash drive and I get the blue Microsoft Solution Accelerator background but instead of the deployment wizard menu options I'm just getting a command prompt at X:\windows\system32
I've been back over my steps several times but can't see anything I'm missing. I would think if there was a communication issue between my reference machine and the deployment share I would still get the wizard but it would fail when I tried to install. Could be wrong though.
I'd appreciate any thoughts or suggestions.
Thanks in Advance!
I am new to the MDT scene and created a task sequence for our laptop builds. During the deployment TS it pauses on an empty command prompt windows and waits for you to exit it before it continues. Nothing is showing in the logs and I have narrowed it down to the post install phase between "Next Phase" and "Restart Computer". Ive checked the ZTINextPhase & ZTIWinRE scripts as best i can but found no reference to using a command window.
Is this something anyone else has seen?
Alright, I've found out the option 66 & 67 information, as what to set for each. The problem I'm trying to figure out is what to use for the boot file for option 67. So far all the info I've found says this:
Configure DHCP option 67 with the right boot image file.
For 32-bits systems \boot\x86\wdsnbp.com
For 64-bits systems \boot\x64\wdsnbp.com
I want to be able to use this for both 32 and 64 bit Windows clients, but cannot find anywhere that specifies how I would be able to do both.
Is there a way to get LTI Wizard to prompt to add user or users to local addmins ?
Ive already added a rule to the customsettings.ini Administrators001=Domain.com\SupportAdmins which is fine as its allways needs to be there on every machine.
However most machines have a secific user or users that need to be set as local admin, I was hoping thre is a way for the Build process to ask for this during the setup.
Hello everyone.
MDT 6.2.5019 on Server 2012.
I'm in process of building very big task sequence for server reference image.
Sometimes, I will receive LTI error that path was not found for example for my Vmware driver store where I keep my VMXNET3 driver for the reference image and sometimes it will do the same on Install Operating System Step.
When I receive path not found error, I can see that Z: drive is mapped fine and I do not see anything out of normal when error occurs. Logs appear to be fine, except this path not found error.
Here is the kicker. When I go back to the same task sequence in MDT and edit it, disable Inject Drivers step or Install Operating System step (depending on which one failed on me this time), hit apply, then OK, then reopen task sequence again and un-check the check box to disable failing step and apply and OK changes, everything goes back to normal, for a while ... :)
To sum this up, it appears that it will happen randomly, I would say 1 out of 10 tries to build the task sequence reference image will throw that error. Editing task sequence and making random change, like disable something, apply and re-enable it back fixes the problem.
Am I encountering some sort of bug?
I went through known issues list for MDT posted on Technet and could not find anything relating to what I see.
I would appreciate any input you might have.
Thanks!
Hi there,
does my MDT 2013 with Version 6.2.5019.0 works with Windows 10 TechPrv or do I have to upgrade to another build ?
I tried out to bind it to an new created task-sequence but after applying the WMI/ISO file while installation, the first boot
failes with:
NTLDR is missing ...
Kind regards
Jens
Hi,
i'm trying to build a Domain Controller (Windows Server 2008 R2 SP1) using MDT 2012.
I created a Standard Task Sequence and append the following:
The task sequence itself is working fine till it comes to the "Configure ADDS" Step. Here it fails showing me the following error code:
ERROR - ADDS role configuration with DCPromo failed , rc = 42
ZTI ERROR - Non-zero return code by ZTIConfigureADDS, rc = 42
Here is my ZTIConfigureADDS.log , any ideas what went wrong?
Thanks a lot !
Regards, Stefan
<![LOG[Microsoft Deployment Toolkit version: 6.0.2223.0]LOG]!><time="16:31:23.000+000" date="06-14-2012" component="ZTIConfigureADDS" context="" type="1" thread="" file="ZTIConfigureADDS"><![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="16:31:23.000+000" date="06-14-2012" component="ZTIConfigureADDS" context="" type="1" thread="" file="ZTIConfigureADDS"><![LOG[---------------- Initialization ----------------]LOG]!><time="16:31:23.000+000" date="06-14-2012" component="ZTIConfigureADDS" context="" type="1" thread="" file="ZTIConfigureADDS"><![LOG[Generating DCPromo answer file]LOG]!><time="16:31:23.000+000" date="06-14-2012" component="ZTIConfigureADDS" context="" type="1" thread="" file="ZTIConfigureADDS"><![LOG[About to execute command: cmd /C C:\windows\system32\dcpromo.exe /answer:C:\Users\ADMINI~1\AppData\Local\Temp\AD_Answer.txt]LOG]!><time="16:31:24.000+000" date="06-14-2012" component="ZTIConfigureADDS" context="" type="1" thread="" file="ZTIConfigureADDS"><![LOG[ERROR - ADDS role configuration with DCPromo failed , rc = 42]LOG]!><time="16:31:34.000+000" date="06-14-2012" component="ZTIConfigureADDS" context="" type="3" thread="" file="ZTIConfigureADDS"><![LOG[ZTI ERROR - Non-zero return code by ZTIConfigureADDS, rc = 42]LOG]!><time="16:31:34.000+000" date="06-14-2012" component="ZTIConfigureADDS" context="" type="3" thread="" file="ZTIConfigureADDS">
I am enabling a WiFi card via Dell's CCTK, but if the card is disabled it requires a reboot before it is recognized. This causes an issue that after I run this and the LiteTouch task sequence attempts to detect and inject the drivers it does not see the Wifi. This results in Wifi driver not being injected.
I'd like to PXE to WinPE and perform the CCTK commands -> apply WinPE and restart machine -> boot back into WinPE without user interaction and continue with driver injection/OS install.
I have tried the following task sequence commands (from the Sysprep and Capture task sequence) without success:
cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE
cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE /STAGE
cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE /BCD
Any help would be appreciated.
Hi,
I am using MDT 2013 and I am trying to deploy server 2008 in it. I mount my 2008 iso file, import OS, then select full set of source files, and enter D:\ . It says, "The source directory does not contain an identifiable operating system". I am sure that install.wim file is present in sources folder. What other folders/files does it need while importing OS?
Note: it is an customized OS. It has MS hotfixes and dotnet 4.5 installation package in it.
Chaitanya.
Chaitanya.
I'm trying to image a Lenovo e555 with MDT but no matter what I've tried it seems to stop at the same point with out error. For context I'm using a standard task sequence with a custom WIM. I have had no issues with this setup in previous deployments for other models. I added the drivers for this deployment just like I have for other models. I am not using selection profiles. At this point the only drivers on my MDT server are the drivers for this particular model laptop.
So I boot as normal and start the task sequence. It injects the drivers and applies the OS. When it restarts after applying the OS it comes to a blank screen with no cursor. I've left the laptop on for several hours with no movement. I've go back and looked at the smsts.log and it appears as if the task sequence is creating a system partition and assigning it to C:. It then creates the OSDisk partition and assigns it to D:. I'm not sure why this is happening as previous deployments did not exhibit this formatting. I've attached the log for investigation. If anyone can assist I would appreciate it!
SMSTS.log http://1drv.ms/1PaZMg6
Where ever you go, there you are.
