Hi. I volunteer at a community center. We have a single server (recently upgraded to SCCM 2012 R2) and 20 workstations (a mix of Win 7 and 8.1). The latest version of MDT 2013 is installed. I implemented LTI deployment w/Server 2012. Now with SCCM, I'd like to do ZTI

I’m following Technet tutorial Prepare for Zero Touch Installation of Windows 8.1 with CM.  I’m having a problem at step Configure the Network Access Account

1. Per an earlier step in the guide (Create Configuration Manager service accounts) I created a user account in AD for user CM_NAA
2. Now I'm following instruction to config Network Access Account. I drill down to Configure Site Components-> Software Distribution.
3. Their sample directions next say
   

In the Network Access Account tab, configure the CONTOSO\CM_NAA user account 
(select New Account) as the Network Access account. Use the new Verify option to verify that the account can connect to the \\DC01\sysvol network share.

Our domain name is cohcybercenter

• When I setup the Windows User Account and click Verify, I get an error (snapshot below)
• I also don’t understand: When I created user account CM_NAA in an earlier step I already assigned it a password. So why does it have me assigning it a password again? If password is different, does it supercede the one I assigned when i created the user in AD?
  
  

We're using MDT 2013 Update 2 with WDS on a Windows Server 2012 R2. We have a mixed enviroment with Windows 7 and just started moving over to Windows 10. Over all everything works more or less as it should. But specifically with Dell Latitude E5450 we have massive problems. Deployment constantly fails at some (random) point in about 65-75% of all computers we have tried to install windows 10 on (about 200 E5450's so far). And this is bare-metal installations. Not upgrades.

The most common error is "bddrun has stopped working". This occurs on random applications when ever the computer feels like it. Also every now and then application installations fails with an error message claiming that another installations is already running or that reboot is needed. And as I said; It varies exactly where the errors occurs. It's not always on the same application/step.

And sometimes the computer tries to swith to wireless network mid-deployment, so it stops. Sometimes it installs 2 or 3 applications and then suddenly it fails with error message "unable to set working directory".

All computers get the same Win10 REF-image and is deployed with the exact same Win10 task sequence. We have about 40 different computer models in our enviroment. Mixed with Dell, HP, Lenovo, Microsoft Surface etc. But Dell Latitude E5450 is the only model that acts this way with Windows 10.

I've managed to fix some hiccups by completely removing all Windows 10 E5450 drivers from the MDT (we're using total control driver assignment btw) and letting Windows 10 install it's own drivers instead.
If I imported Dell's driver CAB for the E5450 to the MDT I got some weird errors when Windows 10 decided to start updating all drivers mid-deployment.

So... I've been rambling on for a while now and I'm sorry for that. I guess my question is this: Is there anyone else out there that has any experience in deploying Windows 10 to the Dell Latitude E5450 using MDT 2013 Update 2? I'm at a loss here.

//Andreas

I have installed MDT2012 but when starting getting the error: Initialization error Powershell.

Installed on a server 2008 32 bit. Powershell is added thru the feature Windows oponents. Having read the SCCM Blog from Guy that has the solution for this problem. Unfortunally the commands are not working on my powershell.

First starting the powershell command prompt as administrator then:
get-executionpolicy
The output for this command is as the screens: restricted

But then it goes wrong: powershell isn't recognizing the command: get-executionpolicy -list en also not the third command...

Help! i cannot go further to use MDT2012...

freddie

Is there anyway to modify the progress bar,especially the "=====".Can't stand it....

Ok, so a little bit about my setup. I'm using MDT 2013 U1. I have a wim of Windows 7 Pro 64 SP1.

I am attempting to deploy to a Dell Precision 7710. This device uses 2 M.2 PCIe SSD's in RAID1 (using Intel RST).

