OSD fails, can't locate a package, it's there, NAA is configured, brain hurts
Here is the story: Toronto Central Site - DP Vancouver Primary Shild Site - DP Halifax Primary Child Site - DP, PSP Running Native mode. None of the sites are configured as protected. All of the boundaries are set correctly per site. I have tried the client from all three boundaries, no change in result. Advertisement is set to allow access to remote DPs if local content not available. If the OS package is on the Halifax DP, everything works fine. If the OS package is not on the Halifax DP and is on the Toronto or Vancouver DPs, the TS fails with: Executing content location request for CS100004:1 as 8b12dd98-5095-454b-b98f-aa50f35f1fc5 TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Initializing CLibSMSMessageHeader with authenticator TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Sending RequestContentLocations TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Messaging Auth Using V4 Mode TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Formatted header: TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>8b12dd98-5095-454b-b98f-aa50f35f1fc5</SourceID><SourceHost/><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-02-18T00:24:47Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="616"/><Hooks><Hook2 Name="clientauth"><Property Name="Token"><![CDATA[CCMClientID: 94930372-3402-4500-8196-b4719e4062e8 CCMClientIDSignature: 34E25C050167F471C0782FB5B507E3423B453C8FE603473820B670C21E0467B5AD83B06C025FA98067380EDB18DC231B209451928A9FBEF4258301B11822BD823951011AC300A66FC83E7F8229E148984EB83327A3CAD0810D6A96861FC3795A1758696AB7ECD247E9D88D56318214F751C74A265560B009ACDB9729EA49A37D5877BD2EFC7B8297CF25C2A1A5B86F7DEB1BF8860414B59B1FDA0E35F34FDD5374F2C7BB08D970E038616EEDE963503C3992970821472129DABC2D6D6BC8AF558E2D1BE162639AC2DA8BDFFD78482DDCB8ACC6827A3CD92D6D310B19F57AF2190B99E40CF76044DC400C85462AA16D79B8A10B11E1FC6EB7B5840D68566C26E3 CCMClientTimestamp: 2011-02-18T03:22:17Z CCMClientTimestampSignature: 0FBA82C743577E46E07DE02403C4E95305DD2938D15F14DB0514FEEAB1613EB09C5540B6691710577995E1745231D2D76DFCC2CE0E25578E6D0DE5D2892271B62665BA0919FAE8060325227C556C6810FE91BA4640240AE4CE6CD3B327E39682C4EDABCC1DF73BE4DA827B11BB1702081B885E11CF7C4C7340CEF8447E26551DE303787A24AFB193729ED032906892B6E1990A6CCABD886722A08095D2943150E50E75BC352F0D01DD270F72C825306F079AD111417D228B28A981672413BE6DC54A6BF6605A2FF9D1A8169D1C1238BD6049ACEC8B975ABD3849367FB520C7BC4239D8588614DD89C1FDA55C61C5611417E2BE6B083E56450FF679392DC67B0C ]]></Property></Hook2></Hooks><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) CLibSMSMessageWinHttpTransport::Send: URL: SCCM-03.MATTHEWTROTTER.LOCAL:443 CCM_POST /ccm_system_AltAuth/request TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) In SSL, but with no client cert TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) The request has succeeded. 200 OK TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Decompressing reply body. TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) ::DecompressBuffer(65536) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Decompression (zlib) succeeded: original size 179, uncompressed size 418. TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Filtering Content Locations. TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Found 0 DPs in subnet, 0 DPs in local site, 0 DPs in remote location and 0 Multicast DPs TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) !lsDPList.empty(), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2136) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) FALSE, HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1635) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Content location request for CS100004:1 failed. (Code 0x80040102) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) pTSPolicyManager->GetContentLocations( m_sPackageID, m_lSourceVersion, m_dwContentSourceFlags, slistContentLocations, slistHttpContentLocations, slistMulticastContentLocations, m_dwContentPackageFlags ), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2330) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) (*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1208) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) Failed to resolve selected task sequence dependencies. Code(0x80040102) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) hrReturn, HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,408) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040102) TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) ThreadToResolveAndExecuteTaskSequence returned code 0x80040102 TSPxe 17/02/2011 7:24:47 PM 1128 (0x0468) Setting wizard error: This task sequence cannot be run because the program files for CS100004 cannot be located on a distribution point. For more information, please contact your system administrator or helpdesk operator. TSPxe 17/02/2011 7:24:47 PM 1128 (0x0468) The usual googling leaves me checking that the package has been actually distributed to the DPs (done, done and done) and that my network access account is configured (done, done and done) So, where do I go from here. I have rebuilt the package, removed it from all DPs, re-added it... No joy. I am at a loss for more troubleshooting methods. -M
February 17th, 2011 10:06pm

I would check your boundaries setup again, the below error implies that the client doesn't find any DP either remote or local Found 0 DPs in subnet, 0 DPs in local site, 0 DPs in remote location and 0 Multicast DPs TSPxe 17/02/2011 7:24:47 PM 2044 (0x07FC) My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2011 1:17am

Yeah, boundaries are fine, beautiful in fact... which is what is weird to me. I have 3 subnets, 3 boundaries, 3 AD sites (it's a lab) Mind you, I read this: http://technet.microsoft.com/en-us/library/bb680614.aspx : Having one site system function as a distribution point for multiple Configuration Manager 2007 sites is not supported. Ok, so it is not supported, but it should be possible right? Otherwise, what is the point of having the "Use remote DP" check box? If I have a datacentre site failure, I should still be able to deploy packages from remote DPs in other sites? Is there anything that says (or others evidence) to show that you CANNOT have content accessed on DP from a client in a different site? Any technet link would suffice. That would put the nail in the coffin.
February 18th, 2011 2:39am

Just tried the same thing with a software advertisement, it won't let it run it if the package is only on a DP in a different site, but the minute I add the package to a DP in the same site it works. Can I get a confirmation this is "by design"?
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2011 2:43am

Hi Matthew, I would have a read of this technet article, it will help explain how clients request content through the management point and which DPs would be used in different scenarios. http://technet.microsoft.com/en-us/library/bb632366.aspx Whether a DP is local or remote depends on the clients network boundary. If the client is on a fast network boundary then the management point defines the DPs from it's site as "local", all other DPs are classed as remote. I would have a read of the article and see how it applies to your own lab. Mark.
February 18th, 2011 4:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics