All of our clients are able to download and install the SCUP updates while connected to the intranet but when on the internet they are unable to download the updates from our internet DP.  All the Microsoft updates install successfully on our internet clients however it looks like they are downloading the updates from the Microsoft servers instead of the SCCM internet DP.  Because of this I'm unsure if this is a problem specific to SCUP updates or if even the MS updates would fail to download from our internet DP if the MS servers were not available.  Perhaps a config issue with the CM internet facing server but I've looked over all the settings multiple times and everything looks good.

This is the error that appears over and over in the DataTransferService.log on the internet client:

Downloading from http://[InternalSCCMServerFQDN]:80/Content/39 without proxy encountered error: BITS error: 'The requested name is valid, but no data of the requested type was found.
'  Context: 'The error occurred while the remote file was being processed.
'. Retrying 1 times DataTransferService 8/26/2015 8:08:24 PM 4532 (0x11B4)

CDTSJob::JobError: DTS Job ID='{6209CEE4-D680-4ED8-8560-F77F105DAE39}' BITS Job ID='{03DC4D74-2EB2-4666-9520-F0ED85C9EE76}' ErrorCode=0x80072AFC DataTransferService 8/26/2015 8:08:24 PM 4532 (0x11B4)

CDTSJob::JobError: DTS Job ID='{6209CEE4-D680-4ED8-8560-F77F105DAE39}' URL='http://[InternalSCCMServerFQDN]:80/Content/39' ProtType=1 DataTransferService 8/26/2015 8:08:24 PM 4532 (0x11B4)

DTS job {6209CEE4-D680-4ED8-8560-F77F105DAE39} BITS job {1C13C7A5-0B5B-4C89-8989-3527BD4EC8FD} failed to download source file http://[InternalSCCMServerFQDN]:80/Content/39/BEA7BE42D6639AE8C66511FA6E9553E184809739.cab to destination C:\Windows\ccmcache\2\BEA7BE42D6639AE8C66511FA6E9553E184809739.cab with error 0x80072AFC DataTransferService 8/26/2015 8:08:24 PM 6068 (0x17B4)

Is anyone able to deploy SCUP updates successfully to internet clients?  Any idea why it is not working for us?

Thanks!

"All the Microsoft updates install successfully on our internet clients however it looks like they are downloading the updates from the Microsoft servers instead of the SCCM internet DP. "

This is by design behavior for Internet clients because clients on the Internet in most cases have better connectivity to Microsoft than they do t your Internet DP and thus it doesn't make sense for them to not use Microsoft as the source for the these files.

This cannot be done for updates you've published via SCUP though because of course these are not hosted by Microsoft.

In the above log snippet, you have [InternalSCCMServer FQDN] in the URL, is that correct? If so, that's clearly an issue because your clients should have access to an *internal* URL. 

Jason, yes that is the case. The link points to the Internal Server FQDN which the internet clients would not have access too. Any idea why they would try and pull the update from that server when they are on the internet and set to communicate with the internet facing server?  I was wondering if all the updates would try and pull from that internal source if the Microsoft update servers were unavailable.

Internet clients should never pull from an Internal source, that would make no sense as its not something anyone would/should ever allow.

Have you verified that the Internet FQDN  entered for the site system is correct?

Have you verified that the client actual thinks that its on the Internet?

I have verified in the client properties it is set to internet and the MP is set to the internet facing server.  I can also remove and reinstall the CM client while connected to the internet so I know it's communicating fine with the internet server.

OK, what about my other question?

Sorry, yes I did verify that is set correctly for the site system on the internet server.

We currently have 5 site servers in our environment, 4 internal and 1 internet. I noticed that the Internet FQDN option is enabled and configured for site system on all the internal servers as well. Should this option be disabled for the internal servers that will not be servicing internet clients?

First, a terminology note. You only have 1 site server. The rest are site systems (sometimes called site system servers). There is a difference though and it is important as each and every "site server" implies an individual site as well.

Having an Internet FQDN on the non-Internet-facing site systems should not be an issue as long as they are set to Intranet only.