Search the Community

Hi, I am using MDT 2012 on a 2008R2 Server. Have been trying to build a laptop via a Task Sequence that I havent tweaked in any way since I created it a long time ago and it is still building a week later (admittedly I am only at the school half a day per week). It was takings its time installing Windows Updates so I have removed the two steps from the Task Sequence. Are there any other steps that get added in as standard that I can remove to speed up the deployment process?

Im new to using MDT and im not sure if its able to do what I want it to do. I have created a Windows 10 image and got it ready for capture. Normally, I would plug in a network cable and capture the image using WDS. The problem is, the laptop is a Lenovo Flex 10 which doesn't have a Ethernet port, this means no network boot. What I want to do is use MDT to create a USB stick which runs the sysprep and capture sequence offline so then I can capture the .wim to my external HDD. I then want to use MDT to create another USB stick which I can use to build the rest of the laptops with the image I captured. Please can someone help me with this? I've trawled the web for a guide on how to do this but haven't been able to find anything.

Hey Guys, Just recently, my WDS server has been asking for me to type in my deployment share when i boot into PXE. It never done this before, and i only have 1 deployment share. Oddly enough, it only does it on the 32bit boot image. If i boot into the 64bit boot image, it doesn't ask for the deployment share. I have attached an image for reference. It doesn't stop us from using WDS here, but it is annoying as there is no reason for it to come up. I have completely regenerated/updated the boot image so i can't see that being a problem. Any help is much appreciated. Regards, Harry Greatorex

Probably the wrong forum area but does anyone know if there is going to be a new version of MDT (Microsoft Deployment Toolkit) any time soon? I'm kind of the unofficial guy who obtains the most up to date installers for software at work - and yes, I know I'm incredibly sad

Hey Guys, I built 2 custom PCs with the exact same hardware. My issue is deploying an image through MDT to the machines. I created a new deployment share and new task sequence to deploy Windows 7 Pro x64. I also added in the Mobo drivers to inject during install. When I deployed the image on the first PC it worked fine. When I deployed the image on the second identically built PC, it will always have an error on starting windows. iastorA.sys is corrupt or missing I created a 2nd task sequence and downloaded the chipset/lan/video drivers from the manufacturers website so they are the latest version. I created a new selection profile to inject only the new drivers. Upon system reboot into Windows, instead of the first error I got BSOD and an immediate crash. I'm not sure why this image will deploy to the first PC but not the second. I can redeploy the image on the first PC with no problems. I am about to do an OS build from scratch on the second, then do a sysprep capture to have a copy of the custom image and I can try deploying that out to both PCs. Time is of the essence here. I only have another day or so to play with these before they need to be deployed out. Any insight into the MDT deployment issue would be appreciated. Build: - ASUS P9X79 LE Motherboard - 32GB Corsair Vengeance Pro quad channel kit DDR3 1866MHz - Intel Core i7 4820k 3.7GHz - Samsung 840 Pro SSD 256GB (OS Disk) - 2x 4TB Seagate Desktop HDD Sata3 (Raid 1 from BIOS) - eVGA GeForce GTX 780 SuperClocked 3GB DDR5 *Note*: On the second build I had the Samsung as Disk 1 instead of Disk 0, so the OS got installed on the Raid. I've fixed this issue, but the error messages as described above are the same.

Hi all, Im having an issue with my mdt 2012 deployment and the OU where the computer account is to go. I have set the ou's in the customsettings.ini like this: DomainOUs1=OU=clients,OU=sales,DC=,DC= DomainOUs2=clients,OU=engineering,DC=,DC= and every single time the task sequence fails to join the domain, but everything else works fine. However, if I have the OU's set up like DomainOUs1=OU=clients,DC=,DC= it works fine! My setup is 2008r2 deploying windows 7 x64. I have installed the ADK but everything was fine with WAIK. I have tried creating a DomainOUList.xml and put it in the scripts folder, but that didn't work. Any help would be great thanks!

Apologies if this is in the wrong section. I am attempting to deploy Policy Central Enterprise v6 via MDT. I have set it up as an application with a batch script running "msiexec /i PCEgpo.....msi /qn". I have Java 8.66 also deploying via MDT application (this works perfectly with a /s after the .exe name). However, PCE6 is failing to actually install even though Event Viewer logs and MDT deployment logs both say it was successful. I am using the Combo MSI and .NET 4.5.2 is in my custom WIM. Does anyone have any ideas where to look? I have previously tried having the msiexe /i [msi name] /qn as the application command line but nothing doing. It is MDT 2012 Update 1 with ADK version 8.59.25584 and Windows 7 x86 clients.

Basically i have setup my Deployment Share with 2 seperate task sequences one for Windows 7 Enterprise 32bit and one for 64bit both also have their own driver folder x86 and x64 respectively which they point to Bascially this is the only manual process (apart from name and OU which i want to keep manual) which i want to automate What i am trying to do is basically get MDT to query the amount of RAM that the machine currently has from the BIOS etc and point it to either 32bit if 3.5GB RAM or lower / 64bit task sequence if 4GB +?? Thanks Jack

Hi I was wondering if there was a way to change the background when MDT is doing the Post - Install part of the task sequence?? I have a very professional one for the boot image but I feel it would look just that bit better if it could continue to the post install stage of apps and updates, is this possible?? Kind Regards Jack