samba - Jul 2014 - SAMBA 4 acting as Domain Server- Is Exchange 2010 capable of being installed?

Hello.

I just ran into this issue myself (with Exchange 2013) and found out how 
to solve it, so I'm trying to reply to this thread to help anyone else 
who is looking.

Use an LDAP editor (I use Apache Directory Studio) to edit the entry for 
the computer account of your (master) Samba domain controller. It has a 
DN of the form:
CN=<computer name>,OU=Domain Controllers,DC=foo,DC=example,DC=org
(Make sure to authenticate as an account that has rights to edit this. 
Usually a Domain Admin is suitable.)

The attribute you want to edit is operatingSystemVersion. Change this to 
whatever version of Windows server is equivalent to the domain 
functional level you're currently running. (A list like this may be 
helpful: http://www.gaijin.at/en/lstwinver.php)

For example, I'm running Samba 4.1.9 at a 2003 functional level and 
Exchange 2013 SP1 requires that the DC be running 2003 with at least 
SP2, so I did the following:

- changed operatingSystemVersion to "5.2 (3790)"
- added operatingSystemServicePack with the value "Service Pack 2"

This passes Exchange's check. (The value of "server string" in the
smb.conf is irrelevant.)

I got these values by looking at the entry for another computer account 
that is really running Windows 2003 R2 SP2. You can verify your changes 
by going to Active Directory Users and Computers and looking at the 
Operating System tab of the Properties of your Samba DC's computer account.

(I don't yet know if there will be future problems doing this (like if 
Exchange makes assumptions that aren't true for Samba's AD) since I 
haven't yet actually installed Exchange. But that's for another thread.)

Hope this helps someone!

Sincerely,
Sean M. Pappalardo
Sr. Networks Engineer
Renegade Technologies
http://www.renegadetech.com