alex meunier (10/24/2016)
Update:using SSMS 2008R2 remotely, I'm able to create the maintenance plan.
So it would seem that the issues would be with SSMS 2016, there would
be a prequisite that is needed but still went on with a successfull install.
I don't see the install logs for SSMS 2016, is there one?
Have you tried it with a different Windows user account?
I ask because, in the past when I've seen "Cannot create a task from XML for task" errors, they've sometimes been related to the Windows profile. Whenever you do something like create a maintenance plan, SSMS writes temporary files containing the commands that it wants to run. Sometimes those temp folders go missing, or get moved, or have their permissions messed.
If you have another account that you can use one that machine, try logging in as that and creating a maintenance plan.
If that does turn out to be the issue, you can generally resolve it by blowing away the user profile on the machine and when you log that account in again and start SSMS it should set everything up again. If that isn't an option for your user account, you can try going into the %TEMP% location for that user profile and manually deleting the temp files associated with SSMS.