You're still going to have to use Samba. Samba is basically the SMB and Windows LDAP application to handle the protocols. There isn't a domain for Linux by default, at least not for an AD server. Inside the smb.conf, you set the domain name, authentication, script paths, etc.
As for not wanting a complete guide, you can find lots of how-tos through google, but I'll tell you this from the experience people I've trained have learned the hard way. If you do not take the time to study how Samba, and it's functions, you will run into a lot of issues. Samba is very temperamental, and without knowing some of the internals, you could be beating your head against a wall for hours figuring out why it's not working correctly. While it has emulated the ability of a Windows AD server, it cannot be configured the same way. As you study the system, the policies and such will come along with it.
Needless to say if you want to keep the AD server on Windows, there are a few other components for a Linux client. One specifically would be AD4Unix, which is an AD plugin to allow Linux/UNIX based clients to work with a Windows based AD server.
If you have any specific questions to help get this running, feel free to ask away.
Samba AD Docs per Samba.org
Linux Client AD Setup