Anyone seeing issues with Block Copy Imaging while on 10.10.3? Fails on imaging? then this is for you READ ON :
after spending days, countless hours on the phone with JAMF support, banging my head against the wall, trying to figure out how to get around this.. FINALLY i found the issue.
The issue is because of OS X 10.9 (Mavericks) brings SMB 2 as the default network protocol and with OS X 10.10 (Yosemite), SMB 3 has been added. If you face issues connecting to your NAS or connections to Windows file servers(SMB) don't work as expected (failing to block copy) then you would do the following:
1: Fresh install of 10.10.3 or .4
2: Follow these instructions https://jamfnation.jamfsoftware.com/article.html?id=313
3: Then in terminal type in this command ( echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf)
4: If you have multiple Users use both commands ( sudo sh -c "echo '[default]' >> /etc/nsmb.conf; echo 'smb_neg=smb1_only' >> /etc/nsmb.conf")
5: Then create image using System Image Utility
6: Enjoy being able to now block copy with no issues
Some side notes: I've used @bentoms wonderful AutoCasperNBI which works like a charm but did not work in this case. @bentoms is it possible to add this script to the app in the next release? For SMB shares. Please let me know if this helps any one else on here i can't imagine I'm the only one running into this issue.
