OSD TS looking for previous package version, not finding it.

Question

Yesterday, I upgraded our SCCM environment from 2012 R2 to 2012 R2 CU3.
I am currently unable image most machines (only VM's work, for some reason) as the TS is failing with the error about it not being able to find the package xxx00002, which is our Configuration Manager Client package.  As a part of the CU3 upgrade, it
initiated a update on this package, taking it from version 10 to version 11.  All distribution points now have the version 11 package.
My pain point is that the task sequences we are attempting to reimage with are failing when looking for version 10 of the package.  Snippet below.  I'm hoping someone has some ideas on how I can resolve this or has seen it before.  I tried
changing the package in the 'Setup Windows and Configmgr' step to another package, saving, and changing it back, to no avail.
Log snippet below.
Content location request: TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
  Package : XXX00002.10 TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
  Client  : GUID:EB7523EE-E5F0-48B0-8F27-C84D21BEE0DC
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
  Local   : 1 TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
  Remote  : 4 TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
  Internet: 0 TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
Sending RequestContentLocations for XXX00002
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
Setting message signatures. TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
Setting the authenticator. TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
CLibSMSMessageWinHttpTransport::Send: URL: servernameFQDN:80  CCM_POST /ccm_system/request
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
Request was successful. TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
::DecompressBuffer(65536) TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
Decompression (zlib) succeeded: original size 244, uncompressed size 882.
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
Location Reply: <ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags=""><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="111" MasterSiteCode="111"
SiteLocality="LOCAL" IISPreferedPort="" IISSSLPreferedPort=""/><LocationRecords/></Site><Site><MPSite SiteCode="222" MasterSiteCode="222" SiteLocality="LOCAL" IISPreferedPort=""
IISSSLPreferedPort=""/><LocationRecords/></Site></Sites><RelatedContentIDs/></ContentLocationReply>
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
Processing 0 locations. TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
No static content server. TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
LocationsList.size() > 0, HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,2138)
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
FALSE, HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,1930)
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
Content location request for XXX00002:10 failed. (Code 0x80040102)
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
hr, HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,2702)
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
Failed to resolve PackageID=䛸Dž TSPxe
1/30/2015 2:30:24 PM 1796 (0x0704)
(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,3488)
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1564)
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
Failed to resolve selected task sequence dependencies. Code(0x80040102)
TSPxe 1/30/2015 2:30:24 PM
1796 (0x0704)
Thanks in advance!
Scot

Answer 1

Yes. They have version 11.
In the meantime, I have created a new Configuration Manager Client package and swapped it out with successful results, as might be obvious.
Most likely, I'll simply update the package on the distribution points to resolve it permanently (to version 12). It's just not a quick fix for us as we have
a lot of distribution points.  Sending down another copy, since the files are already there in content library, won't require nearly as much WAN traffic or time.  We'll swap the task sequences back once
we update XXX00002 to version 12.
Thanks,
Scot