I've never changed it from a workgroup to a domain situation, but you should be able to modify the CIFS server settings at any time. One thing you'd have to consider is if you have local user accounts for that server, will you need to remap them or will you be replacing them with domain permissions. Also, enabling the domain membership allows for some easier Windows-embedded management so you should gain some functionality there. The permissions/usermapping would be my primary concern to allow seamless visibility to the users.
If you have a spare GbE port on the DM you could always try creating a test CIFS server and emulate the process prior to applying it to the production server as well, if you don't have a test-dev unit.
My apologies for answering for the wrong device! On the VNXe the domain membership is handled globally in the system settings. I am unsure how the share permissions would react to the change on the VNXe if you have local users created, but I can't imagine that any problems that came up couldn't be alleviated by simply redoing the CIFS/Windows permissions on the shares. Sorry it's not a great answer, but if you don't have granular permissions in your trees then it may be a simple update.
VNxe
16 Posts
1851
1
Posted November 8th, 2013 07:00
Hello Hsn,
You can disable standalone option and then you would have an option to join the same CIFS server to a AD domain.
Log in to Unisphere
Go to Settings -> Shared folder server settings -> Highlight the CIFS server and click on details
Go to Sharing protocols and click on disable option.
Note :- This would disable standalone CIFS server option and by doing this users will get disconnected to the CIFS shares.
Once you disable, then you would have an option to re-join the CIFS server to AD domain.