I agree with TheSQLGuru. Even if the maintenance task has improved, it will be a long time before I trust them again. They were once a pain to use and migrate. (It required a custom xml transformation the last time I tried to migrate a plan years ago.) I ended up using my own T-SQL maintenance job until I found Ola's work (http://ola.hallengren.com/). I've been using Ola's script for several years without any issues. There was another recent article using PowerShell to do maintenance. It can be good to consider (or reconsider) ways to improve on a process. However, sometimes, it's hard to improve on something that already works.