Steve Campbell wrote:
On 4/22/2014 2:13 PM, Les Mikesell wrote:
On Tue, Apr 22, 2014 at 9:07 AM, Steve Campbell campbell@cnpapers.com wrote:
I'm not sure why I need that. As I stated, I'm a little new to Samba and AD. For some reason, my research suggests that to get AD, I need
Samba
Do you want to replace AD or just interoperate with a Microsoft AD? Samba 3 will do the latter.
I'll tell you what we've got now, and how the new stuff will be used. I'm definitely not a windows type guy, and windows domains are confusing as H*** to me.
With our current netware:
We have 3 "domains". They're really not domains but we have 3 separate companies here. Based on the netware logins, you get certain volumes mapped to windows drives. The netware login scripts do the mapping. We have opted not to get a new Windows Server and whatever Netware is now.
So I guess from the Samba standpoint, the volumes are shares. This netware guy wants the ability to add new users to a "domain" that will have common mappings, and all the other stuff like specific printers attached. When the new user/machine is configured, the Windows domain is specified as well for that user.
<snip> I'm nowhere near a samba guru, but I'd think that the AD info - that's a version of LDAP - could *say* what shares a given user mounts.
Wait, as I think of it, this is percolating through: nahhh, what you do is have three workgroups, and what they user is on gets that workgroup's shares.
mark