samba - Apr 2015 - Joining 2008 R2 to Samba4 AD DC

We have a Samba4 AD DC running on an Ubuntu 14.04 VM

[ smb.conf ]

# Global parameters
[global]
         workgroup = MEADORANDCO
         realm = meadorandco.com
         netbios name = SOGO
         server role = active directory domain controller
         dns forwarder = 192.168.121.1
         idmap_ldb:use rfc2307 = yes
         passdb backend = samba
         allow dns updates = nonsecure

         ### Configuration required by OpenChange server ###
         #dcerpc endpoint servers = epmapper, mapiproxy, dnsserver
         #dcerpc endpoint servers = +mapiproxy
         #dcerpc_mapiproxy:server = true
         #dcerpc_mapiproxy:interfaces = exchange_emsmdb, exchange_nsp, 
exchange_ds_rfr
         ### Configuration required by OpenChange server ###

         #mapistore:namedproperties = mysql
         #namedproperties:mysql_user = openchange-user
         #namedproperties:mysql_pass = Passw0rd
         #namedproperties:mysql_host = localhost
         #namedproperties:mysql_db = openchange
         #mapistore:indexing_backend = 
mysql://openchange-user:Passw0rd at localhost/openchange
         #mapiproxy:openchangedb = 
mysql://openchange-user:Passw0rd at localhost/openchange

[netlogon]
         path = /var/lib/samba/sysvol/meadorandco.com/scripts
         read only = No

[sysvol]
         path = /var/lib/samba/sysvol
         read only = No

As you can see, I've commented out the "dcerpc" calls.

All the tests under "Testing DNS" work correctly

https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO#Testing_DNS

All Windows clients refer only to the Samba AD DC for DNS, and the Samba 
AD DC forwards DNS to our gateway device.  That was discussed during an 
earlier e-mail to the mailing list.

https://lists.samba.org/archive/samba/2015-February/189159.html
https://lists.samba.org/archive/samba/2015-February/189506.html

We have one Windows 2008 Server used for storage and one Windows 2008 R2 
Server used for MSSQL which "join" correctly (no problems), but we
have
one Windows 2008 R2 Server which does not "join"

It's used for Remote Desktop Services.

Specific error: "Network path not found"

(1) Any suggestions on what to investigate to get this last Server 
joined correctly?

https://wiki.samba.org/index.php/Joining_a_Windows_Client_to_a_Domain

(2) Should it be joined as a DC?  Would it help to do so?

https://wiki.samba.org/index.php/Joining_a_Windows_Server_2008_/_2008_R2_DC_to_a_Samba_AD

My Windows 7 clients "join" correctly with no problems but two Windows
XP clients fail to "join"

Specific error: "Internal error"

Looking at the Windows Server Event Viewer, I find this error:

The Remote Desktop license server could not be registered as a service 
connection point in Active Directory Domain Services (AD DS). Ensure 
that there is network connectivity between the license server and AD DS. 
To register the license server as a service connection point in AD DS, 
use Review Configuration in the RD Licensing Manager tool.

Would this keep me from joining the Samba domain on this server?

I'm going to pursue resolving it regardless.

I've also checked all the Samba logs I can find, and the only error I 
see is the following:

[2015/04/17 14:59:31.114933,  0] ../source4/smbd/server.c:121(sig_term)
   Exiting pid 4528 on SIGTERM
[2015/04/17 14:59:31.118968,  0] ../source4/smbd/server.c:121(sig_term)
[2015/04/17 14:59:31.122492,  0] ../source4/smbd/server.c:116(sig_term)
   SIGTERM: killing children
[2015/04/17 14:59:31.125133,  0] ../source4/smbd/server.c:121(sig_term)
   Exiting pid 4514 on SIGTERM
[2015/04/17 14:59:31.128769,  0] ../source4/smbd/server.c:121(sig_term)
[2015/04/17 14:59:31.116065,  0] ../source4/smbd/server.c:121(sig_term)
   Exiting pid 4526 on SIGTERM
   Exiting pid 4523 on SIGTERM
[2015/04/17 14:59:31.142037,  0] ../source4/smbd/server.c:121(sig_term)
   Exiting pid 4521 on SIGTERM
[2015/04/17 14:59:31.140884,  0] ../source4/smbd/server.c:121(sig_term)
[2015/04/17 14:59:31.124917,  0] ../source4/smbd/server.c:121(sig_term)
   Exiting pid 4519 on SIGTERM
[2015/04/17 14:59:31.119915,  0] ../source4/smbd/server.c:121(sig_term)
[2015/04/17 14:59:31.155906,  0] ../source4/smbd/server.c:121(sig_term)
[2015/04/17 14:59:31.174042,  0] ../source4/smbd/server.c:121(sig_term)
   Exiting pid 4524 on SIGTERM
   Exiting pid 4520 on SIGTERM
   Exiting pid 4527 on SIGTERM
   Exiting pid 4516 on SIGTERM
[2015/04/17 14:59:31.180534,  0] ../source4/smbd/server.c:121(sig_term)
   Exiting pid 4529 on SIGTERM
[2015/04/17 14:59:31.155057,  0] ../source4/smbd/server.c:121(sig_term)
   Exiting pid 4522 on SIGTERM
[2015/04/17 14:59:31.193863,  0] ../source4/smbd/server.c:121(sig_term)
   Exiting pid 4517 on SIGTERM
   Exiting pid 4525 on SIGTERM
[2015/04/17 15:00:12.469457,  0] 
../source4/smbd/server.c:370(binary_smbd_main)
   samba version 4.1.6-Ubuntu started.
   Copyright Andrew Tridgell and the Samba Team 1992-2013
[2015/04/17 15:00:20.290825,  0] 
../source4/smbd/server.c:492(binary_smbd_main)
   samba: using 'standard' process model
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call 
setproctitle_init() or link against libbsd-ctor.


It may not be related to my "join" error, but I have no idea what
causes it.

Thanks for any suggestions.

In regard to the first question:

*Steve Ankeny* steve_a at cinergymetro.net 
<mailto:samba%40lists.samba.org?Subject=Re%3A%20%5BSamba%5D%20Joining%202008%20R2%20to%20Samba4%20AD%20DC&In-Reply-To=%3C5534E304.4000707%40cinergymetro.net%3E>
/Mon Apr 20 05:29:08 MDT 2015/

Looking at the Windows Server Event Viewer, I find this error:

The Remote Desktop license server could not be registered as a service
connection point in Active Directory Domain Services (AD DS). Ensure
that there is network connectivity between the license server and AD DS.
To register the license server as a service connection point in AD DS,
use Review Configuration in the RD Licensing Manager tool.

Would this keep me from joining the Samba domain on this server?

I'm going to pursue resolving it regardless.


It appears I need to change the "Discovery Scope" from
"Workgroup" to
"Domain"

However, I am unsure how to do that when I haven't "joined" the
server
to a domain?  Need answer.

Right now, I plan to "deactivate" the License Server, join the domain 
then "reactivate" the License Server.

The License Server is the same machine I'm trying to join to the Samba 
domain.

Any suggestions from those familiar with Windows Remote Desktop Servers?