Caution: It is difficult to change this decision after you run setup.
Hmmm. I'm not sure what drove us to make this statement in the documentation, as making this transition is actually quite simple and straightforward. I *think* that it might have been the fact that CIFS has to be stopped and restarted to move from workgroup mode into domain mode (or vice versa), thus temporarily and briefly disrupting file service to Windows clients. However, if you can arrange to make the transition at a time of low usage (the small hours of the morning for example), the disruption should have minimal impact. The whole operation should take just a few minutes. You need to execute a "cifs terminate" followed by another "cifs setup" and then you're basically done.
<gulp> Okay, I do want to change (from a workgroup to a domain).
Good move! :-)
How difficult is "difficult"?
As I mentioned, not very (aside from the brief service disruption).
How does changing the authentication method from NIS to a domain controller affect the UNIX boxes accessing the filer via NFS?
It doesn't. However, if you do start creating NTFS or MIXED mode file systems after making the transition, you may need to take a look at how UNIX security is effected by the use of these modes. There are two papers in the "Technology" section of our web site that explain these issues quite well. If you stick with UNIX mode file systems however, you have absolutely no reason to be concerned about how the new domain mode of CIFS effects NFS, because it doesn't.
Keith
On Wed, 3 Mar 1999, Keith Brown wrote:
Caution: It is difficult to change this decision after you run setup.
Hmmm. I'm not sure what drove us to make this statement in the documentation, as making this transition is actually quite simple and straightforward.
On a (similarly) related subject, did I ignorantly look past a set of documentation somewhere on 'cifs setup'? unlike most every other command, I don't recall ever seeing a list of all the options (just a "run this and it will ask you"..) Not that it really matters, but this would be nice to see covered for those of us who tend to poke around too much.
(bridge)
For the 'customer wishlist' of trivial and inconsequential features, it'd be really smooth if somewhere along the way ontap's shell would handle tab completion and prompting, ala IOS... I find myself so often hitting 'disk \t\t\t'..oh yeah..
..kg..
(..back to writing fluff implementation docs for the 760's and hoping I'm not making a bad decision...)
On Wed, 3 Mar 1999, kg wrote:
On a (similarly) related subject, did I ignorantly look past a set of documentation somewhere on 'cifs setup'? unlike most every other command, I don't recall ever seeing a list of all the options (just a "run this and it will ask you"..) Not that it really matters, but this would be nice to see covered for those of us who tend to poke around too much.
The best that I found in the CD docs was:
file:..../5_2_1-cd/ontap/5_2_1/doc/html/first/index.htm
Chapter 4 Preparing for CIFS Configuration CIFS information needed
In there is a worksheet from which all your answers to the `cifs setup` come.
For the 'customer wishlist' of trivial and inconsequential features, it'd be really smooth if somewhere along the way ontap's shell would handle tab completion and prompting, ala IOS... I find myself so often hitting 'disk \t\t\t'..oh yeah..
Yes. And, a command history. And, an editable command line. Please? Wishes, indeed, but it would make the usability of the CLI easier.
Until next time...
Todd C. Merrill The Mathworks, Inc. 508-647-7792 24 Prime Park Way, Natick, MA 01760-1500 508-647-7012 FAX tmerrill@mathworks.com http://www.mathworks.com ---
On Wed, 3 Mar 1999, Keith Brown wrote:
Caution: It is difficult to change this decision after you run setup.
Hmmm. I'm not sure what drove us to make this statement in the documentation, as making this transition is actually quite simple and straightforward. I *think* that it might have been the fact that CIFS has to be stopped and restarted to move from workgroup mode into domain mode (or vice versa), thus temporarily and briefly disrupting file service to Windows clients. However, if you can arrange to make the transition at a time of low usage (the small hours of the morning for example), the disruption should have minimal impact. The whole operation should take just a few minutes. You need to execute a "cifs terminate" followed by another "cifs setup" and then you're basically done.
Just wanted to follow up that this went entirely smoothly and quickly. Indeed, just:
cifs terminate cifs setup
answer the questions for NT domain authentication as yes, and you're all set.
If the docs could be changed to reflect the fact that this is not difficult, all that is difficult is scheduling the downtime for the cifs service.
Until next time...
Todd C. Merrill The Mathworks, Inc. 508-647-7792 24 Prime Park Way, Natick, MA 01760-1500 508-647-7012 FAX tmerrill@mathworks.com http://www.mathworks.com ---
-
Keith Brown -
kg -
Todd C. Merrill