Beware while creating Maintenance plans using SP2.

I created maintenance plans from my laptop which has got SP2 to the servers that doesnt have SP2 installed. I observed that the old backup files didnt get deleted, I was wondering if that is a bug too so I started to create the maintenance plans from the server itself. so guys beware of this fact. I dont even know if that is a bug or not. Need to verify the same in other servers.

The another glitch is when you create a maintenance plan using a machine with SP2 we cant edit it from a non sp2 client or server, this is the way SP2 has been designed to work so guys beware of this fact too.

Any thoughts or insights in this? Did some one else found out similar issues?

Critical Hot Fix on SP2

The earlier release on SP2 had a maintenance plan bug (if you have downloaded the SP2 before March 5th), which did an early delete of the backup files, then MS released a hot fix then later on seems like they have found out another bug, which prevents from the maintenance plans to execute the checkdb. They have released another hot fix (It is supposed to be of a critical hot fix type.). The details of this can be read from .
this
I am thinking that MS is a bit hassle in all the releases of this SQL 2005 and that too with the SP2 release its not even couple of months they have released back to back hot fixes on this SP2. Now Im a bit scared to apply SP2 in my servers, since SP2 has no come back once we apply it.