Scripts for jobs contain "@schedule_uid=N'c8576cb9-a455-4894-9ad6-b1734d004d67'" row (example) which should be just omitted - job scheduling GUIDs are usually different between servers unless you restore msdb on DR from backup of the original server.
Note: This is more complicated than I thought. This only seems to be a problem when running a script against SQL Server 2005. KATMAI and DENALI seem to have no problem with the parameter being included.
Scripts for jobs contain "@schedule_uid=N'c8576cb9-a455-4894-9ad6-b1734d004d67'" row (example) which should be just omitted - job scheduling GUIDs are usually different between servers unless you restore msdb on DR from backup of the original server.
Note: This is more complicated than I thought. This only seems to be a problem when running a script against SQL Server 2005. KATMAI and DENALI seem to have no problem with the parameter being included.