I have added Hotfix 3366972 by injecting it into the wim using dism (using this https://support.microsoft.com/en-us/kb/2990941 method). I did NOT inject the hotfix into the boot wim, because it is WinPE 10, so should be supported natively (my Windows 10 installation disk can install to the drives without issue). I have also injected the Intel RST f6flpy-x86 (downloaded from https://downloadcenter.intel.com/download/25165/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver ) drivers into the boot wim, and have the f6flpy-x64 drivers injected into the installation.

I can boot into the MDT boot wim just fine. I select my task sequence, it deploys, and reboots. Upon booting Windows, the PC has a BSOD. When attempting to boot into safe mode, it halts at DISK.SYS before BSOD'ing. Obviously it doesn't like that.

I have attempted booting into an installation disk and removing DISK.SYS from C:\Windows\Drivers or C:\Windows\System32\Drivers, I cannot remember which at the moment. I didn't expect that to work because it was specifically disk.sys, and it didn't, but I figured I'd tried because I've had success removing other faulty drivers before. I have also tried reinstalling the RST drivers by booting into an installation disk and using dism to inject the drivers directly, with no effect. As a last ditch effort, I even tried running a chkdsk /f, which didn't work.

I have never had to deploy to NVMe disks before, and I am truly stumped. I know my org's switching to Windows 10 come March / April, but we haven't converted yet, and our images aren't "Golden" yet, so my manager isn't allowing us to just image this one with 10 early.

Anybody with any ideas?

Hello,

I'm trying to join a pc to an AD security group during a MDT 2012 Task Sequence with a VBS script. I'm running the script during the TS as another user. I'm getting error 0x80004005. I've run the script in Windows as another user the script just works.

I've tried several things, but I can't let it work.

I hope someone can help me

Thank you

Edward de Ruiter

MDT 2013,  WDK 8.1, running on W2k12 R2.  Using to create Windows 7 x64 media.  I have been using the deployment for several years.  I was recently importing new model drivers to the deployment share when I encountered the index error. I have turned nothing up on internet searches so I am posting here.  Below is the output from the driver import:

Scanning directories for the count of INFs to import.
Expanding CAB file C:\Workdir\W7 Drivers\7710\x64\audio\NJJGX_A00-00\production\Windows7-x64\MaxxAudio_Data.cab
Expanding CAB file C:\Users\Administrator\AppData\Local\Temp\MaxxAudio_Data.cab.extract\maxxaudio_data.cab
Expanding CAB file C:\Workdir\W7 Drivers\7710\x64\chipset\2JYGG_A00-00\production\Windows7-x64\stdcfltn.cab
Expanding CAB file C:\Workdir\W7 Drivers\7710\x64\video\F5D6C_A00-00\Production\Windows7-x64\MB-64-4287.inf\10.18.15.4287\DisplayAudiox64.cab
Performing the operation "import" on target "Out-of-box drivers".
Copying existing item Realtek Semiconductor Corp. MEDIA HDXADC.INF 6.0.1.6080 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item Realtek Semiconductor Corp. MEDIA HDXADCMA.INF 6.0.1.6080 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item Realtek Semiconductor Corp. MEDIA HDXADCMAX6.inf 6.0.1.6080 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item Realtek Semiconductor Corp. MEDIA HDXADCMAX7.inf 6.0.1.6080 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Intel DPTF dptf_acpi.inf 8.1.10602.174 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Intel DPTF dptf_cpu.inf 8.1.10602.174 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Intel DPTF dptf_pch.inf 8.1.10602.174 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Intel DPTF esif_manager.inf 8.1.10602.174 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named ST Microelectronics DiskDrive stdcfltn.inf 1.00.00.12 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named STMicroelectronics System ST_Accel.inf 2.2.3.7 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Intel System heci.inf 11.0.0.1166 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item Intel Ports mesrl.inf 11.0.0.1136 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System baytrail-iSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System braswellSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System broadwellSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System commonSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System cougarpointSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL USB cougarpointUSB.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System haswellSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System ivybridgeSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System lynxpoint-hrefreshSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System lynxpointlpSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System lynxpointSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System pantherpointSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System sandybridgeSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System skylakeSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System sunrisepoint-hSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL SDHost sunrisepoint-lpSDHost.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System sunrisepoint-lpSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System valleyview2System.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL USB valleyview2USB.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL System wildcatpointlpSystem.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item INTEL USB wildcatpointlpUSB.inf 10.1.1.9 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item Intel(R) Corporation USB iusb3hub.inf 4.0.0.36 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item Intel(R) Corporation USB iusb3xhc.inf 4.0.0.36 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Realtek Semiconduct Corp. MTD RtsPerX.inf 10.0.10240.21281 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Intel(R) Corporation System tbt70x.inf 15.2.34.12 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Intel(R) Corporation Net tp2p70x.inf 15.2.34.4 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Intel(R) Corporation USB ausb3hub.inf 15.2.30.11 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Intel(R) Corporation USB ausb3xhc.inf 15.2.30.11 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Alps Mouse Apfiltr.inf 10.1207.101.103 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Creating new item named Dell Inc HIDClass DellRctl.inf 1.0.0.4 at DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item Intel Net E1C62x64.inf 12.10.29.0 (3) from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.
Copying existing item Intel Net E1D62x64.inf 12.13.17.4 from DS002:\Out-of-Box Drivers\Dell Inc.\Precision T3620 to DS002:\Out-of-Box Drivers\Dell Inc.\Precision 7710.

System.Management.Automation.CmdletInvocationException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.Collections.Generic.List`1.get_Item(Int32 index)
   at Microsoft.BDD.PSSnapIn.Verifier.AddDriver(String theInfFile)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.BDD.Wizards.DriverProgress.WizardProcessing()
   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

I do not know what is causing this or how to correct this.  I really do not want to create a new deployment share (unless this is the only option).

Hi,

I'm trying to deploy Windows 10 Enterprise LTSB and my deployment task fails in several areas. The built-in administrator account shows nothing when logged in but a black screen and a mouse pointer. Logging in as another local user sees the log in process hang on "Preparing Windows" or just take a ridiculously long time >10 minutes to arrive at that same black screen. 10 minutes for a default user profile that is 29MB in size. What is making it take so long. LTSB doesn't have any of the useless Windows Store crap (that's why we chose it), so it cannot be setting that up. No Cortana, so what is it doing? The domain-join part of the task sequence failed, the computer didn't even get the name I specified in the wizard. 

Jason

Where can I find the version of MDT that is installed on a server?

Hi,

I am fairly new to using MDT 2013 Update 1 (6.3.8298.1000) with WAIK (10.0.26624). The plan is to have a task sequence that will fully patch the machine during the build without any user/admin intervention.

During a task sequence to build a Windows 7 x64 machine I have configured windows updates to be pulled from the WSUS server in a Post Application Installation task. The first pass completes successfully then the machine reboots. After it restarts it goes for Pass 2 and at this point it hangs on "searching for updates".  This prevents a couple of other tasks running therefore the full task sequence does not complete. During the LTI I do select the computer OU that the other machines on the domain are  located. Could GP be preventing it from running or is there a particular log i can check?

Can you limit the task to only do 1 pass or to kill the task after a certain amount of time?

Thanks in advance.

Which version of MDT is capable of capturing and deploying Windows 10 images?

I have three task sequences that will deploy Windows 7, 8.1 and 10 that work great.  I am attempting to combine them with some conditional statements based on the model number.

Due to driver compatibility with some machines I need to INSTALL Windows 7 and UPGRADE to Windows 10.  I am having difficulties getting a single Task Sequence to respond correctly when I copy/paste the UPGRADE task Sequence into the INSTALL task sequence.

Is it possible to combine the different Deployments Types?  If so, how is this handled, a variable in Bootstrap.ini?

Something Bad Happened (tm)

We tried a few things to fix it (tm)

It got worse.

I'm Using MDT 2013 with win 10 update, MDW(6.3.8330.1000), ADK (not sure if it was updated), WDS (6.3.9600.16384) with LiteTouch PE configuration. 

We updated MDT to support Win 10 and I was adding some windows 10 wims and task sequences when I had to image a couple computers.  The MDT stopped following it's own rules and so we blamed it on WDS and tried to restore an old WDS image. I do not think we did this correctly but I did not do the restores, and the person who did that part is on vacation. This did not, of course fix it so I went through and removed the rules and task sequences I'd been working on and re-updated the boot image. I'm reasonably certain he used "boot images > Add Boot Image but I wasn't there.

The final statement above may be relevant in that, when I moved to WDS to add the newly updated image to the Boot images folder, I received the error "Group not found"  The group is, I presume from the wizard is "Image group: Boot Images"  Of note, the same error occurred when I disabled the existing boot images, however they at least show up as disabled, although they may not be. Additionally I do know that I was able to add a boot image as recently as Monday, so whatever happened happened since Monday.  Of note, we upgraded MDT prior to Monday.

After that, things get a little crazypants. So i'll hold that thought for some time.

So, uh, any suggestions where to start in troubleshooting this particular problem?

We have upgraded our test server to MDT 2013 with service pack 2 (production server is running previous version and deploying Win8.1 Enterprise without issues). We have successfully (we believe) built the task sequence to capture a Win10 image and have created the image we wish to deploy. We have also built a task sequence to deploy the image. However, no matter what we do, and how many refreshes we try, when booting an endpoint using a USB built on the server, the task sequence is blank. My team has spent days trying everything we can think of:

• rebuilding everything!
• reinstalling MDT
• manually creating a connection between the two computers using net use before running
• adding a delay to make sure the network has time to connect
• trying to launch the process manually, over the network, from the server itself
• verifying everything is 64bit (no mixing of 32/64)
• and many more

Can anyone offer any insight into what might cause this. We're stumped.

Hey guys,

I need a little help with Wiz Editor. This probably very simple, I just can't figure it out.

I have added a pane for user to select their country, which is being used for the computer name and such. I don't want users to just hit next and use Andorra as their country by default. I added a blank line at the top and want to disable the next button until they select a country.

I been playing around with the Settings ( custom script, validation and conditions) for hours and cannot get it to work.

Any suggestions?

Thanks

Dave

I'm currently in the process of create an Image for my Server 2012 R2 Servers. I've successfully captured the image am now attempting to create bootable USB media to allow me to install this. However I don't want the partitions to be wiped etc during setup; I'd like to be prompted to configure this myself so as to prevent data loss. I've followed several guides I've found online however these don't seem to work. I've tried disabling "format and partition disk" within the task sequence and setting ShowUI to Always on disk configuration within the unattended file. Below is a screen shot of the error I receive

Any help is greatly appreciated

We are trying to use both MDT and SCCM to reimage this unit (Optiplex 7040). The imaging process completes normally. When the unit restarts, it goes into a constant Repair boot loop. I have rebooted it in safemode and then notice that on AMDKMPFD.sys, the unit will restart. Both deployments have been configured to use ONLY drivers for the 7040. Anyone had this issue?

I have created a MDT task sequence isolating the drivers for the 7040 and it still has the issue.