The Samba-Bugzilla – Bug 4926
Argument createcomputer does not work in net rpc join
Last modified: 2010-03-08 10:14:40 UTC
Currently the 'net rpc join' does not support creating the machine account in a specific OU since this is an AD specific operation.
In an AD environment it becomes essential to support this since the default folder 'Computers' is usually locked down and very few folks can create objects in this folder.
Created attachment 2899 [details]
Patch to support createcomputer using net rpc join in an AD environment
I'm pretty solidly opposed to this patch as I do not believe it belongs
in 'net rpc join' at all. Why do you require "net rpc join" in an AD
I suggest you poll the samba-technical mailing list and see if anyone
else might support it.
After the explanation you had provided on the samba list, i was almost convinced that i was probably the only one who ran into this issue and decided not to file the bug.
However i received an email from a Samba user (James. R Grinter) who was interested in the patch. I filed an enhancement bug so that people can find the patch and use it if it is applicable in their environment.
My request would be wait for a few days and see other people's interest in this patch and if we don't have many takers for this, please feel free to mark this bug as INVALID or WONTFIX.
Sure. I'll leave it open. That's also why I suggested bring it up
for discussion on the samba-technical list to get input from the
other devs as well.
Being new to this, why would you need to net rpc join an AD while setting AD options? Isn't that just what net ads join is for? If your Samba can't do ADS, you'll run into trouble later anyway, I'd guess.
We have certain deployments which is running older versions of AD and hence needs to support 'rpc mode'.
Sorry, i just don't see a need to use OU's with rpc. Older AD setups should still work with net ads.