Since I migrated Jamf to a Windows 2019 server two weeks ago, I have been troubleshooting the primary distribution point. The distribution point and jamf server are running on the same VM. I have tried and failed with https, probably because of the same root cause... so I am trying to simplify the issue by first troubleshooting the SMB dist point problem.
I am able to mount the share both from Windows and Mac clients using the jamf service accounts. I have been able to validate that the accounts work as-should... one read-only, the other read-write. I don't know what the jamf binary and jamf admin do differently to mount the distribution point, but both fail without any helpful messages.
I'm wondering if any of you have had a similar experience, and whether you have been able to locate your root cause and resolve. I have a packet capture out to Jamf support right now. I have been working with them for two weeks without resolution. I just re-built my Jamf server a second time with the same results.
Solved! Go to Solution.
A few years back, had the same issue when we migrated/updated our on-premise server. If I recall, it ended up being the settings on Jamf Pro (Settings, Server, File share distribution points). SMB.
It had something to do with the username needing a "\" in front of the username.
Or maybe both a "." and "\".
Example: username: .\caspershare
Once we played with that, it worked. I can't recall all the details, but if I come across the articles, I'll post.