title | description | ms.service | ms.workload | ms.topic | author | ms.author | ms.date |
---|---|---|---|---|---|---|---|
SMB FAQs for Azure NetApp Files | Microsoft Docs |
Answers frequently asked questions (FAQs) about the SMB protocol of Azure NetApp Files. |
azure-netapp-files |
storage |
conceptual |
b-hchen |
anfdocs |
04/21/2022 |
This article answers frequently asked questions (FAQs) about the SMB protocol of Azure NetApp Files.
Azure NetApp Files supports SMB 2.1 and SMB 3.1 (which includes support for SMB 3.0).
Yes, you must create an Active Directory connection before deploying an SMB volume. The specified Domain Controllers must be accessible by the delegated subnet of Azure NetApp Files for a successful connection. See Create an SMB volume for details.
You can configure only one Active Directory (AD) connection per subscription and per region. See Requirements for Active Directory connections for additional information.
However, you can map multiple NetApp accounts that are under the same subscription and same region to a common AD server created in one of the NetApp accounts. See Map multiple NetApp accounts in the same subscription and region to an AD connection.
Both Azure Active Directory (AD) Domain Services and Active Directory Domain Services (AD DS) are supported. You can use existing Active Directory domain controllers with Azure NetApp Files. Domain controllers can reside in Azure as virtual machines, or on premises via ExpressRoute or S2S VPN. Azure NetApp Files doesn't support AD join for Azure Active Directory at this time.
If you are using Azure NetApp Files with Azure Active Directory Domain Services, the organizational unit path is OU=AADDC Computers
when you configure Active Directory for your NetApp account.
Azure NetApp Files supports Windows Server 2008r2SP1-2019 versions of Active Directory Domain Services.
As a best practice, set the maximum tolerance for computer clock synchronization to five minutes. For more information, see Maximum tolerance for computer clock synchronization.
Azure NetApp Files supports modifying SMB Shares
by using MMC. However, modifying share properties has significant risk. If the users or groups assigned to the share properties are removed from the Active Directory, or if the permissions for the share become unusable, then the entire share will become inaccessible.
Azure NetApp Files doesn't support using MMC to manage Sessions
and Open Files
.
Use the JSON View link on the volume overview pane, and look for the startIp identifier under properties -> mountTargets.
No. However, Azure NetApp Files SMB shares can serve as a DFS Namespace (DFS-N) folder target.
To use an Azure NetApp Files SMB share as a DFS-N folder target, provide the Universal Naming Convention (UNC) mount path of the Azure NetApp Files SMB share by using the DFS Add Folder Target procedure.
Azure NetApp Files supports modifying SMB Shares
by using Microsoft Management Console (MMC). However, modifying share properties has significant risk. If the users or groups assigned to the share properties are removed from the Active Directory, or if the permissions for the share become unusable, then the entire share will become inaccessible.
You can change the NTFS permissions of the root volume by using NTFS file and folder permissions procedure.
No. However, you can create a new SMB volume with the new share name from a snapshot of the SMB volume with the old share name.
Alternatively, you can use Windows Server DFS Namespace where a DFS Namespace with the new share name can point to the Azure NetApp Files SMB volume with the old share name.
Yes.
Azure NetApp Files supports CHANGE_NOTIFY
response. This response is for the client’s request that comes in the form of a CHANGE_NOTIFY
request.
Azure NetApp Files also supports LOCK
response. This response is for the client’s request that comes in the form of a LOCK
request.
The Azure NetApp Files service has a policy that automatically updates the password on the Active Directory machine account that is created for SMB volumes. This policy has the following properties:
- Schedule interval: 4 weeks
- Schedule randomization period: 120 minutes
- Schedule: Sunday
@0100
To see when the password was last updated on the Azure NetApp Files SMB machine account, check the pwdLastSet
property on the computer account using the Attribute Editor in the Active Directory Users and Computers utility:
Note
Due to an interoperability issue with the April 2022 Monthly Windows Update, the policy that automatically updates the Active Directory machine account password for SMB volumes has been suspended until a fix is deployed.