I built a new MDT server on Server 2016 following this guide. https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/prepare-for-windows-deployment-with-mdt Everything went pretty much according to the documentation and I tested my
first production image on a VM and I was able to PXE boot and deploy the image right away. For my second test I tried to deploy to a new Dell 7480 laptop which is a UEFI device and it just fails right away. I am not using any DHCP helper setting
as the DCHP server, MDT server, and laptop are all on the same subnet. I have been reading pages and pages of documentation over the past couple days and everything I find shows that it should just work. Even the guild says it will automatically
detect bios or UEFI. If I switch the Dell laptop to legacy bios mode it works just fine. If I switch my VM to UEFI bios it fails as well. I'm pretty much pulling my hair out at this point and I already don't have much left. Any
ideas would really be appreciated.
↧
New MDT build on Server 2016 won't deploy to UEFI devices
↧
MDT 8443 - Install Roles and Features - Server 2016 Task Sequence
I'm currently trying to get the "Install roles and features" deployment window to appear during the running of the MDT task sequence from SCCM for imaging Server 2016 so they can be manually selected during OSD. According to the documentation this window should appear as a default unless you add SkipRoles=YES in the CustomSettings.ini file, this does not work so either I'm doing something wrong or there may be a bug.... any help appreciated it's driving me nuts!
Thanks
Dave.
↧
↧
MDT Windows 7 FAILURE 5627
Hey all,
A little while back, our Windows 7 deployment image stopped working completely (Windows 10 still works fine). The error message I get is:
<![LOG[Return code from command = -2146498547]LOG]!><time="10:43:57.000+000" date="08-01-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[FAILURE ( 5627 ): -2146498547 0x800F080D: Run DISM.exe]LOG]!><time="10:43:57.000+000" date="08-01-2018" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Command completed, return code = -2147467259]LOG]!><time="10:43:57.000+000" date="08-01-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="10:43:57.000+000" date="08-01-2018" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="10:43:57.000+000" date="08-01-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
SMSTS is a bit more helpful. I found the following information:
<![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="0" thread="1636" file="string.cpp:1364"><![LOG[Failed to run the action: Install Operating System. Unknown error (Error: 000015FB; Source: Unknown)]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="3" thread="1636" file="instruction.cxx:921"><![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="1" thread="1636" file="utils.cpp:6143"><![LOG[Set a global environment variable _SMSTSLastActionRetCode=5627]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="0" thread="1636" file="executionenv.cxx:662"><![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="0" thread="1636" file="executionenv.cxx:662"><![LOG[Clear local default environment]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="0" thread="1636" file="executionenv.cxx:801"><![LOG[Let the parent group (Install) decides whether to continue execution]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="0" thread="1636" file="instruction.cxx:1033"><![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="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="3" thread="1636" file="instruction.cxx:221"><![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="0" thread="1636" file="string.cpp:1364"><![LOG[Failed to run the last action: Install Operating System. Execution of task sequence failed. Unknown error (Error: 000015FB; Source: Unknown)]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="3" thread="1636" file="engine.cxx:246"><![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="1" thread="1636" file="utils.cpp:6143"><![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="10:43:57.170+480" date="08-01-2018" component="TSManager" context="" type="3" thread="1636" file="tsmanager.cpp:1240">I've tried rebuilding the Task Sequence from scratch, as recommended in other places, as well as trying various Win7 images we have, but have had no luck. The CCM folder message seems telling to me, but I can't figure out where to go from there. Any assistance would be appreciated.
↧
LiteTouch Deployment Failed. Return Code = -2147467259 0x80004005
I received this error on a laptop that was sent back to me for re-imaging. When I set it to start with all parameters set, I received this error. I then went into a command line and did a clean on disk 0 to clear all volumes and partitions. When I went to perform the deployment over again, I got the same error message. Looking through the logs, I am unable to determine exactly what caused this failure. I have attached the log files generated from the deployment to a public sharing site. Below is the link to the log files themselves.
https://1drv.ms/f/s!AnkJZ7azSrQpbxulrqvCSjfUCBU
↧
Can not find script file "Z:\Scripts\LiteTouch.wsf"
Hi,
I installed and configured MDT 2013 yesterday on server 2012. I have a WDS also. I am able to create a WIM file. I did PXE boot into a test virtual machine and I was able to install Windows 10. My MDT is also on vmware ESXI. MDT server is joined to my domain.
I created a task sequence with "sysprep and capture". On the vm that I want to capture I mapped the deployment share and I tried to run the "LiteTouch.vbs" I got the following error:
Can not find script file "Z:\Scripts\LiteTouch.wsf"
I am confused because "LiteTouch.wsf" is just below the vbs file.
This is the first time I am trying to capture an image on the newly built MDT.
Please let me know what I am doing wrong or what I can do to resolve this.
Thanks,
Boris The Blade
↧
↧
MDT- Not enough space on the disk
Hi
I'm trying to capture an image of a machine using the 'Capture Machine' task sequence on MDT 2013 Update 2.
But when I go to do it I get 10 errors and 2 warnings:
------------------------------------------------------------------------------------------------------------------------
ZTI ERROR - Unhandled error returned by LITApply: (-2147024784 0x80070070)
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Apply Windows PE.
There is not enough space on the disk (Error: 80070070; Source: Windows)
The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Apply Windows PE. execution of task sequence failed.
There is not enough space on the disk. (Error: 80070070; Source: Windows)
Task sequence engine failed Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetnamedSecurityInfo() failed
SetObjectOwner () failed 0x80070005
-------------------------------------------------------------------------------------------------------------------
So I went into DISKPART for Disk 0 and had a look at the partitions:
Partiton 1 Recovery 450MB
Partiton 2 System 100MB
Partition 3 Reserved 128MB
Partiton 4 Primary 57GB
My assumption is that it is trying to install the Windows PE onto Partition 1 first that doesn't have enough space? I can't find anything in the task sequence that lets me change the 'Capture Machine' task sequence to use the whole disk or selected partitions and I know you cannot change partition numbers in DISKPART.
Also, what does it actually mean when it is trying to 'Install Windows PE'?
I can't do a clean install of windows because it is a Zebra Industrial tablet and doing a clean install of windows gets messy because there are no driver downloads on their website, only an installation image. I've tried extracting the drivers from a working tablet into a clean installed one but had no luck. The touch screen or network does not work.
Any ideas and suggestions will be greatly appreciated.
↧
Litetouch script runs again before Final Summary....why?
MDT 2013 w/ current ADK trying to deploy Win10 1803 Education.
I can successfully deploy an OS but before the final summary is shown the litetouch script runs again. I choose the OS and name like I was gonna image then it runs the clean up script and shows the final summary. I don't know what is causing the wizard to run twice. It just started happening and I believe it has to do with the CustomSettings.ini or Bootstrap.ini but not sure. I was messing with those when I was trying to get SYSPREP and CAPTURE to work. I changed it all back for our Production$ but wonder if I missed something or is it something completely different. I have created new Task Sequences but they are affected as too.
↧
Not enough memory available to create a ramdisk device
We're struggling with trying to deploy a Windows 7 image created with MDT 2012 via Windows 2008 WDS to an HP notebook. We boot through WDS and then when we choose the OS to deploy we get a Windows Boot Manager message
Status: 0xc0000017
Info: There isn't enough memory available to create a ramdisk device.
Anyone seen this before?
Orange County District Attorney
↧
Sophos cloud Install via MDT
Hi
I se MDT latest version 8450 and normally i have a task to install sophos with the command sophossetup.exe --silent upto the latest version this was installing fine, however now i get a box thown up after a while stating bdd.exe has crashed. i close this box and the rest of my install carry on installing.
whilst i know the latest sophos install is to blame , when i run this command whilst logged in as a user once windows is on the machine this works no problem. If i contact sophos they will just say its MDT thats the issue. Anyone else seeing this or know how to resolve this?
↧
↧
Win 10 Sysprep - Why did my PC Restart? after every instance of sysprep
This has happened 5 times - on 5 different computers.
I remove the apps (CandyCrush, etc)
Run sysprep - OOBE, generalize with no errors
After I copy the image using Ghost
I start the computer, it takes me to the "Hi there" screen where you set the time zone and language
Click Next and I get "Why did my PC restart".
↧
Issue with MDT Monitoring
We have discovered an issue with MDT Monitoring which I hope can be addressed in the next release of the toolkit. There is some inconsistency in what is reported as the "computername" to the Windows Event Logs during a deployment.
Event 41016 (Deployment Started) appears to be using the BIOS Serial Number
Event 41015 (Deployment Completed) appears to be using the OSDComputerName
We use Scheduled Tasks based on Event Triggers to email the technician and log basic information to a deployment database when a deployment completes. In most cases, the BIOS Serial Number and OSDComputerName are the same so there are no issues. In cases where the 2 do not match, it isn't possible for us to find all events in the event log related to the deployment.
I have enabled the EventShare option and can see that the 41016 event has the correct computer name, however the event log entry has the serial number of the machine instead. I have browsed through the relevant scripts in the deployment share and it appears that this issue is occurring in the monitor service. Is it possible to make is so that the events are always written using a consistent computer name?
Sample CreateEvent below:
EventShare entry:
41016,4,,win7-ref,OSD00000,OSD00000,0,0,UNC
NEWCOMPUTER,UNC
LTI beginning deployment
EventLog entry:
<ProviderName="MDT_Monitor" />
<EventID Qualifiers="0">41016</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2017-08-25T14:17:54.000000000Z" />
<EventRecordID>21239</EventRecordID>
<Channel>Application</Channel>
<Computer>wds1.richland2.org</Computer>
<Security/>
</System>
<Data>Deployment started for computer VMware-56 4d eb 54 be 5c 62 00-c8 25 70 3a 47 72 37 e4.</Data>
</EventData>
</Event>
↧
MDT not updating the correct computer name for event 41016
hey all ,
when deploying an application the event 41016 has the correct name but if you do a full deployment the name doesn't get updated from the auto generated default.
however it does look like the monitoring server does update the name correctly.
see attached screen shots.
thanks
https://social.technet.microsoft.com/Forums/getfile/1301743
https://social.technet.microsoft.com/Forums/getfile/1301744
↧
Lenovo Ultra ideapad will not boot from anything but HDD
I am trying to get the machine to boot underneath the OS to dParted. But no matter what I do (what I know about to try). nothing will get it to boot frlma USB or a DVD. The windows 10 disk has a partition which is also volume that only uses 27GB, the size of both the partition and the volume size Since I can't get much software to load up on it. I have changed The direction that the program code will go to a D: drive, the there are components of a program that must dwell with the components of the OS, which still fills it up, leaving it locked up.
Sorry. I just noted that I am asking a question that is not MDT . Maybe there is something the MDT can do to help this situation?
Regards,
John Beale
↧
↧
USB Media - TS not starting
I have updated my deployment image with Windows 10 1803 and recreated my USB media, when booting with the USB stick it starts the deployment wizard and when I am done selecting the deployment options (domain join, applications,...) the computer screen goes black and the laptop reboots.
It does that on all model i tried.
I am deploying Dell laptops only, grabbed the latest WinPE drivers and and recreated my boot images.
I cannot get any logs so I am not sure where to look.
↧
MDT Asset from SQL DB
Hello
I am trying to deploy machine using Assett number for the MDT Database
has any on succeeded in doing this obviously if i use the %assettag% variable i get the bios
asset tag which is of no use to - any help would be appreciated
↧
CopyProfile not working for me MDT 2013 deploying Windows 10
Hi Folks,
I'm a relative newbie to MDT technology, having used ghost for my whole career. I've been using a couple of technet articles on , first, creating a windows 10 reference image using MDT 2013, and then , second, deploying that image to a computer. I'm happy with the results so far except I'm confused about copyprofile . I can't get it to work and the articles/tutorials I'm using don't cover this.
These are my current steps:
1. Create a deployment share called MDTBuildlab to create a reference image. As part of this process, I accessed the unattend.xml through Task Sequence -> OS Info tab and followed the steps to enable CopyProfile. As i added a suspend action in the Task Sequence, I customized the Administrator profile to my liking and resumed the successful creation of the reference image.
2. I created a 2nd deployment share called MDTProduction and imported the image file I created earlier. I didn't do anything in Task Sequences except enable Microsoft updates and I disabled "Restore user States and "Restore user groups." However, i did modify the boot.ini and customsettings.ini files to add the computer to a domain. This step works fine.
When I deployed the image to a computer and logged on with a domain user account, none of the desktop shortcuts and other default user profile modifications seem to have took. I'm wondering if I should have edited the unattend.xml file in the Production share as opposed to the reference build image creation?
Any suggestions?
Many thanks Adrian
↧
Restoring MDT with DFS-R
Our MDT server took a "hit" and all information was lost, including backup. We were using DFS-R to replicate MDT data at our nine other sites. Can we use the data that is stored on one of our other servers to make our main server fully functional
again. This would reduce the amount of time rather then from starting from scratch. Just looking for some guidance here. Any help would be appreciated.
↧
↧
Windows 7 Deploy FAILURE 5627
Hey all,
A little while back, our Windows 7 deployment image stopped working completely (Windows 10 still works fine). The error message I get in SMSTS log is:
<![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="0"thread="1636"file="string.cpp:1364"><![LOG[Failed to run the action: Install Operating System. Unknown error (Error: 000015FB; Source: Unknown)]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="3"thread="1636"file="instruction.cxx:921"><![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="1"thread="1636"file="utils.cpp:6143"><![LOG[Set a global environment variable _SMSTSLastActionRetCode=5627]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="0"thread="1636"file="executionenv.cxx:662"><![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="0"thread="1636"file="executionenv.cxx:662"><![LOG[Clear local default environment]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="0"thread="1636"file="executionenv.cxx:801"><![LOG[Let the parent group (Install) decides whether to continue execution]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="0"thread="1636"file="instruction.cxx:1033"><![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="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="3"thread="1636"file="instruction.cxx:221"><![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="0"thread="1636"file="string.cpp:1364"><![LOG[Failed to run the last action: Install Operating System. Execution of task sequence failed. Unknown error (Error: 000015FB; Source: Unknown)]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="3"thread="1636"file="engine.cxx:246"><![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="1"thread="1636"file="utils.cpp:6143"><![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="10:43:57.170+480"date="08-01-2018"component="TSManager"context=""type="3"thread="1636"file="tsmanager.cpp:1240">I've tried rebuilding the Task Sequence from scratch, as recommended in other places, as well as trying various Win7 images we have, but have had no luck. I also tried playing with my boot and bios config in the Task Sequence. The CCM folder message seems telling to me, but I can't figure out where to go from there. Any assistance would be appreciated.
↧
MDT 2013 deployment failure 5624
HI All
Have built a new MDT 2013 server upon a windows 2012 box, currently getting the following error when deploying Windows 7 image only all Win 8.1 and 10 images deploy fine. Can any one help with ?
FAILURE (5624): 1392 Run DISM: /Apply-
Image /ImageFile:\\HUYTONSC\DeploymentShare$|Operating Systems\Win 7 x32 Sp1 July 2015\Win 7 x32 Sp1 July 2015.wim index:1 /ApplyDir.F:
Litetouch Deployment Failed, Return Code -2147467259 0x800004005
Have tested the same images on a MDT 2010 server running Server 2k8 and also in a lab setup before hand and they all performed as expected and deployed fine.
Applied the MDT 2013 update 2 hoping that would resolve but it didnt, have also deleted and re added the images they work for 1 deployment and then fail there after
Banging my head on the table right now
Cheers
↧
Can WDS be installed on Windows 7?
I was wondering, if Windows Deployment Services can be installed on a Windows 7 machine?
↧