So – MDT 2012 is out and, as I explored in a previous post, it integrates nicely with SCCM 2012 RC.
If you jump into the administration console and try to make an MDT-based boot image, you will probably encounter this error:
“Could not find a part of the path ‘C:ToolsPEToolsx86WinPE_FPs'” or “Could not find a part of the path ‘C:ToolsPEToolsx64WinPE_FPs'”
Could not find a part of the path 'C:ToolsPEToolsx86WinPE_FPs'
Looks like there’s an MDT 2012 bug in the form of a hard-coded link to reference the presence of the Windows Automated Installation Kit (WAIK) – all the necessary files are to be found in “C:Program FilesWindows AIKToolsPEToolsx86WinPE_FPs” (or x64, depending on the architecture of the boot image you’re creating).
Simply copying the ..Tools.. folder and all the subfolders to C: will get around this error. It’s clunky, but given that the problematic bit of code probably lies within one of the MDT DLLs (my money is on Microsoft.BDD.Wizards.dll) then there’s not much we can do right now, unless you’re really, really keen on uncompiling/recompiling DLLs.
UPDATE 30/11/2011 – After some discussion with the most awesome Michael Niehaus, there’s definitely not a hard link to C:. The ConfigMgr Console needs to be run as Administrator, and then it all works fine. Not sure whether this is functionality which will make it all the way through to the RTM, so we’ll see.
UPDATE 09/12/2011 – Yet more awesomeness from Michael Niehaus. This is a reproducible issue in the current beta and will be resolved in the Release Candidate of MDT 2012.
Running the SCCM 2012 Administration Console as an administrator will solve the problem.
So it does – I guess that’s the bug, then. Thanks for the heads-up!
I’m running the console as admin and have hit this exact error.
Hi, I’ve tried running the console as admin and it doesn’t work for me either. i get the exact error above.
make sure to also run the Configure ConfigMgr Integration after installing MDT 2013, run that as Administrator and all should be fine.
Niall you are an amazingly smart man, this was exactly the issue I was having and this fixed it right up. Thank you.
I’ve RUN evertything as administrator, and I still have the problem. I’ve got MDT 2013 Update 2 installed, I’ve run the Configure ConfigMgr Integration as administrator, I’ve run the console as administrator, aI’m installed and run it on the server itself, and on my latop which has the Config Manager Console and MDT installed….Nothing works! Anyone have any ideas?
I have the exact same issue. I’ve done all the exact same steps. Still a problem.