Q1: What is the impact of running CIFS setup again (7-mode)?
- Cifs setup cannot be run until the CIFS service is terminated.
ontap7m> cifs setup
CIFS Setup can not be run while CIFS is active
- The "
cifs terminate" command will cause the cifs service to be stopped for the particular vfiler it is run against.
- When cifs is terminated, the symlinks, shares, and share acl’s will remain intact.
Q2: What is the impact of running CIFS create again?
- Running cifs create a second time requires that the cifs server be deleted. See question 3 below for impact of deleting a cifs server.
Q3: What is the impact of deleting and recreating a CIFS server?
- Any current smb\cifs sessions will be closed. New smb\cifs authentication will be denied until the cifs server is created again.
- Cifs symlinks/widelinks configuration will be deleted for the vserver
- Cifs shares and share acls for the vserver will be deleted. .
- Data contained in the shares will not be deleted
- Cifs server/security options may be deleted.
Note: If the machine account has been deleted, Cifs server Machine account deleted from AD can be followed to recreate the machine account without deleting the cifs server via the "
cifs modify" command.
Q4: What is the impact of modifying a CIFS server name?
- Modifying the cifs server name requires that the cifs service on the vserver to be set to administratively down (closing all cifs connections)
Q5: What is the impact of modifying the domain of a CIFS server?
- Modifying the domain of the cifs server requires that the cifs service on the vserver be set to administratively down (closing all cifs connections).
Q6: What is the impact of modifying the organizational unit (OU) of a CIFS server?
- Modifying the OU of the cifs server requires that the cifs service on the vserver be set to administratively down (closing all cifs connections).
Go to this link for more information on "Commands for managing CIFS servers"