Steve. This article was of great interest to me as I recently had problems with being able to edit/delete jobs after renaming a server. It seems that in SQL 7 the sp_add_job procedure's default for the @originating_server parameter is '(local)' so it didn't matter if the server was renamed. In SQL 2000 this parameter is set to SERVERPROPERTY('ServerName') if the parameter is supplied as NULL or even '(local)'. When the server is renamed the originating server name is different and so SQL Server considers the job to have been created by a master server.