Hello,
I am new to the Ontap 9 solution. I cannot create a CIFS home directory.Can you help me ?
thanks for any help
Hi.
We can definitely try. Please share details about the failures or uncertainties you experience. I'm adding some relevant documents below that can help you to do it step-by-step.
https://docs.netapp.com/ontap-9/topic/com.netapp.doc.exp-cifs-cfg/GUID-DAE79B03-9C4A-4308-A9FA-2F30D77538C1.html?cp=13_7_1
https://docs.netapp.com/ontap-9/topic/com.netapp.doc.pow-cifs-cg/GUID-F9767F59-BAC2-454E-AB23-C93C9B460AB1.html?cp=13_6_1
There is also a way to create dedicated-per-user dynamic shares for home directory.:
https://docs.netapp.com/ontap-9/topic/com.netapp.doc.cdot-famg-cifs/GUID-D16B85B1-FE36-4F01-9C04-9E1E58E6834E.html?cp=13_9_6_0
Although - I prefer a simple ABE as it's more industry standard and will not lock you down to a specific vendor (Well - NetApp in that case):
https://docs.netapp.com/ontap-9/topic/com.netapp.doc.cdot-famg-cifs/GUID-F28FF706-D2ED-4D86-93B8-2017C9E43937.html?cp=13_9_6_5
Hello, thank you very much for the reply.When I use the server command "cifs share create -vserver toto -share-name% w -path% d /% w -share-properties oplocks, browsable, changenotify, homedirectory" to createa dynamic personal directory. the home directory is created at the root of the SVM.- Unable to access the security tab and unable to open the directory from Windows, any idea?- Is it possible to create the home directory in share. how should we proceed?
thanks a lot for your help
The root volume likely to be unix-based (can see with the command "qtree show".
For using the feature with the commnad you provided, you need to add the created volume to the search path:
vserver cifs home-directory search-path add -vserver vserver -path path
see here:
https://docs.netapp.com/ontap-9/topic/com.netapp.doc.cdot-famg-cifs/GUID-5991E6B3-FE3A-4606-AA09-1611DC3E3711.html?resultof=%22%73%68%61%72%65%22%20
Again. I'm agins't using this feature. As I don't think it gives any advantage, and can lock you down to a specific product and vendor.
I believe that access based enumeration share is more straightforward and similarly secure (if not even more - as it's very visible if security is set wrong) : https://docs.netapp.com/ontap-9/topic/com.netapp.doc.cdot-famg-cifs/GUID-F28FF706-D2ED-4D86-93B8-2017C9E43937.html?cp=13_9_6_5