... at least not on your sms 2003 environment. sms 2003 sp3 is the only version that will support a sql 2005 sp2 infrastructure. of course, you know sms 2003 sp3 is not out yet. hold on your deployments until this new sms 2003 service pack is out.
UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress. if you are using the v2 toolkit, PLEASE read this blog post before proceeding. here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
Hey Marcus,
ReplyDeleteAlbeit in a lab, I'm running SQL 2005/SP2 with SMS SP2 and it runs fine. I recently upgraded to SMS SP3 RC1 (upgrade) and it runs fine as well. Just curious: where did you read there was a problem with SMS 2003 SP2 with SMS SQL 2005 SP2?