Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

NEW Content downloading stuck at 0% via client - boundary assigned / content available via browser

  • Thread starter Thread starter Alfred
  • Start date Start date
  • Replies Replies 1
  • Views Views 1K

Alfred

Member
Messages
9
Solutions
1
Reaction score
0
Points
1
For some reason our clients are not able to download packages from the DP via Software Center, but we can browse to the packages via browser just fine.

Basically our jobs get stuck at 0%, our content has been copied to the DP (verified) and we are added successfully to a boundary group. It seems to be permissions related but we do not know.

We have checked Boundary (Group) assignments in the MECM console (added the Column Boundary Group(s) to The Devices overview). The logs also show this: <BoundaryGroup GroupID="16777218", this seems fine. Boundaries are also assigned by IP range.

What we tried:

1. AV disabled (client) - doesn't help
2. Firewall disabled (client) - doesn't help
3. DP Allows clients to connect annonymously
4. Clients can access the HTTP link directly via the webbrowser, packages are there and can be downloaded without any problems;
http://xxxxxx.com:80/SMS_DP_SMSPKG$/Content_9486f285-fedd-4db3-8585-7cf9785cdaea.1

5) Have created new packages, have redistributed existing packages - did not solve issue
6) Reinstallation of the client does not solve anything
7) Tried disabling eHTTPS with disabling "Use Configuiration Manager-generated certificates for HTTP site systems" but this did not solve the issue
8) Bitlocker policies get applied without a problem by the client.

We are using default certificates that came with the installation, no custom certs have been created or uploaded.

Something that might be related:

Client installation (ccmexec.exe) via switch "/mp:" also fails (tried server name/server name + fqdn/http://servername etc.) but works without problem when specifying /source with the files on a different shared folder or local folder.
We can browse to the client files via webpage just fine.

Any ideas?
 

Attachments

  • msedge_LJaNixRnTq.png
    msedge_LJaNixRnTq.png
    42.9 KB · Views: 5
  • msedge_AyOG4EAryh.png
    msedge_AyOG4EAryh.png
    27.5 KB · Views: 5
  • LocationServices.log
    LocationServices.log
    102.9 KB · Views: 3
  • CAS.log
    CAS.log
    95 KB · Views: 3
Back
Top