I have several remote deployment shares on my network. I have monitoring turned on and is pointing to my central MDT server. We are a large enterprise and image thousands of computers each year. MDT meets our needs without spending the money for SCCM.
Is there a way to look at an active session and see what deployment share is doing the deployment?
If not, here's a suggestion for for the future! Maybe even add the user who is doing the deployment?
Howdy everyone, we are getting some bluescreens on our Dell laptops here and see that there are some urgent updates avaialble via Dell...these updates are not reflected in the recent cab file they provide...how can we inject these individual drivers so that we image our laptops with the latest drivers?
Hi , I am getting this error message when I try to update deployment share for AMD x64. I have MDT in a separate server and WDS in separate server. once the WIM is updated , I map the other server and update the boot image to the WDS to deployment.
This is the error message.
=== Making sure the deployment share has the latest x86 tools ===
=== Processing LiteTouchPE (x86) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x86.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x86.wim will be used.
Unable to mount the WIM, so the update process cannot continue.
=== Completed processing platform x86 ===
=== Making sure the deployment share has the latest x64 tools ===
=== Processing Generic (x64) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x64.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\Generic_x64.wim will be used.
Unable to mount the WIM, so the update process cannot continue.
=== Processing LiteTouchPE (x64) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x64.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x64.wim will be used.
Unable to mount the WIM, so the update process cannot continue.
=== Completed processing platform x64 ===
=== Processing complete ===
Please help,
Thanks
I am new to using MDT/WDS and have followed the directions "https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/prepare-for-windows-deployment-with-mdt" to setup and deploy Microsoft Windows 10 and everything is working great but when I try to add new OS's either Windows 8.1 or Windows 7 both Pro versions with their separate Task Sequences and separate drivers I keep getting the nice pink screen stating "Failure (5627) -2146498547 0x800F080D Run Dism.exe /Litetouch Deployment Failed / Failed to run the action: Install Operating Systems. Operation aborted (error: 80004004; Source: Windows Failed to run last action"
I'm using Server 2012 and MDT 2013.
Any assistance would be greatly appreciated.
I am setting up a Deployment workbench to deploy Windows 10 Enterprise IoT 2016. I am working on a standalone PC and the deployment will be made by creating a bootable ISO. I have all of this working. I am creating a new user account and need to copy a couple of command files to the user directory before I create the iso image.
The user directory structure is not created until the user logs in for the first time, so I tried creating the user home directory and copying the files to that directory. When I do this and the user logs in for the first time, the home directory becomes some strange name instead of the directory I created.
Is it possible to create a new user account and force it to create the user home directory structure in MDT?
I am currently using a command file that executes "net user NewUser NewUserPassword /add /homedir:c:\Users\NewUser" to create the user account from MDT.
Hi guys ,
when i setup win 10 from external media on usb 3 ,pc failed to boot ,the media is created by mdt
but when i setup with usb 2 i have not probleme ,
it also when i upgrade win 7 to win10 from sccm or mdt task and external media is connected on usb3 ,the packages is copied on external hard drive and setup is failed on reboot and return to win 7 ??
anywhone can help me
IE closed Unexpectedly every day. tried below:
1. update Java to lastest version
2. Clear IE cache, Reset IE, Uninstall/Reinstall IE
3. update Anti-virus, Run Virus full Scan
4. SFC /Scannow
5. disable crash recovery in IE advanced setting
all above is not working.
could you please advise if other solution can be try.
thanks
Where can I find the MDT 6.3.8443 MSI? I cannot find it anywhere. Thank you for your help.
Nicholas
Hi,
How to Remove edge and set Internet explorer as default browser either during creation ofreference image or osd.
How to do changes the internet explorer settings during osd or during refernce image creation .
How to use Internet Explorer Administrator Kit in mdt
Please help
Thanks
Hello everyone,
I would like to know if it is possible to deploy a machine with LACP teaming pre-configured in MDT.
Right now we are deploying machines using one NIC and setting up teaming manually afterwards.
Desired configuration is automated deployment with 2 NICs configured as a team. (OS: 2012 R2, 2016)
Thank you very much for you ideas/replies.
Kind regards,
Jan
Never seen this one before. MDT 8450 with ADK 1809.
When trying to generate boot image I'm getting following error. Any ideas?
or:
Hi All,
Just needs some help with MDT 2013 which is on Server 2008 R2. I have added drivers for some Dell machines along with my Lenovo drivers and regenerated the deployment image and added it back into WDS Boot image.
Now when i try building the computer, I tested on Dell Optiplex 3020 and older Lenovo X220i. The Dell completed the image fine but the Lenovo has just stopped after installing the OS in a blank DOS screen.
Now we use databases in our organisation for MDT 2013 and also the drivers a injected using the following
DriverGroup001
Windows 7\%Make%\%Model%
below is some of the bdd log file. I can't seem to upload or add the whole log file as it exceeds the character limit.
<![LOG[Property LTIDirty is now = FALSE]LOG]!><time="09:54:26.000+000" date="10-10-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="09:54:26.000+000" date="10-10-2014" component="LiteTouch" context="" type="1"
thread="" file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="09:54:26.000+000" date="10-10-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="09:54:26.000+000" date="10-10-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
Any advice would be appreciated.
Thanks
Hi All,
I'm using MDT 8450, ADK 1809, on a Windows Server 2016 and I'm getting a Failure (5615): False: Boot Drive was not found... Failed to run the action: Install Operating System.
1. This is a new Dell OptiPlex 7060 and I've tested on three of the same model
2. Using the latest WinPE10 Drivers
3. UEFI partition is set to GPT, not MBR.
4. BIOS is set to boot w/UEFI, Legacy Options ROM turned on, SecureBoot Turned Off, NIC Stack w/PXE Support enabled, AHCI instead of RAID
5. Same image of Windows 10 Ent. build 1803 works on OptiPlex 7050 and older as well as Latitude 5480 and older booting into Legacy BIOS.
6. Operating System installs to 100% and promptly generates the error. Immediately I run DiskPart and under drive 0 I see the following...
Volume 0, Letter D, Type DVD-ROM
Volume 1, Letter E, Label Windows, 460GB, NTFS, Partition
Volume 2, Letter F, Label Recovery, 5392MB, NTFS, Partition
For some reason I can't understand, it cannot grab drive letter C. It appears to format successfully using UEFI and creating the necessary partitions. According to the LTIApply log, it applies the .WIM file successfully but is unable to find the boot drive. From the LiteTouch.log, my OS drive is E:\ thus my error. I'm at a loss at this point as to why this is occurring. Is something within the Dell BIOS disallowing C:\ to be used?
Hello all!
I really need your help as this is making me going crazy...
So i have installed MDT latest version with AIK latest version all to deploy windows 10 1709 kms iso.
I setup MDT with sql database as i have multiple locations to manage; the setup went fine without problems or errors. So now i have put only windows 10 OS, created the pxe boot drivers disk from Dell pxe v10 download, created roles, locations, models, task sequences and uploaded the needed drivers.
On the SQL server the database is up and running and all tables/views seem to be there.
Now when a new pc boots it fires up the pxe boot and the task sequence and all seems ok until the step where the custom settings are loaded and the different SQL sections are loaded.... it all goes fine until loading the LPACKAGES section. Until here it goes fast for each section but from here it is slow and generates errors on the logs.
I cant understand why this happens.... please HELP!
Hi There,
We have modified unattend.xml file which we want to use when running sysprep in MDT. How can we place the unattend.xml file and what is the location, so that MDT automatically picks it and apply sysprep?
Any help would be much appreciated!
Thanks,
Sourav
Born to Learn
Hi,
We have a task sequence which deploys Windows 1803 with 5 language packs and their feature packs. When I deploy this task to a VM machine it runs fine without a problem.
However when we deploy the task to a physical machine the task stops at applying image (Install Operating System) at 40%. Actual there are two pass, the first one completes to 100% then we see it applies dism.exe with an unattend.xml which resides in the C:\Windows\Panther folder. After dism.exe there is a second pass of the task "Install Operating System" Weird is, it always starts at 30% and get stuck at 40% without an error message. I looked at the unattend.xml which MDT creates. I think it will be created from the unattend.xml which belongs to the task sequence and the packages to apply. It seems that when deploying the task to a physical machine there is a problem to work down the unattend.xml. As a test we modified the task sequence for the task "apply patches" to selection profile "nothing". Then the task runs fine on the physical machine.
We tried several physical machine and all have the same issue. However deploying the task to a VM runs just fine.
Any idea what is different between deploying to a VM and physical machine?
Thanks
Edy
Edy from Switzerland
Back to WSUS in my org again...
I am going through the setup Wizard and I see all the Products listed. I'm pretty clear on the Classifications, which I'm instructed to choose Critical, Definition and Security updates. I believe the Classification updates you get are based off
of what you choose in
the Products list.
I don't believe I need things like Office 365 updates, as we push those out in LanDesk.
What I don't understand in the Products list is all of the Windows versions. We're using Windows 1803 today. I most definitely do not want driver updates during the MS Updates. I only see things like 1703 and drivers, or 1803 and drivers. I just want Critical,
Definition and Security updates for 1803.
I do see Windows 10 box. If I check that, will that include everything from 1511 to 1809?
I also realize that once you download updates to WSUS, it's pretty impossible to wipe them out and start over.
So my question is...I just want Critical, Definition and Security Updates for 1803. Which Product items do I select for this?
Thanks
Hello,
i want a automatic installation of Office 2019 deployed with MDT (as application).
With earlier versions of MS Office i did by : setup.exe /config proplus.ww\config.xml
I think this is not possible anymore with Office 2019.
Until now i can deploy office 2019 with the setup.exe and configuration-Office365-x64.xml
My xml-file is:
<Configuration>With this setup, the volume licensing version is downloaded, and installed.
Problem:
After starting an Office Application, office must still be activated with the same key.
Anybody having a (better?) solution for the deploying Office 2019 with mdt?
Anybody having a solution for the activation-problem?
Thx
I downloaded my MSDN iso of v1809 a few hours ago and also noticed the new ADK is available.
Is MDT 8450 able to work with Windows 10 v1809/ADK v1809?
Thanks,
B