all you need to know is that
2000 uses 'Ole Automation Procedures'
2005 uses vbscript
2008 uses powershell
had to do it this way due to complexity but someone else might be able to fix it better.
if you do not have powershell installed on 2008 sql server you can use the vbscript version also for 2008 just change the code to jump to that part.
execution is easy, note there is no file extension on the @ps1filename
@ps1filename = 'c:\downloads\createjobs',
@filename = 'c:\downloads\createjobsscript.sql',
@catfilename = 'c:\downloads\tempcategoryscript.sql', @tempfilename = 'c:\downloads\tempjobsscript.sql'
Works for all three environments and its ugly code but it works. maybe if I get time I will work on it and clean it up.
V1 and V2 of powershell require a slightly different syntax and as a result i have to test for powershell version at end of powershell script for 2008