As I'm going through the list of servers and content, it's pretty obvious the only ones missing content are ones with prestaged content, so I think we have the bug that was being talked about earlier.
I'm still curious as to why validate didn't catch this, so if anyone has insight into that I'd be very happy. On Fri, Sep 13, 2013 at 9:02 AM, Ryan <[email protected]> wrote: > It's in progress now, and on one of the DPs (there were 4 that I've found > so far) it already started the transfer. This was after I hit redistribute. > > It just seems to be a problem with validate. We were hoping to use > validate to make sure content was on the DPs, but if it doesn't track all > content by design, we will probably just write a custom script for it and > have that run. > > > On Fri, Sep 13, 2013 at 8:55 AM, Dzikowski, Michael < > [email protected]> wrote: > >> What happens if you update your DP? Or resend the package? **** >> >> ** ** >> >> ** ** >> >> ** ** >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Ryan >> *Sent:* Friday, September 13, 2013 9:41 AM >> *To:* [email protected] >> *Subject:* [mssms] Validate content not working for legacy packages?**** >> >> ** ** >> >> So we were having problems with imaging, and I validated the content to >> be sure it was on all DPs. The Win7 image came back 100% successful. I >> then finally got logs from the guy in California (Have only been asking for >> a week now) and I found that it wasn't finding the package on the server. >> So, sure enough, I go to the SMSPKG share and it doesn't have the image >> package listed. **** >> >> ** ** >> >> I re-validated the content on that specific server and it still shows >> 100% successful. Is this expected behavior for legacy packages stored the >> old way and not with dedupe? I'm trying to figure out if this is a problem >> with the server validating content or expected behavior. I'm not finding >> the answer on Google.**** >> >> ** ** >> >> > >
