No T-Shirt & AFAIK it's not a bug.

I often see the distribution point.

IIRC only http hides the distribution points.

AFAIK I know this is expected behavior, although the restricted symbol has never shown up for me.

I actually see the same behavior in 8.21 right now, but I want to say its been even before this version. Never really bothered me though so I never said anything.

I have to admit we haven't done a lot of pushing, and when we do it's usually via HTTP. But now that we are moving our Distribution Points to NAS, we will be losing HTTP capability. So only now we're noticing this. I'm hoping there is a way to mount the CasperShare without it being visible in Finder.

Don

Yea somewhere in the back of my mind I remembered you used HTTP hence my comment.

I'm guessing there's a way of editing fstab to hide the share.

Me too I would really like to know how to hide the Caspershare volume when using AFP.
Cheers
Carlo

We've always seen it. Users have gotten used to it. We're going to be moving to https delivery on new infrastructure so it'll go away at some point.

Anytime you mount a "Share Point" in OS X you will see something like shown above. It's just that you aren't' seeing the share point mounted as a typical share point, and simply being mounted as a folder.

Please note my feature request here:
https://jamfnation.jamfsoftware.com/featureRequest.html?id=210

I've requested this via e-mail before, but let's give it another go!

We're actually migrating away from AFP (and HTTP) as we move the Distribution Points to NAS. We'll need to test to see if the same thing happens with SMB mounts, and whether we can hide the mounts.

So no SCP or FTP or SFTP capability in JSS? :)

Don

Hi Jared,

I'll understand if you can't give details due to security/confidentiality, but I'm curious what kind of infrastructure you're standing up that you're going to be using HTTP. I have to admit I'm a little concerned about HTTP, but mostly due to AAMEE (c'mon Jody, give us flat packages! <g>).

Thanks,
Don

We've always seen it. Users have gotten used to it. We're going to be moving to https delivery on new infrastructure so it'll go away at some point.