Uh... Just out of curiosity... Can you expound on "Unfortunately we use DPM?" If you want to reply to me off list, I'd be ok with that too. :)
On Fri, May 16, 2014 at 10:08 AM, Robertson, Casey < [email protected]> wrote: > Unfortunately we use DPM (problem #1) and #2, it may have been “backing > up” bad data for a while. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Daniel Ratliff > *Sent:* Friday, May 16, 2014 9:56 AM > *To:* '[email protected]'; '[email protected]' > *Subject:* RE: [mssms] Corrupted SCCM package source > > > > Got backups? We backup out entire content share daily. Haven't had to use > it yet though. > > -Daniel Ratliff > > -----Original Message----- > *From: *Robertson, Casey [[email protected]] > *Sent: *Friday, May 16, 2014 12:54 PM Eastern Standard Time > *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 > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > > > >
