1. You may want to make sure your packages are not set to update on a schedule, temporarily, until you are able to place known good source files into the source directory. When you copy new files into the source directory, nothing happens until a package is either updated in SCCM manually or through the set schedule if there is one set on the package. Also, if the package is set to always obtain files from the source directory, then even a package refresh action will also go looking back to the source directory.
2. Unfortunately I can't answer question 2, but If you have a long term DPM backup to tape you may want to see if you can get the last known good backup, especially if you're able to zoom in on roughly when the issue started. From: [email protected] [mailto:[email protected]] On Behalf Of Robertson, Casey Sent: Friday, May 16, 2014 9:52 AM To: [email protected] Subject: [mssms] Corrupted SCCM package source Good morning, Due to issues with our SAN/server team that I won't get into - my SCCM package source directory structure it corrupt. Files are all there but if you try to copy any of the files out or run any .exe's or .msi's they are all bad. So... fortunately current packages run OK since they run from the DP. The obvious concern is updating existing packages or versioning them since it will try to rebuild from source. I think I'm stuck with finding new copies of the sources and replacing them. So.questions: 1. As long as the path stays the same and the files are good, the packages themselves shouldn't care if I copy new files..so I should be good there? 2. Any tips/tricks with drivers?? They are enough of a pain anyway now I'm not looking forward to dealing with the versioning of those again. 3. Has this happened to anybody else before? If so what did you do? Other than cry or just go out for coffee and then cry. Thanks, Casey
