Ran into the same issue. In order for my client to run any workflow in Casper Imaging I had to mount the DP first by connecting to server. After doing that I was able to image just fine. Later found out that my "Workgroup or Domain" (under File Sharing tab in the Distribution Point settings) section was wrong. When I corrected it Casper Imaging worked without manually mounting the DP first.

I don't know if this is the same issue your having but it sounds pretty similar to mine.

Had same issue. Reverted back to a previous Netboot with Casper Imaging 9.6.3 and it worked. Either something wrong with my new netboot image or 9.6.5 not communicating with my JSS properly.

This is the first Netboot image I've created in the 9.6 series -- our old netboot image is 8.73. Mounting the drive manually before imaging is not an option for us.

Our workgroup/domain seems fine. I can mount via the command line in in finder via cmd-k. We can't use AFP, only SMB. It's very odd. I've been stuck on this for hours. I have no idea what is happening. The jamf log shows no useful information whatsoever:

"There was an error mounting the file server . Giving up"

Hey great.

This seems to be the same for our system too, more bugs...?

mike, is your netboot image 10.10.2?

We fixed our issue with 9.6.5 by deleting and re-adding the Casper Read/Write and Read only users on our OS X server and then deleting and re-adding the Distribution Point in the JSS. We could manually mount our SMB CasperShare but Casper Admin and Imaging would not so it seemed to be an authentication issue with the apps and the JSS. Flushing the users server side and redoing the Distribution point in JSS fixed it for us.

That doesn't seem to be working for me. At least, deleting and re-adding the distribution point. Our casper share is actually on a Windows file server using SMB, so the accounts for read and read/write are domain resource accounts. I haven't deleted and recreated them but am not sure why that might fix something.

Still stumped.

We are having a similar issue with 9.6.5. Casper Admin cannot mount the Distribution Point using 9.6.5, but if we downgrade to 9.6.3, it opens and mounts without a problem. OTP with support now, but they are stumped.

Edit - We did delete the distribution point in JSS and resetting the permissions on the folder. Clearly this is an issue with 9.6.5

Same here, had to recreate the accounts for the JDS then worked fine with 9.65

One note we had to enable WebDav first then connect, then enable SMB.

It sounds like some of you are indicating this is a 9.65 issue, so the following may not apply to you, but I have seen something similar recently so I thought I'd pass it on:

Configuration: SMB shares, AD domain accounts for read and write service accounts.

Issue: Casper Admin/Remote/Imaging could not mount the SMB shares when the Mac was not joined to the domain (as in the netboot situation mentioned above). I could mount the shares using 'Connect to Server' in the Finder regardless of the domain binding---the windows logs showed that the OS mounted the share using Kerberos while jamf tried to use NTLM...so there is some difference in how the share is being mounted.

Solution: Modify the userWorkstations value on the service accounts. This prevented the accounts from mounting SMB shares on servers that aren't explicitly listed in that attribute. You can add your server names, or remove the attribute so the account can login anywhere. You can view the Attribute using ADSI Edit to confirm this is your issue. More info on this attribute: https://msdn.microsoft.com/en-us/library/ms680868(v=vs.85).aspx

@dmw3 Can you go into detail on how you created new accounts for the JDS? I can't seem to find where to do that?

I'm wondering if this behavior for users who have upgraded to 9.65 is a known issue/defect, or is a side effect of a database schema change, and deleting/re-adding JDSes and Distribution Points works around it.

@amanda.wulff? Anyone else from JAMF care to chime in? I've put the brakes on any thoughts of upgrading client JSSes to 9.65 until more details are known on this.

@RobertHammen

I’ve seen a small handful of cases in which Casper Admin had trouble mounting the Master distribution point (AFP, SMB, or JDS) after updating to 9.65, however, in each case the underlying cause was always different so it doesn’t seem to be a case of one specific thing that’s causing it to happen.

If it’s something anyone here is running into in your test environment or in your production environment, please get in touch with your Technical Account Manager so they can look at it in a bit more detail.

Thanks!
Amanda Wulff
JAMF Software Support

Update - our issue was resolved. Our rep determined there is an issue with special characters in password. We created new accounts for our Distribution Point and were finally able to mount the share and open Casper Admin.

I've only tested Imaging 9.65 with a 9.63 JSS, but worked fine mounting an AFP volume.

Only special character present was "@" though

We are having all sorts of issues.
Casper remote crashes.
Can't install anything from Self Service.
What a bloody mess...

Looks like it's issues with mounting SMB shares here as well. No word from anyone yet at JAMF, but we've found the DP's are not mounting and it looks as if the CasperShare are mounting in some cases then phantom instances remaining which keep Self Service from running. Even running policies in verbose mode show the issue. Mounting any of the DP's in the Finder works fine though...

It's the same result as if you have a policy set to run at login.
When the policy is running and you launch Self Service, you get errors on installs as the CasperShare is already mounted. So it seems like 9.65 is not properly unmounting and releasing the CasperShare volumes. In for a world of hurt come Monday...

SMB share issues here too. When running a policy from the Self Service, Self Service is unable to mount our "CasperShare". ( Right after updating to JSS 9.65 )

@erikstam, et al...
Try changing the DP to IP address instead of DNS.
So far:

IP address on DP:
Install apps via Self Service – OK
Quit Self Service, install more apps – OK
Reboot client Mac (no change to server):
Install apps via Self Service – OK
Quit Self Service, install more apps – OK
Change DP back to DNS:
Install apps via Self Service – fails
Quit Self Service, install more apps – fails
Change back to IP:
Install apps via Self Service – OK
Quit Self Service, install more apps – OK

Give it a shot. So far, so good...testing Imaging now.

Scott

Defect logged with JAMF: D-008630

*EDITED after @amanda.wulff comments below:

I should have stated it was added to this defect, so I apologize. I've been running nuts trying to fix this for our client...

I assume it's related but my Casper Admin also will not mount the share. I haven't tried changing it to IP based yet.

Hey all,

Just to elaborate a bit on @boettchs ‘ comments a little:

D-008630 does require a slightly specific set of circumstances to be the root cause of Admin being unable to mount a share.

With D-008630 the behavior we see is that Casper Admin 9.65 will not mount an SMB share that has a / in the server host name.

If this situation describes how your SMB distribution point is named, one workaround we have at the moment is to replace the server’s name with the IP address instead and it should work, which is what @boettchs mentioned further up the thread.

If you have additional questions, are seeing something different, or are not using an SMB share point, please open up a case with your Technical Account Manager if you have not already done so, so we can troubleshoot the issue further and determine what the underlying cause is.

Additionally, if you have an ongoing case about this issue and find that your situation does fall under the situation described in D-008630, please let your Technical Account Manager know so we can be sure to get your existing case attached to the defect for tracking.

Thanks!
Amanda Wulff
JAMF Software Support

Also note, besides the / in the server host name being an issue, never use $ : or / in a password for an account to mount the share (i.e. casperadmin/casperinstall).

Adding my name to the list - since upgrading to 9.65, Casper Admin believes it cannot mount CasperShare for replication... but as others mentioned, the mount point sets up behind the scenes (seen with "mount") and remains there until "umount"ed.

No special characters in passwords, changed to IP instead of hostname, no help.

I flipped back to Casper Admin 9.63 and no problems :(

Other suggested solution was to document the DP settings, then delete it and re-add it, but yeah, *something* is broken with 9.65, apparently.