MS Exchange
Gregory Leblanc
GLeblanc at cu-portland.edu
Thu Sep 16 20:41:05 GMT 1999
I changed PDC on our network just a few weeks ago, and we didn't have any
trouble with our exchange server (except that the administration is a
bitch). Actually both of our exchanges servers are happy and healthy after
changing from a HP pavilion PDC to a Compaq ProLiant 2500. (Talk about a
BIG upgrade) I can't imagine that it's storing the sid of the PDC, but
there IS a domain SID last I checked. I'd guess that that could be the SID
that's screwing up. When I've "ghosted" machines, I have to remove them
from the domain, then add them after I've ghosted, and none of the services
that I have logging in as domain users work, I have to go re-enter the
passwords.
Greg
Involuntary NT Administrator :)
> -----Original Message-----
> From: Florian Laws [mailto:florian at void.s.bawue.de]
> Sent: Thursday, September 16, 1999 1:32 PM
> To: Multiple recipients of list SAMBA-NTDOM
> Subject: Re: MS Exchange
>
>
> On Thu, Sep 16, 1999 at 01:22:27AM +1000, Paul L. Lussier wrote:
> >
> > >> If after, then did you make sure that it only knows
> about the Samba
> > >> PDC and not the old domain controller?
> > >
> > > The old domain controller was, of course, shut down
> during the testing (in
> > >night hours, some backups failed but who cares about them :-) ).
> >
> > Right, but the Exchange server wasn't, which means it's
> trying to authenticate
> > against the old PDC, which has a different SID than the Samba one.
>
> If Exchange was keeping track of the PDC's SID, that would mean that
> you can't even switch from one NT PDC to another.
> I can't really believe that.
> (But then again, it is Microsoft...
> Has anybody got a few spare NT Servers to test? :-)
>
> Cheers,
>
> Florian
>
More information about the samba-ntdom
mailing list