|File Size||0.51 MB|
|Create Date||January 9, 2019|
|Last Updated||January 27, 2019|
If you have MDT integrated in your Configuration Manager 2012 environment, then you will notice that when you use a console on your CM server everything works fine. However, if you have a console installed on a client machine, then you may see this error when trying to view or edit a MDT task sequence step:
'Could not load file or assembly'
This is because the client machine does not have the Microsoft.BDD.CM2012Actions.dll file on it, so this file needs to be copied to the machine into the correct location. To make this as quick and easy for you, we have created a fix that will install this file into the correct location and you should then be able to view and edit MDT integration task sequence steps on a client machine rather than on a server. We have made this fix into an MSI file so it can be easily added to the SCCM Software Catalog too.