Windows 10: MDT Upgrade Woes

Good Afternoon! As part of a process of rebuilding my company's deployed image, I wanted to upgrade my MDT on my deployment server from Build 8450 to 8456. I did this, because as long as I'm building a new image, I might as well have the right stuff on there for Windows 11 next year. Anyway; I installed 8456 (and the binaries fix); uninstalled the Windows 10 ADK, Installed the Windows 11 ADK and the PE add-in; everything a growing boy needs. .Net 3.5 and 4 are both installed and updated, as well as Powershell 3 Upon firing up DeploymentWorkbench, I'm prompted to upgrade my development share, which I acknowledge. It went through and did that seemingly without incident; but when I go to a Task Sequence, and select any of the tabs within, MMC crashes. The error details taken from the event viewer are as follows: Application: mmc.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at Microsoft.BDD.Workbench.TaskSequenceEditor.GetActionControl(XmlNode propertyNode) at Microsoft.BDD.Workbench.TaskSequenceEditor.PopulateTree(TreeNode col, XmlNode node) at Microsoft.BDD.Workbench.TaskSequenceEditor.PopulateTree(TreeNode col, XmlNode node) at Microsoft.BDD.Workbench.TaskSequenceEditor.RefreshTree(XmlNode selectedNode) at Microsoft.BDD.Workbench.TaskSequenceEditor.RefreshData(ResultNode userNode) at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification) at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessNotification(Notification notif) at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClien t.ProcessNotification(Notification notification) at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification) at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification() at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback) Exception Info: System.Reflection.TargetInvocationException at Microsoft.ManagementConsole.Executive.MmcThreadMessageWindow.OnThreadException(Exception e) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoCompo nentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at Microsoft.ManagementConsole.Internal.SnapInMessagePumpProxy.Microsoft.ManagementConsole.Internal.ISn apInMessagePumpProxy.Run() at Microsoft.ManagementConsole.Internal.ISnapInMessagePumpProxy.Run() at Microsoft.ManagementConsole.Executive.SnapInThread.OnThreadStart() at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart() Additionally, clicking through the error gives you this: at Microsoft.BDD.Workbench.TaskSequenceEditor.GetActionControl(XmlNode propertyNode) at Microsoft.BDD.Workbench.TaskSequenceEditor.PopulateTree(TreeNode col, XmlNode node) at Microsoft.BDD.Workbench.TaskSequenceEditor.PopulateTree(TreeNode col, XmlNode node) at Microsoft.BDD.Workbench.TaskSequenceEditor.RefreshTree(XmlNode selectedNode) at Microsoft.BDD.Workbench.TaskSequenceEditor.RefreshData(ResultNode userNode) at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification) at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessNotification(Notification notif) at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClien t.ProcessNotification(Notification notification) at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification) at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification() at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback) Can anyone give me advice on how to proceed to fix this?

:)

 

MDT install application with the credentials for connecting to network shares

Hi,



Thank you for writing to Microsoft Community Forums.



I understand your query regarding Microsoft Development Kit.



However, we do have a dedicated forum for issues related to Microsoft Development Kit, let me point you in the right direction. I would suggest you to post your query in
TechNet forums, where we have support professionals with expertise on Microsoft Development
Kit to assist you with the appropriate details.



Below are few articles that might be helpful for you:

• Using the Microsoft Deployment Toolkit
  
• Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit
  
• Prepare for deployment with MDT.
  

Regards,

Nikhar Khare

Microsoft Community - Moderator

 

MDT Multicast

Hello Everyone,

I am new to MDT multicast and was hoping someone can answer my question, I set my MDT server up for multicast and it goes all the way to 99% and I watch it in the WDS console under my deployment share, I can see three clients and when they reach 99% and
I hit refresh the clients disappear which i think means it reached 100% but then on the client side its rolls back to installing operating system and starts the percent count again. Is multicast on MDT work different, does it first download the image to one
computer and once downloaded it distributes that one image to all others . I found an article below that explains how it should work but I am not sure if I am understanding it correctly.

Here is the overall process:

• ClientA starts a multicast session to download Win7SP1x86.wim from the MDT/WDS Server.
• When the broadcast session of Win7SP1x86.wim reaches 25%, ClientB joins the session in progress. ClientB knows that it missed the first ¼ of the Win7SP1x86.wim file, so it starts writing 25% into its local copy of Win7SP1x86.wim.
• When the multicast session reaches 100% of Win7SP1x86.wim, ClientA is done and drops off. However, ClientB is still missing the first ¼ of the file, and stays on the multicast chanel as it restarts (rolls back) to zero.
• Eventually the multicast session of Win7SP1x86.wim reaches the 25% mark where ClientB first joined. ClientB now has 100% of the file and drops off. No clients are connected, and the server stops broadcasting.

 

Media Creation Tool or MDT?

Hello all.

Just wondering here, I know the Media Creation Tool is mostly for home consumer based users, but I would like to know if MDT can be used to create a Win10 USB Media boot stick as explained here. Just wondering if it is worth the time to perform this using MDT instead of the MCT.

Create a bootable USB with MDT 2013 | Askme4Tech

I had tested this out myself using a Virtual Machine and seemed to work. Everything is all automated with just a few interventions at the beginning. This was less time consuming for me as I did not need any apps to be added and installing apps was manually done after Windows installation was finished. I had about 3 apps to install and that was it.

Just wondering, for advanced users, should this be a step up method for creating a Win10 USB Boot media?