samba - Jun 2011 - Fwd: removing windows 2003 from samba4&In-Reply-To=<4DEDC91A.3080706@samba.org>

Hello Matthieu,
>Did you wait for a couple of minutes (1 or 2 hours maybe) for the sync
>to settle ? also did you transfer roles to the samba4 DC ?
>
>In anycase you should restart samba with a higher log level so that we
>can have more information.
>
>If needed pop up in #samba-technical for more real time support.
>
>Matthieu.
I've restarted samba with log level 5, above is what i've see ( full
log is to big )

sync appears to be doing fine, i think:

/usr/local/samba/sbin/samba_dnsupdate: schema_fsmo_init: we are master: yes
Child /usr/local/samba/sbin/samba_spnupdate exited with status 0 - Success
Completed SPN update check OK
Child /usr/local/samba/sbin/samba_dnsupdate exited with status 0 - Success
Completed DNS update check OK

and

dreplsrv_notify: DsReplicaSync OK for
c0f2d2cc-eab6-4704-9046-1b9566ed85e3._msdcs.samba4.casa

if i understood right, my samba already have the right roles too

ldb: pdc_fsmo_init: we are master: yes

ldb: naming_fsmo_init: we are master: yes

-----------------------------------------------------
and that appeared when i run dcpromo to remove windows DC:

dreplsrv_periodic_run(): run pending_ops memory=110
dreplsrv_periodic_schedule(300) scheduled for: Tue Jun ?7 17:16:15 2011 BRT
Schema load pass 1: 0/1 of 1 objects left to be converted.
ldb: start ldb transaction (nesting: 0)
ldb: replmd_extended_replicated_objects

...

ldb: replmd_modify

ldb: commit ldb transaction (nesting: 1)
ldb: commit ldb transaction (nesting: 0)
schema_fsmo_init: we are master: yes
Replicated 1 objects (0 linked attributes) for
CN=Schema,CN=Configuration,DC=samba4,DC=casa
UpdateRefs failed with WERR_DS_DRA_BUSY/NT code 0xc00020f6 for
f34e07bd-b0b9-4398-84ca-b3f030a33ef9._msdcs.samba4.casa
CN=Schema,CN=Configuration,DC=samba4,DC=casa
dreplsrv_op_pull_source(WERR_DS_DRA_BUSY) for
CN=Schema,CN=Configuration,DC=samba4,DC=casa
ldb: start ldb transaction (nesting: 0)
ldb: objectclass_modify



thanks in advance.

--
Alan Morais

On 08/06/2011 05:14, Alan wrote:
> Hello Matthieu,
>
>> Did you wait for a couple of minutes (1 or 2 hours maybe) for the sync
>> to settle ? also did you transfer roles to the samba4 DC ?
>>
>> In anycase you should restart samba with a higher log level so that we
>> can have more information.
>>
>> If needed pop up in #samba-technical for more real time support.
>>
>> Matthieu.
> I've restarted samba with log level 5, above is what i've see (
full
> log is to big )
>
> sync appears to be doing fine, i think:
>
> /usr/local/samba/sbin/samba_dnsupdate: schema_fsmo_init: we are master: yes
> Child /usr/local/samba/sbin/samba_spnupdate exited with status 0 - Success
> Completed SPN update check OK
> Child /usr/local/samba/sbin/samba_dnsupdate exited with status 0 - Success
> Completed DNS update check OK
>
> and
>
> dreplsrv_notify: DsReplicaSync OK for
> c0f2d2cc-eab6-4704-9046-1b9566ed85e3._msdcs.samba4.casa
>
> if i understood right, my samba already have the right roles too
>
> ldb: pdc_fsmo_init: we are master: yes
>
> ldb: naming_fsmo_init: we are master: yes
Better try this:
./bin/samba-tool fsmo show --url=ldap://127.0.0.1 -U administrator
> -----------------------------------------------------
> and that appeared when i run dcpromo to remove windows DC:
>
> dreplsrv_periodic_run(): run pending_ops memory=110
> dreplsrv_periodic_schedule(300) scheduled for: Tue Jun  7 17:16:15 2011 BRT
> Schema load pass 1: 0/1 of 1 objects left to be converted.
> ldb: start ldb transaction (nesting: 0)
> ldb: replmd_extended_replicated_objects
>
> ...
>
> ldb: replmd_modify
>
> ldb: commit ldb transaction (nesting: 1)
> ldb: commit ldb transaction (nesting: 0)
> schema_fsmo_init: we are master: yes
> Replicated 1 objects (0 linked attributes) for
> CN=Schema,CN=Configuration,DC=samba4,DC=casa
> UpdateRefs failed with WERR_DS_DRA_BUSY/NT code 0xc00020f6 for
> f34e07bd-b0b9-4398-84ca-b3f030a33ef9._msdcs.samba4.casa
> CN=Schema,CN=Configuration,DC=samba4,DC=casa
> dreplsrv_op_pull_source(WERR_DS_DRA_BUSY) for
> CN=Schema,CN=Configuration,DC=samba4,DC=casa
> ldb: start ldb transaction (nesting: 0)
> ldb: objectclass_modify
You say windows 2003 is it 2003 or 2003r2 ? We mostly test Windows 
2003r2, Windows 2008 and Windows 2008r2. So we might have some corner 
cases still with Windows 2003 (we had last year with samba joining a 
Windows 2003 DC domain).

Once I have your answer I'll try to setup a domain join samba, seize 
roles and try to dcpromo /remove on Windows. It might not be the best 
idea when the other DCs is saying that it wants to leave the domain to 
try to keep it informed about changes ...

If you are in hurry and you transferred all the roles to samba you can 
safely remove the DC by removing the entry in Domain controllers + the 
Server entries in the Configuration naming context, but there isn't much 
interests do it as it will still leave some attributes. This issue 
should be solved soon as we have a couple of patchs waiting in the queue 
for this but for the moment they are not there ...

Matthieu.

-- 
Matthieu Patou
Samba Team        http://samba.org
Private repo      http://git.samba.org/?p=mat/samba.git;a=summary