samba - Apr 2007 - LDAP, tdbsam, and profiles

I have a new PDC ready to replace an older one (which is using LDAP
locally).  The new one will be using tdbsam.

I plan to first change LDAP on the existing system to the tdbsam
backend and ensure proper functioning.  I understand I can use the
pdbedit tool to make this change.  Comments?

At this point I would like to ask how profiles (which will be stored
locally on the clients) will be affected by logging on to the
subsequently new PDC.  The docs say that I need to import data from the
old system to the new (again using pdbedit) but if the current system
uses the backend only for authentication why does this need to be done?
 How does the backend influence local profiles?

Thanks for any advice or comments.


      Ask a question on any topic and get answers from real people. Go to Yahoo!
Answers and share what you know at http://ca.answers.yahoo.com

Peter Matulis wrote:
> I have a new PDC ready to replace an older one (which is using LDAP
> locally).  The new one will be using tdbsam.
>
> I plan to first change LDAP on the existing system to the tdbsam
> backend and ensure proper functioning.  I understand I can use the
> pdbedit tool to make this change.  Comments?
>   
Why switch? Why not migrate everything to the new PDC? LDAP allows you 
to use multiple domain controllers and keep them synchronized, which 
gives you a greater degree of safety during the move to the new domain 
controller.
> At this point I would like to ask how profiles (which will be stored
> locally on the clients) will be affected by logging on to the
> subsequently new PDC.  The docs say that I need to import data from the
> old system to the new (again using pdbedit) but if the current system
> uses the backend only for authentication why does this need to be done?
>  How does the backend influence local profiles?
>   
If you aren't using roaming profiles, then you only need to move the 
account data, login scripts, etc..