On Wed, 2013-02-20 at 09:09 -0800, Gregory Sloop wrote:
DE Originally I had a Win 2003 DC. I added a samba 4.0.0 DC to the
DE domain, allow full replication to take place and then transferred all
DE the roles to the samba 4.0.0 dc. Finally I removed the Windows DC from
DE the domain.
DE
On 22 February 2013 11:48, Andrew Bartlett abart...@samba.org wrote:
Indeed, if the domain originally came from windows, then
upgradeprovision should NOT be run. Indeed, I would have hoped that the
tool would detect this and would not attempt an upgrade, but clearly
this fails.
Ah. It might
On Fri, 2013-02-22 at 13:12 +, Dominic Evans wrote:
On 22 February 2013 11:48, Andrew Bartlett abart...@samba.org wrote:
Indeed, if the domain originally came from windows, then
upgradeprovision should NOT be run. Indeed, I would have hoped that the
tool would detect this and would not
Originally I had a Win 2003 DC. I added a samba 4.0.0 DC to the
domain, allow full replication to take place and then transferred all
the roles to the samba 4.0.0 dc. Finally I removed the Windows DC from
the domain.
Everything has been working well. Today I upgraded from samba 4.0.0 to
4.0.3 and
DE Originally I had a Win 2003 DC. I added a samba 4.0.0 DC to the
DE domain, allow full replication to take place and then transferred all
DE the roles to the samba 4.0.0 dc. Finally I removed the Windows DC from
DE the domain.
DE Everything has been working well. Today I upgraded from samba
