- Timestamp:
- Nov 24, 2016, 1:14:11 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-NT4Migration.xml
r414 r988 7 7 </chapterinfo> 8 8 9 <title>Migration from NT4 PDC to Samba -3PDC</title>9 <title>Migration from NT4 PDC to Samba PDC</title> 10 10 11 11 <para> … … 13 13 <indexterm><primary>domain control</primary></indexterm> 14 14 This is a rough guide to assist those wishing to migrate from NT4 domain control to 15 Samba- 3-based domain control.15 Samba-based domain control. 16 16 </para> 17 17 … … 28 28 <para> 29 29 <indexterm><primary>migration plan</primary></indexterm> 30 Those wishing to migrate from MS Windows NT4 domain control to a Samba -3domain control30 Those wishing to migrate from MS Windows NT4 domain control to a Samba domain control 31 31 environment would do well to develop a detailed migration plan. So here are a few pointers to 32 32 help migration get underway. … … 39 39 <indexterm><primary>migration process</primary></indexterm> 40 40 The key objective for most organizations is to make the migration from MS Windows NT4 41 to Samba -3domain control as painless as possible. One of the challenges you may experience41 to Samba domain control as painless as possible. One of the challenges you may experience 42 42 in your migration process may well be convincing management that the new environment 43 43 should remain in place. Many who have introduced open source technologies have experienced … … 47 47 <para> 48 48 <indexterm><primary>change motivations</primary></indexterm> 49 Before attempting a migration to a Samba- 3-controlled network, make every possible effort to49 Before attempting a migration to a Samba-controlled network, make every possible effort to 50 50 gain all-round commitment to the change. Know precisely <emphasis>why</emphasis> the change 51 51 is important for the organization. Possible motivations to make a change include: … … 74 74 <indexterm><primary>ADS</primary></indexterm> 75 75 <indexterm><primary>without ADS</primary></indexterm> 76 Make sure everyone knows that Samba -3is not MS Windows NT4. Samba-3 offers76 Make sure everyone knows that Samba is not MS Windows NT4. Samba-3 offers 77 77 an alternative solution that is both different from MS Windows NT4 and offers 78 advantages compared with it. Gain recognition that Samba -3lacks many of the78 advantages compared with it. Gain recognition that Samba lacks many of the 79 79 features that Microsoft has promoted as core values in migration from MS Windows NT4 to 80 80 MS Windows 2000 and beyond (with or without Active Directory services). … … 82 82 83 83 <para> 84 What are the features that Samba -3cannot provide?84 What are the features that Samba cannot provide? 85 85 </para> 86 86 … … 100 100 101 101 <para> 102 The features that Samba -3does provide and that may be of compelling interest to your site102 The features that Samba does provide and that may be of compelling interest to your site 103 103 include: 104 104 </para> … … 135 135 <para> 136 136 <indexterm><primary>successful migration</primary></indexterm> 137 Before migrating a network from MS Windows NT4 to Samba -3, consider all necessary factors. Users137 Before migrating a network from MS Windows NT4 to Samba, consider all necessary factors. Users 138 138 should be educated about changes they may experience so the change will be a welcome one 139 139 and not become an obstacle to the work they need to do. The following sections explain factors that will … … 161 161 <indexterm><primary>slave servers</primary></indexterm> 162 162 <indexterm><primary>multiple domains</primary></indexterm> 163 Samba -3can be configured as a domain controller, a backup domain controller (probably best called163 Samba can be configured as a domain controller, a backup domain controller (probably best called 164 164 a secondary controller), a domain member, or a standalone server. The Windows network security 165 165 domain context should be sized and scoped before implementation. Particular attention needs to be 166 166 paid to the location of the Primary Domain Controller (PDC) as well as backup controllers (BDCs). 167 One way in which Samba -3differs from Microsoft technology is that if one chooses to use an LDAP167 One way in which Samba differs from Microsoft technology is that if one chooses to use an LDAP 168 168 authentication backend, then the same database can be used by several different domains. In a 169 169 complex organization, there can be a single LDAP database, which itself can be distributed (have … … 282 282 <indexterm><primary>SID</primary></indexterm> 283 283 <indexterm><primary>NTuser.DAT</primary></indexterm> 284 Profiles may also be managed using the Samba -3tool <command>profiles</command>. This tool allows the MS284 Profiles may also be managed using the Samba tool <command>profiles</command>. This tool allows the MS 285 285 Windows NT-style security identifiers (SIDs) that are stored inside the profile 286 <filename>NTuser.DAT</filename> file to be changed to the SID of the Samba -3domain.286 <filename>NTuser.DAT</filename> file to be changed to the SID of the Samba domain. 287 287 </para> 288 288 </sect3> … … 296 296 <indexterm><primary>migrate group</primary></indexterm> 297 297 <indexterm><primary>map</primary></indexterm> 298 It is possible to migrate all account settings from an MS Windows NT4 domain to Samba -3. Before299 attempting to migrate user and group accounts, you are STRONGLY advised to create in Samba -3the298 It is possible to migrate all account settings from an MS Windows NT4 domain to Samba. Before 299 attempting to migrate user and group accounts, you are STRONGLY advised to create in Samba the 300 300 groups that are present on the MS Windows NT4 domain <emphasis>AND</emphasis> to map them to 301 301 suitable UNIX/Linux groups. By following this simple advice, all user and group attributes … … 322 322 <indexterm><primary>netlogon share</primary></indexterm> 323 323 <indexterm><primary>BDC</primary></indexterm> 324 Samba -3is set up as a domain controller with netlogon share, profile share, and so on. Configure the &smb.conf; file324 Samba is set up as a domain controller with netlogon share, profile share, and so on. Configure the &smb.conf; file 325 325 to function as a BDC: <parameter>domain master = No</parameter>. 326 326 </para></listitem> … … 415 415 <para> 416 416 There are three basic choices for sites that intend to migrate from MS Windows NT4 417 to Samba -3:417 to Samba: 418 418 </para> 419 419 … … 473 473 </row> 474 474 <row> 475 <entry><para>Move all accounts from NT4 into Samba -3</para></entry>475 <entry><para>Move all accounts from NT4 into Samba</para></entry> 476 476 <entry><para>Copy and improve</para></entry> 477 477 <entry><para>Authentication regime (database location and access)</para></entry> … … 493 493 </row> 494 494 <row> 495 <entry><para>Integrate Samba -3, then migrate while users are active, then change of control (swap out)</para></entry>495 <entry><para>Integrate Samba, then migrate while users are active, then change of control (swap out)</para></entry> 496 496 <entry><para>Take advantage of lower maintenance opportunity</para></entry> 497 497 <entry><para></para></entry> … … 503 503 504 504 <sect2> 505 <title>Samba -3Implementation Choices</title>505 <title>Samba Implementation Choices</title> 506 506 507 507 <variablelist> 508 508 <varlistentry><term>Authentication Database/Backend</term><listitem> 509 509 <para> 510 Samba -3can use an external authentication backend:510 Samba can use an external authentication backend: 511 511 </para> 512 512 … … 516 516 <listitem><para>External server could use Active Directory or NT4 domain.</para></listitem> 517 517 <listitem><para>Can use pam_mkhomedir.so to autocreate home directories.</para></listitem> 518 <listitem><para> Samba -3can use a local authentication backend: <parameter>smbpasswd</parameter>,518 <listitem><para> Samba can use a local authentication backend: <parameter>smbpasswd</parameter>, 519 519 <parameter>tdbsam</parameter>, <parameter>ldapsam</parameter> 520 520 </para></listitem>
Note:
See TracChangeset
for help on using the changeset viewer.
