Re: [MDT-OSD] MDT 8443: Invalid DeploymentType value "" specified. The deployment will not proceed.

What does the bdd.log says? On Mon, Nov 14, 2016, 2:32 PM explanoit wrote: > Hello everyone! > I posted the following on the MDT forum, do you have any ideas for what I > could try? > > >

RE: [MDT-OSD] MDT Reference Image Build question

Thanks. That make sense. I am using Hyper-V currently, but am thinking of switching back to Virtual Box for greater flexibility. No drivers needed in either one that I've found. I was hoping that HyperV would improve in Server 2016, but as far as I can tell it is still missing USB pass

Re: [MDT-OSD] MDT Reference Image Build question

Someone may correct me if I'm wrong, but I believe the drivers are staged for setup.exe to consume during installation. Apply patches would be if you had imported packages in to MDT that needed to be applied. MDT will do it via DISM offline servicing before it boots the OS. On Mon, Nov 14, 2016

[MDT-OSD] RE: MDT Reference Image Build question

The drivers and patches are copied prior to the "Install Operating System" step, because right after that step applies the image it applies the unattend.xml file using DISM, which is what injects them. The steps themselves don't call DISM. Thanks, -Michael From:

Re: [MDT-OSD] MDT Reference Image Build question

By the way, if it's a reference image then you should be building it on VM's and in my experience you don't need any drivers if it's a Hyper-V VM anyways. Not sure about other virtualization platforms. Might need boot or network drivers potentially, but unlikely. On Mon, Nov 14, 2016 at 7:37

[MDT-OSD] MDT Reference Image Build question

This question refers to MDT 2013 U2 stand alone being used to build a Reference Image. I have maybe a stupid question, but I cant figure this out... In the Standard Task Sequence, why do the task sequence items "Inject Drivers" and "Apply Patches" occur in preinstall --- before the "Install

RE: [MDT-OSD] MDT Reference Image Build question

Vmware ESXi will work to if you use the E1000 nic From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Brian Klish Sent: den 15 november 2016 01:43 To: mdtosd@lists.myitforum.com Subject: Re: [MDT-OSD] MDT Reference Image Build question By the way, if it's a

[MDT-OSD] RE: Best methods to replicate MDT content

DFS sounds like it would probably be the best solution for something that scale.. We have a primary MDT distribution point and 5 remote Linked Deployment Shares, and I recently started using powershell with scheduled tasks to automate things. The downside is there's no log to see if something

[MDT-OSD] MDT 8443: Invalid DeploymentType value "" specified. The deployment will not proceed.

Hello everyone! I posted the following on the MDT forum, do you have any ideas for what I could try? https://social.technet.microsoft.com/Forums/en-US/8c74127b-0857-4f3a-b23b-35fa4cfcaa73/mdt-8443-invalid-deploymenttype-value-specified-the-deployment-will-not-proceed?forum=mdt *MDT 8443: Invalid

RE: [MDT-OSD] MDT 8443: Invalid DeploymentType value "" specified. The deployment will not proceed.

Are you sure you updated your boot images? You could see an error like this if you were using updated MDT wizard pages with an older ZTIUtility.vbs script. I would suggest completely regenerating your boot image and importing that into WDS. If you still see the error, send me the BDD.LOG

[MDT-OSD] Best methods to replicate MDT content

Hi All, I need to automate replication across 3 different regional MDT servers located in three different regions of the world and then down to 47+/- local MDT servers at various sites scattered among the three regions. The flow of data needs to be one way, all downstream. Nothing can go