SQL Server Central thread:
"Under SQL Server 2005, we have found that we are having a problem with our maintenance plans. Since most of our servers are on VMWare, when we installed a new server, our system admins cloned this server and created a DR server at our DR facility. However, when we tested the DR server, the maintenance plans were running on the original server. The connections for the maintenance plans were still point to the original server, and not the DR server."
"After renaming a SQL Server, one must go in an edit all of the connections for a Maintenance Plan to coincide with the new SQL Server name."
Experts Exchange thread:
"I have production server 'A' and virtual server 'B'. I took the master, msdb, model, and db1 backups from server 'A' and restored them to server 'B'. I then ran the sp_drop server 'a' and then sp_addserver 'B' on server 'B'. The maint plans were created on server 'A' to use local connection, however when they are on server 'B' SQL Agent, the maint plan jobs execute against server 'A'."
Isn't all these three scenarios related to how the connection is stored in the Maintenance Plans? It seems like it is the orginal sql server name that is stored and then when you do things like restoring system databases on another server, renaming the server or cloning the server, things doesn work as expected.
This is just my analysis. It could be that there is something that I don't understand.