Toasters,
I have a client who needs to use SnapDrive for Windows. I'd like to use storacl to limit SnapDrive visibility to that client's volumes and fibre channel luns. I'd also like to avoid joining the filer to the AD domain.
I created a local ontap account that is a member of the local administrators ontap group. I can configure SnapDrive's transport protocol settings to connect to the filer using the ontap account via https. SnapDrive see's all of the volumes on that filer as expected.
Is it possible to create storacl rules that apply to SnapDrive for Windows when connecting via https using a local ONTAP user to a filer that is not a member of domain? Everything I see in the storacl documentation seems to only apply to filers that are a member of a domain.
Much appreciated, Phil