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.
If you want to be notified when we post more quality guides like this one, sign up to our newsletter and you will receive an email when a new post is live.
No need to worry, we will not be filling your inbox with spam and you can unsubscribe anytime you like.