PDC upgrade from beta4 to 2.0 failure

[Todd Pfaff]

I think you guys are being a little too hard on yourselves.  I think the
warnings about PDC support in 2.0 were sufficiently clear and anyone
running a samba-2.0.0 PDC is taking risks.

In my own case, I am running a samba-2.0.0 PDC in production for a couple
of small domains.  It's working sufficiently well, and is at least as good
as the NISgina solution I was using previously.

This patch was a little inconvenient because I found I had to have each NT
workstation re-join the domain after fixing the MACHINE.SID, but since I
only have a few domain members it was not a big deal.


On Sat, 23 Jan 1999, Luke Kenneth Casson Leighton wrote:

> > What this means is that 2.0 has broken code when used
> > as a PDC
> 
> if 2.0 is used as a PDC you will run into difficulties.  the rpc code is
> broken and is about 3 months out of date.
> 
> > - and I'm really sorry about it. I know we didn't
> > advertise 2.0 as being PDC
> 
> we also haven't taken any action to disable 2.0 from being a PDC, and also
> haven't explicitly stated that it should not really be used as a PDC in a
> production environment.
> 
> > ready but this is an amateurish
> > mistake and I'm ashamed of it.
> 
> my fault.
> 

--
Todd Pfaff                         \  Email: pfaff at mcmaster.ca
Computing and Information Services  \ Voice: (905) 525-9140 x22920
ABB 132                              \  FAX: (905) 528-3773
McMaster University                   \
Hamilton, Ontario, Canada  L8S 4M1     \