<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 10. Migrating NetWare Server to Samba-3</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"><link rel="start" href="index.html" title="Samba-3 by Example"><link rel="up" href="DMSMig.html" title="Part II. Domain Members, Updating Samba and Migration"><link rel="prev" href="ntmigration.html" title="Chapter 9. Migrating NT4 Domain to Samba-3"><link rel="next" href="RefSection.html" title="Part III. Reference Section"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 10. Migrating NetWare Server to Samba-3</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ntmigration.html">Prev</a> </td><th width="60%" align="center">Part II. Domain Members, Updating Samba and Migration</th><td width="20%" align="right"> <a accesskey="n" href="RefSection.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="nw4migration"></a>Chapter 10. Migrating NetWare Server to Samba-3</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="nw4migration.html#id368455">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id368561">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id368660">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id368732">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="nw4migration.html#id368903">Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="nw4migration.html#id368911">NetWare Migration Using LDAP Backend</a></span></dt></dl></dd></dl></div><p>
<a class="indexterm" name="id368324"></a>
<a class="indexterm" name="id368330"></a>
Novell is a company any seasoned IT manager has to admire. It has become increasingly
Linux-friendly and is emerging out of a deep regression that almost saw the company
disappear into obscurity. Novell's SUSE Linux hosts the NetWare server and it is the
platform of choice to which many older NetWare servers are being migrated.
It will be interesting to see what becomes of NetWare over time.
Meanwhile, there can be no denying that Novell is a Linux company.
</p><p>
<a class="indexterm" name="id368348"></a>
<a class="indexterm" name="id368355"></a>
<a class="indexterm" name="id368362"></a>
<a class="indexterm" name="id368369"></a>
Whatever flavor of Linux is preferred in your environment, whether Red Hat, Debian,
Gentoo, Mandrake, or SUSE (Novell), the information in this chapter should be read with
the knowledge that file locations may vary a little; even so, the information
in this chapter should provide something of value.
</p><p>
<a class="indexterm" name="id368382"></a>
Contributions to this chapter were made by Misty Stanley-Jones, a UNIX administrator of many
years who surfaced on the Samba mailing list with a barrage of questions and who
regularly helps other administrators to solve thorny Samba migration questions.
</p><p>
<a class="indexterm" name="id368394"></a>
<a class="indexterm" name="id368401"></a>
<a class="indexterm" name="id368407"></a>
<a class="indexterm" name="id368414"></a>
One wonders how many NetWare servers remain in active service. Many are being migrated
to Samba on Linux. Red Hat Linux, SUSE Linux 9.x, and SUSE Linux Enterprise Server 9 are
ideal target platforms to which a NetWare server may be migrated. The migration method
of choice is much dependent on the tools that the administrator finds most natural to use.
The old-hand NetWare guru will likely want to use tools like the NetWare NLM for
<code class="literal">rsync</code> to migrate files from the NetWare server to the Samba server.
The UNIX administrator might prefer tools that are part of the Mars_NWE (Martin Stovers' NetWare
Emulator) open source package. The MS Windows network administrator will likely make use of the
NWConv utility that is a part of Windows NT4 Server. Whatever your tool of choice,
migration will be filled with joyous and challenging moments though probably not
concurrently.
</p><p>
The priority that Misty faced was one of migration of the data files off the NetWare 4.11
server and onto a Samba-based Windows file and print server. This chapter does not pretend
to document all the different methods that could be used to migrate user and group accounts
off a NetWare server. Its focus is on migration of data files.
</p><p>
This chapter tells its own story, so ride along. Maybe the information presented here
will help to smooth over a similar migration challenge in your favorite networking environment.
</p><p>
File paths have been modified to permit use of RPM packages provided by Novell. In the
original documentation contributed by Misty, the Courier-IMAP package had been built
directly from the original source tarball.
</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id368455"></a>Introduction</h2></div></div></div><p>
<a class="indexterm" name="id368462"></a>
Misty Stanley-Jones was recruited by Abmas to administer a network that had
not received much attention for some years and was much in need of a makeover.
As a brand-new sysadmin to this company, she inherited a very old Novell file server
and came with a determination to change things for the better.
</p><p>
A site survey turned up the following details for the old NetWare server:
</p><table class="simplelist" border="0" summary="Simple list"><tr><td><p>200 MHz MMX processor</p></td></tr><tr><td><p>512K RAM</p></td></tr><tr><td><p>24 GB disk space in RAID1</p></td></tr><tr><td><p>Novell 4.11 patched to service pack 7</p></td></tr><tr><td><p>60+ users</p></td></tr><tr><td><p>7 network-attached printers</p></td></tr></table><p>
The company had outgrown this server several years before and was dealing with
severe growing pains. Some of the problems experienced were:
</p><div class="itemizedlist"><ul type="disc"><li><p>Very slow performance</p></li><li><p>Available storage hovering around the 5% range</p><div class="itemizedlist"><ul type="circle"><li><p>Extremely slow print spooling.</p></li><li><p>
Users storing information on their local hard
drives, causing backup integrity problems
</p></li></ul></div></li></ul></div><p>
<a class="indexterm" name="id368550"></a>
At one point disk space had filled up to 100 percent, causing the payroll database
to become corrupt. This caused the accounting department to be down for over
a week and necessitated deployment of another file server. The replacement
server was created with very poor security and design considerations from
a discarded desktop PC.
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id368561"></a>Assignment Tasks</h3></div></div></div><p>
Misty has provided this summary of her migration experience in the hope
that it will help someone to avoid the challenges she faced. Perhaps her
configuration files and background will accelerate your learning as you
grapple with a similar migration challenge. Let there be no confusion,
the information presented in this chapter is provided to demonstrate
how Misty dealt with a particular NetWare migration requirement, and
it provides an overall approach to the implementation of a Samba-3
environment that is significantly divergent from that presented in
<a href="happy.html" title="Chapter 5. Making Happy Users">???</a>.
</p><p>
The complete removal of all site-specific information in order to produce
a generic migration solution would rob this chapter of its character.
It should be recognized, therefore, that the examples given require
significant adaptation to suit local needs and thus
there are some gaps in the example files. That is not Misty's fault;it
is the result of treatment given to her files in an attempt to make
the overall information more useful to you.
</p><p>
<a class="indexterm" name="id368590"></a>
After management reviewed a cost-benefit report as well as an estimated
time-to-completion, approval was given proceed with the solution proposed.
The server was built from purchased components. The total project cost
was $3,000. A brief description of the configuration follows:
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>
<p>3.0 GHz P4 Processor</p>
</td></tr><tr><td>
<p>1 GB RAM</p>
</td></tr><tr><td>
<p>120 GB SATA operating system drive</p>
</td></tr><tr><td>
<p>4 x 80 GB SATA data drives (RAID5 240 GB capacity)</p>
</td></tr><tr><td>
<p>2 x 80 GB SATA removable drives for online backup</p>
</td></tr><tr><td>
<p>A DLT drive for asynchronous offline backup</p>
</td></tr><tr><td>
<p>SUSE Linux Professional 9.1</p>
</td></tr></table><p>
The new system has operated for 6 months without problems. Over the past months
much attention has been focused on cleaning up desktops and user profiles.
</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id368660"></a>Dissection and Discussion</h2></div></div></div><p>
<a class="indexterm" name="id368668"></a>
<a class="indexterm" name="id368675"></a>
<a class="indexterm" name="id368682"></a>
<a class="indexterm" name="id368688"></a>
A decision to use LDAP was made even though I knew nothing about LDAP except that
I had been reading the book & LDAP seemed to provide some of the functionality of Novell's e-Directory Services
and would provide centralized authentication and identity management.
</p><p>
<a class="indexterm" name="id368705"></a>
<a class="indexterm" name="id368711"></a>
<a class="indexterm" name="id368718"></a>
Building the LDAP database took a while and a lot of trial and error. Following
the guidance I obtained from & Administration,</span>& a more current version from source) and built my initial LDAP tree.
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id368732"></a>Technical Issues</h3></div></div></div><p>
<a class="indexterm" name="id368739"></a>
<a class="indexterm" name="id368746"></a>
<a class="indexterm" name="id368753"></a>
<a class="indexterm" name="id368760"></a>
<a class="indexterm" name="id368767"></a>
<a class="indexterm" name="id368773"></a>
<a class="indexterm" name="id368780"></a>
<a class="indexterm" name="id368787"></a>
<a class="indexterm" name="id368794"></a>
The first challenge was to create a company white pages, followed by manually
entering everything from the printed company directory. This used only the inetOrgPerson
object class from the OpenLDAP schemas. The next step was to write a shell script that
would look at the <code class="filename">/etc/passwd</code> and <code class="filename">/etc/shadow</code>
files on our mail server and create an LDIF file from which the information could be
imported into LDAP. This would allow use of LDAP for Linux authentication, IMAP, POP3,
and SMTP.
</p><p>
Because a decision was made to use Courier-IMAP the schema & from the Courier-IMAP source, tarball is necessary to resolve Courier-specific LDAP directory
needs. Where the Courier-IMAP file provided by SUSE is used, this file is named
<code class="filename">courier.schema</code>.
</p><p>
Looking back, it would have been much easier to populate the LDAP directory using a convenient
tool such as <code class="literal">phpLDAPAdmin</code> from the outset. An excessive amount of time was
spent trying to generate LDIF files that could be parsed using the <code class="literal">ldapmodify</code>
so that necessary changes could be written to the directory. This was a learning experience!
</p><p>
An attempt was made to use the PADL POSIX account migration scripts, but I gave up trying to
make them work. Instead, even though it is most inelegant, I wrote a simple script that did
what I needed. It is enclosed as a simple example to demonstrate that you do not need to be
a guru to make light of otherwise painful repetition. This file is listed in <a href="nw4migration.html#sbeamg" title="Example 10.1. A Rough Tool to Create an LDIF File from the System Account Files">???</a>.
</p><div class="example"><a name="sbeamg"></a><p class="title"><b>Example 10.1. A Rough Tool to Create an LDIF File from the System Account Files</b></p><div class="example-contents"><pre class="screen">
#!/bin/bash
cat /etc/passwd | while read l; do
uid=`echo $l | cut -d : -f 1`
uidNumber=`echo $l | cut -d : -f 3`
gidNumber=`echo $1 | cut -d : -f 4`
gecos=`echo $l | cut -d : -f 5`
homeDirectory=`echo $l | cut -d : -f 6`
loginShell=`echo $l | cut -d : -f 6`
userPassword=`cat /etc/shadow | grep $uid | cut -d : -f 2`
echo "dn: cn=$gecos,ou=people,dc=mycompany,dc=com"
echo "objectClass: account"
echo "objectClass: posixAccount"
echo "cn: $gecos"
echo "uid: $uid"
echo "uidNumber: $uidNumber"
echo "gidNumber: $gidNumber"
echo "homeDirectory: $homeDirectory"
echo "loginShell: $loginShell"
echo "userPassword: $userPassword"
done
</pre></div></div><br class="example-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
The PADL MigrationTools are recommended for migration of the UNIX account information into
the LDAP directory. The tools consist of a set of Perl scripts for migration of users, groups,
aliases, hosts, netgroups, networks, protocols, PRCs, and services from the existing ASCII text
files (or from a name service such as NIS). This too set can be obtained from the <a href="http://www.padl.com" target="_top">PADL Web site</a>.
</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id368903"></a>Implementation</h2></div></div></div><p>
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id368911"></a>NetWare Migration Using LDAP Backend</h3></div></div></div><p>
The following software must be installed on the SUSE Linux Enterprise Server to perform
this migration:
</p><table class="simplelist" border="0" summary="Simple list"><tr><td><p>courier-imap</p></td></tr><tr><td><p>courier-imap-ldap</p></td></tr><tr><td><p>nss_ldap</p></td></tr><tr><td><p>openldap2-client</p></td></tr><tr><td><p>openldap2-devel (only for Samba compilation)</p></td></tr><tr><td><p>openldap2</p></td></tr><tr><td><p>pam_ldap</p></td></tr><tr><td><p>samba-3.0.20 or later</p></td></tr><tr><td><p>samba-client-3.0.20 or later</p></td></tr><tr><td><p>samba-winbind-3.0.20 or later</p></td></tr><tr><td><p>smbldap-tools Version 0.9.1</p></td></tr></table><p>
Each software application must be carefully configured in preparation for migration.
The configuration files used at Abmas are provided as a guide and should be modified
to meet needs at your site.
</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id368982"></a>LDAP Server Configuration</h4></div></div></div><p>
The <code class="filename">/etc/openldap/slapd.conf</code> file Misty used is shown here:
</p><pre class="programlisting">
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema
include /etc/openldap/schema/samba3.schema
include /etc/openldap/schema/dhcp.schema
include /etc/openldap/schema/misc.schema
include /etc/openldap/schema/idpool.schema
include /etc/openldap/schema/eduperson.schema
include /etc/openldap/schema/commURI.schema
include /etc/openldap/schema/local.schema
include /etc/openldap/schema/courier.schema
pidfile /var/run/slapd/run/slapd.pid
argsfile /var/run/slapd/run/slapd.args
replogfile /data/ldap/log/slapd.replog
modulepath /usr/lib/openldap/modules
loglevel 256
sasl-host ldap.corp.abmas.org
sasl-realm DIGEST-MD5
sasl-secprops none
TLSCipherSuite HIGH:MEDIUM:+SSLV2
TLSCertificateFile /etc/ssl/certs/private/abmas-cert.pem
TLSCertificateKeyFile /etc/ssl/certs/private/abmas-key.pem
password-hash {SSHA}
defaultsearchbase "dc=abmas,dc=biz"
database bdb
suffix "dc=abmas,dc=biz"
rootdn "cn=manager,dc=abmas,dc=biz"
rootpw {SSHA}gdo/dUvoT4ZJmULz3rUt6A3H/hBEduJ5
directory /data/ldap
mode 0600
checkpoint 500 5
index objectClass eq
index cn eq,sub
index sn eq,sub
index uid eq,sub
index uidNumber eq
index gidNumber eq
index sambaSID eq
index sambaPrimaryGroupSID eq
index sambaDomainName eq
index default sub
cachesize 2000
replica host=baa.corp.abmas.org:389
suffix="dc=abmas,dc=biz"
binddn="cn=replica,dc=abmas,dc=biz"
credentials=verysecret
bindmethod=simple
tls=yes
replica host=ns.abmas.org:389
suffix="dc=abmas,dc=biz"
binddn="cn=replica,dc=abmas,dc=biz"
credentials=verysecret
bindmethod=simple
tls=yes
access to *
by group/groupOfUniqueNames/uniqueMember="cn=LDAP
Administrators,ou=groups,dc=abmas,dc=biz" write
by * break
access to
attrs=userPassword,sambaNTPassword,sambaLMPassword,sambaPwdLastSet,
sambaPwdMustChange,sambaPwdCanChange
by self write
by * auth
access to attrs=hometelephoneNumber,homePostalAddress,
mobileTelephoneNumber,pagerTelephoneNumber
by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
ou=groups,dc=abmas,dc=biz"
write
by self write
by * none
access to dn.sub="ou=Email Aliases,dc=abmas,dc=biz"
by * read
access to dn.children="ou=Email Aliases,dc=abmas,dc=biz"
by dnattr=roleOccupant write
by * read
access to dn.sub="ou=people,dc=abmas,dc=biz"
by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
ou=groups,dc=abmas,dc=biz"
write
by * read
access to dn.sub="ou=bizputers,dc=abmas,dc=biz"
by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
ou=groups,dc=abmas,dc=biz"
write
by * read
access to dn.sub="ou=groups,dc=abmas,dc=biz"
by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
ou=groups,dc=abmas,dc=biz"
write
by * read
access to dn.sub="ou=inactive,dc=abmas,dc=biz"
by * none
access to attrs=namingcontexts,supportedControl
by anonymous =cs
by * read
access to *
by dn.base="cn=replica,ou=people,dc=abmas,dc=biz" write
by * read
</pre><p>
</p><p>
<a class="indexterm" name="id369093"></a>
The <code class="filename">/etc/ldap.conf</code> file used is listed in <a href="nw4migration.html#ch8ldap" title="Example 10.2. NSS LDAP Control File /etc/ldap.conf">???</a>.
</p><div class="example"><a name="ch8ldap"></a><p class="title"><b>Example 10.2. NSS LDAP Control File /etc/ldap.conf</b></p><div class="example-contents"><pre class="screen">
URI ldap://127.0.0.1
base ou=corp,dc=abmas,dc=biz
ldap_version 3
rootbinddn cn=Manager,dc=abmas,dc=biz
pam_filter objectclass=posixAccount
pam_login_attribute uid
pam_member_attribute memberUID
pam_password exop
ssl start_tls
tls_cacertfile /etc/ssl/certs/private/abmas-cert.pem
...
</pre></div></div><br class="example-break"><p>
The NSS control file <code class="filename">/etc/nsswitch.conf</code> has the following contents:
</p><pre class="screen">
passwd: compat ldap
group: compat ldap
</pre><p>
</p><p>
<a class="indexterm" name="id369173"></a>
<a class="indexterm" name="id369179"></a>
In my setup, users authenticate via PAM and NSS using LDAP-based accounts.
The configuration file that controls the behavior of the PAM <code class="literal">pam_unix2</code>
module is shown in <a href="nw4migration.html#sbepu2" title="Example 10.3. The PAM Control File /etc/security/pam_unix2.conf">???</a> file.
This works out of the box with the configuration files in this chapter. It
enables you to have no local accounts for users (it is highly advisable
to have a local account for the root user). Traps for the unwary include the following:
</p><div class="example"><a name="sbepu2"></a><p class="title"><b>Example 10.3. The PAM Control File <code class="filename">/etc/security/pam_unix2.conf</code></b></p><div class="example-contents"><pre class="screen">
auth: use_ldap
account: use_ldap
password: use_ldap
session: none
</pre></div></div><br class="example-break"><a class="indexterm" name="id369231"></a><a class="indexterm" name="id369238"></a><a class="indexterm" name="id369245"></a><div class="itemizedlist"><ul type="disc"><li><p>
If your LDAP database goes down, nobody can authenticate except for root.
</p></li><li><p>
If failover is configured incorrectly, weird behavior can occur. For example,
DNS can fail to resolve.
</p></li></ul></div><p>
I do have two LDAP slave servers configured. That subject is beyond the scope
of this document, and steps for implementing it are well documented.
</p><p>
The following services authenticate using LDAP:
</p><a class="indexterm" name="id369278"></a><a class="indexterm" name="id369284"></a><a class="indexterm" name="id369291"></a><table class="simplelist" border="0" summary="Simple list"><tr><td><p>UNIX login/ssh</p></td></tr><tr><td><p>Postfix (SMTP)</p></td></tr><tr><td><p>Courier-IMAP/IMAPS/POP3/POP3S</p></td></tr></table><p>
<a class="indexterm" name="id369319"></a>
<a class="indexterm" name="id369326"></a>
Companywide white pages can be searched using an LDAP client
such as the one in the Windows Address Book.
</p><p>
<a class="indexterm" name="id369337"></a>
<a class="indexterm" name="id369344"></a>
Having gained a solid understanding of LDAP and a relatively workable LDAP tree
thus far, it was time to configure Samba. I compiled the latest stable Samba and
also installed the latest <code class="literal">smbldap-tools</code> from
<a href="http://idealx.com" target="_top">Idealx</a>.
</p><p>
The Samba <code class="filename">smb.conf</code> file was configured as shown in <a href="nw4migration.html#ch8smbconf" title="Example 10.4. Samba Configuration File smb.conf Part A">???</a>.
</p><div class="example"><a name="ch8smbconf"></a><p class="title"><b>Example 10.4. Samba Configuration File smb.conf Part A</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> <a class="indexterm" name="id371377"></a>
<a class="indexterm" name="id371384"></a>
<a class="indexterm" name="id371390"></a>
Most of these shares are only used by one company group, but they are required
because of some ancient Qbasic and Rbase applications were that written expecting
their own drive letters.
</p><p>
<a class="indexterm" name="id371402"></a>
<a class="indexterm" name="id371409"></a>
<a class="indexterm" name="id371416"></a>
Note: During the process of building the new server, I kept data files
up to date with the Novell server via use of <code class="literal">rsync</code>.
On a separate system (my workstation in fact), which could be rebooted
whenever necessary, I set up a mount point to the Novell server via
<code class="literal">ncpmount</code>. I then created a
<code class="filename">rsyncd.conf</code> to share that mount point out to my
new server, and synchronized once an hour. The script I used to synchronize
is shown in <a href="nw4migration.html#sbersync" title="Example 10.9. Rsync Script">???</a>. The files exclusion list I used
is shown in <a href="nw4migration.html#sbexcld" title="Example 10.10. Rsync Files Exclusion List /root/excludes.txt">???</a>. The reason I had to have the
<code class="literal">rsync</code> daemon running on a system that could be
rebooted frequently is because <code class="constant">ncpfs</code>
(part of the MARS NetWare Emulation package) has a nasty habit of creating stale
mount points that cannot be recovered without a reboot. The reason for hourly
synchronization is because some part of the chain was very slow and
performance-heavy (whether <code class="literal">rsync</code> itself, the network,
or the Novell server, I am not sure, but it was probably the Novell server).
</p><div class="example"><a name="sbersync"></a><p class="title"><b>Example 10.9. Rsync Script</b></p><div class="example-contents"><pre class="screen">
#!/bin/bash
echo "#############################################"
echo "New sync operation starting at `date`"
if ! pgrep -fl '^rsync\> ; then
echo "Good, no rsync is running!"
echo "Synchronizing oink to BHPRO"
rsync -av --exclude-from=/root/excludes.txt
baa.corp:/BHPRO/SYS1/ /data/samba/shares/SYS1
retval=$?
[ ${retval} = 0 ] && echo "Sync operation completed at `date`"
echo "Fixing permissions"
find /data/samba/shares/Engr/ -perm +770 -exec chmod 770 {} \;
find /data/samba/shares/Engr/ ! -group engr -exec chgrp engr {} \;
else
echo "Oh no, rsync is already running!"
echo "#############################################"
fi
</pre></div></div><br class="example-break"><div class="example"><a name="sbexcld"></a><p class="title"><b>Example 10.10. Rsync Files Exclusion List <code class="filename">/root/excludes.txt</code></b></p><div class="example-contents"><pre class="screen">
/Acct/
/Apps/
/DATA/
/Engr/*.pc3
/Engr/plotter
/Engr/APPOLO/
/Engr/LIBRARY/
/Home/Accounting/
/Home/Angie/
/Home/AngieY/
/Home/Brandon/
/Home/Carl/
</pre></div></div><br class="example-break"><p>
After Samba was configured, I initialized the LDAP database. The first
thing I had to do was store the LDAP password in the Samba configuration by
issuing the command (as root):
</p><pre class="screen">
<code class="prompt">root</pre><p>
where & </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
The Idealx smbldap-tools package can be configured using a script called
<code class="literal">configure.pl</code> that is provided as part of the tool. See <a href="happy.html" title="Chapter 5. Making Happy Users">???</a>
for an example of its use. Many administrators, like Misty, choose to do this manually
so as to maintain greater awareness of how the tool-chain works and possibly to avoid
undesirable actions from occurring unnoticed.
</p></div><p>
Now Samba was ready for use and it was time to configure the smbldap-tools. There are two
relevant files, which are usually put into the directory
<code class="filename">/etc/smbldap-tools</code>. The main file,
<code class="filename">smbldap.conf</code> is shown in <a href="nw4migration.html#ch8ideal" title="Example 10.11. Idealx smbldap-tools Control File Part A">???</a>.
</p><div class="example"><a name="ch8ideal"></a><p class="title"><b>Example 10.11. Idealx smbldap-tools Control File Part A</b></p><div class="example-contents"><pre class="screen">
SID="S-1-5-21-725326080-1709766072-2910717368"
slaveLDAP="127.0.0.1"
slavePort="389"
masterLDAP="127.0.0.1"
masterPort="389"
ldapTLS="0"
verify=""
</pre></div></div><br class="example-break"><div class="example"><a name="ch8ideal2"></a><p class="title"><b>Example 10.12. Idealx smbldap-tools Control File Part B</b></p><div class="example-contents"><pre class="screen">
cafile=""
certificate to use to connect to the ldap server
clientcert=""
clientkey=""
suffix="ou=MEGANET2,dc=abmas,dc=biz"
usersdn="ou=People,${suffix}"
computersdn="ou=People,${suffix}"
groupsdn="ou=Groups,${suffix}"
idmapdn="ou=Idmap,${suffix}"
sambaUnixIdPooldn="sambaDomainName=MEGANET2,${suffix}"
scope="sub"
</pre></div></div><br class="example-break"><div class="example"><a name="ch8ideal3"></a><p class="title"><b>Example 10.13. Idealx smbldap-tools Control File Part C</b></p><div class="example-contents"><pre class="screen">
hash_encrypt="MD5"
crypt_salt_format="%s"
userLoginShell="/bin/false"
userHome="/home/%U"
userGecos="Samba User"
defaultUserGid="513"
defaultComputerGid="515"
skeletonDir="/etc/skel"
defaultMaxPasswordAge="45"
</pre></div></div><br class="example-break"><div class="example"><a name="ch8ideal4"></a><p class="title"><b>Example 10.14. Idealx smbldap-tools Control File Part D</b></p><div class="example-contents"><pre class="screen">
userSmbHome=""
userProfile=""
userHomeDrive=""
userScript=""
mailDomain="abmas.org"
with_smbpasswd="0"
smbpasswd="/usr/bin/smbpasswd"
</pre></div></div><br class="example-break"><p>
<a class="indexterm" name="id371746"></a>
Note: I chose not to take advantage of the TLS capability of this.
Eventually I may go back and tweak it. Also, I chose not to take advantage
of the master/slave configuration as I heard horror stories that it was
unstable. My slave servers are replicas only.
</p><p>
The <code class="filename">/etc/smbldap-tools/smbldap_bind.conf</code> file is shown here:
</p><pre class="screen">
slaveDN="cn=Manager,dc=abmas,dc=biz"
slavePw="verysecret"
masterDN="cn=Manager,dc=abmas,dc=biz"
masterPw="verysecret"
</pre><p>
</p><p>
The next step was to run the <code class="literal">smbldap-populate</code> command, which populates
the LDAP tree with the appropriate default users, groups, and UID and GID pools.
It creates a user called Administrator with UID=0 and GID=0 matching the
Domain Admins group. This is fine because you can still log on as root to a Windows system,
but it will break cached credentials if you need to log on as the administrator
to a system that is not on the network.
</p><p>
After the LDAP database has been preloaded, it is prudent to validate that the
information needed is in the LDAP directory. This can be done done by restarting
the LDAP server, then performing an LDAP search by executing:
</p><pre class="screen">
<code class="prompt">root -D "cn=Manager,dc=abmas,dc=biz" \
"(Objectclass=*)"
Enter LDAP Password:
dn: dc=abmas,dc=biz
objectClass: dcObject
objectClass: organization
o: abmas
dc: abmas
dn: ou=People,dc=abmas,dc=biz
objectClass: organizationalUnit
ou: People
dn: ou=Groups,dc=abmas,dc=biz
objectClass: organizationalUnit
ou: Groups
dn: ou=Idmap,dc=abmas,dc=biz
objectClass: organizationalUnit
ou: Idmap
...
</pre><p>
</p><p>
<a class="indexterm" name="id371820"></a>
<a class="indexterm" name="id371827"></a>
<a class="indexterm" name="id371834"></a>
<a class="indexterm" name="id371841"></a>
<a class="indexterm" name="id371847"></a>
With the LDAP directory now initialized, it was time to create the Windows and POSIX
(UNIX) group accounts as well as the mappings from Windows groups to UNIX groups.
The easiest way to do this was to use <code class="literal">smbldap-groupadd</code> command.
It creates the group with the posixGroup and sambaGroupMapping attributes, a
unique GID, and an automatically determined RID. I learned the hard way not to
try to do this by hand.
</p><p>
<a class="indexterm" name="id371866"></a>
<a class="indexterm" name="id371873"></a>
<a class="indexterm" name="id371880"></a>
After I had my group mappings in place, I added users to the groups (the users
don't really have to exist yet). I used the <code class="literal">smbldap-groupmod</code>
command to accomplish this. It can also be done manually by adding memberUID
attributes to the group entries in LDAP.
</p><p>
<a class="indexterm" name="id371898"></a>
<a class="indexterm" name="id371905"></a>
<a class="indexterm" name="id371912"></a>
The most monumental task of all was adding the sambaSamAccount information to each
already existent posixAccount entry. I did it one at a time as I moved people onto
the new server, by issuing the command:
</p><pre class="screen">
<code class="prompt">root</pre><p>
<a class="indexterm" name="id371932"></a>
<a class="indexterm" name="id371939"></a>
<a class="indexterm" name="id371946"></a>
I completed that step for every user after asking the person what his or her current
NetWare password was. The wiser way to have done it would probably have been to dump the
entire database to an LDIF file. This can be done by executing:
</p><pre class="screen">
<code class="prompt">root</pre><p>
<a class="indexterm" name="id371967"></a>
<a class="indexterm" name="id371973"></a>
Then update the LDIF file created by using a Perl script to parse and add the
appropriate attributes and objectClasses to each entry, followed by re-importing
the entire database into the LDAP directory.
</p><p>
Rebuilding of the LDAP directory can be done as follows:
</p><pre class="screen">
<code class="prompt">root<code class="prompt">root<code class="prompt">root<code class="prompt">root<code class="prompt">root</pre><p>
This can be done at any time and for any reason, with no harm to the database.
</p><p>
I first added a test user, of course. The LDIF for this test user looks like
this, to give you an idea:
</p><pre class="screen">
dn:cn=Test User,ou=people,ou=corp,dc=abmas,dc=biz
cn: Test User
gecos: Test User
gidNumber: 513
givenName: Test
homeDirectory: /home/test.user
homePhone: 555
l: Somewhere
l: ST
mail: test.user
o: Corp
objectClass: top
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: sambaSamAccount
postalCode: 12345
sn: User
street: 10 Some St.
uid: test.user
uidNumber: 1074
sambaLogonTime: 0
sambaLogoffTime: 2147483647
sambaKickoffTime: 2147483647
sambaPwdCanChange: 0
displayName: Samba User
sambaSID: S-1-5-21-725326080-1709766072-2910717368-3148
sambaLMPassword: 9D29C287C58448F9AAD3B435B51404EE
sambaAcctFlags: [U]
sambaNTPassword: D062088E99C95E37D7702287BB35E770
sambaPwdLastSet: 1102537694
sambaPwdMustChange: 1106425694
userPassword: {SSHA}UzFZ2VxRGdwUueLnTGtsTBtnsvMO1oj8
loginShell: /bin/false
</pre><p>
</p><p>
Then I went over to a spare Windows NT machine and joined it to the MEGANET2 domain.
It worked, and the machine's account entry under ou=Computers looks like this:
</p><pre class="screen">
dn:uid=w2kengrspare$,ou=Computers,ou=MEGANET2,dc=abmas,dc=biz
objectClass: top
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: sambaSamAccount
cn: w2kengrspare$
sn: w2kengrspare$
uid: w2kengrspare$
uidNumber: 1104
gidNumber: 515
homeDirectory: /dev/null
loginShell: /bin/false
description: Computer
gecos: Computer
sambaSID: S-1-5-21-725326080-1709766072-2910717368-3208
sambaPrimaryGroupSID: S-1-5-21-725326080-1709766072-2910717368-2031
displayName: W2KENGRSPARE$
sambaPwdCanChange: 1103149236
sambaPwdMustChange: 2147483647
sambaNTPassword: CA199C45CB6737035DB6D9D9F6CD1834
sambaPwdLastSet: 1103149236
sambaAcctFlags: [W ]
</pre><p>
</p><p>
<a class="indexterm" name="id372066"></a>
So now I could log on with a test user from the machine w2kengrspare. It was all well and
good, but that user was in no groups yet and so had pretty boring access. I fixed that
by writing the login script! To write the login script, I used
<a href="http://www.kixtart.org" target="_top">Kixtart</a> because it will work
with every architecture of Windows, has an active and helpful user base, and was both
easier to learn and more powerful than the standard netlogon scripts I have seen.
I also did not have to do a logon script per user or per group.
</p><p>
<a class="indexterm" name="id372086"></a>
I downloaded Kixtart and put the following files in my netlogon share:
</p><pre class="screen">
KIX32.EXE
KX32.dll
KX95.dll <-- Not needed unless you are running Win9x clients.
kx16.dll <-- Probably not needed unless you are running DOS clients.
kxrpc.exe <-- Probably useless as it has to run on the server and can
only be run on NT. It's for Windows 95 to become group-aware.
We can get around the need.
</pre><p>
</p><p>
<a class="indexterm" name="id372109"></a>
I then wrote the <code class="filename">logon.kix</code> file that is shown in
<a href="nw4migration.html#ch8kix" title="Example 10.15. Kixtart Control File File: logon.kix">???</a>. I chose to keep it all in one file, but it
can be split up and linked via include directives.
</p><div class="example"><a name="ch8kix"></a><p class="title"><b>Example 10.15. Kixtart Control File File: logon.kix</b></p><div class="example-contents"><pre class="screen">
; This script just calls the other scripts.
; First we want to get things done for everyone.
; Second, we do first-time login stuff.
; Third, we go through the group-oriented scripts one at a time.
; We want to check for group membership here to avoid the overhead of running
; scripts which don't apply.
call "\\massive\netlogon\scripts\main.kix"
call "\\massive\netlogon\scripts\setup.kix"
IF INGROUP("MEGANET2\ACCT")
call "scripts\acct.kix"
ENDIF
IF INGROUP("MEGANET2\ENGR","MEGANET2\RECEPTIONIST")
call "\\massive\netlogon\scripts\engr.kix"
ENDIF
IF INGROUP("MEGANET2\FURN")
call "\\massive\netlogon\scripts\furn.kix"
ENDIF
IF INGROUP("MEGANET2\TRUSS")
call "\\massive\netlogon\scripts\truss.kix"
ENDIF
</pre></div></div><br class="example-break"><div class="example"><a name="ch8kix2"></a><p class="title"><b>Example 10.16. Kixtart Control File File: main.kix</b></p><div class="example-contents"><pre class="screen">
break on
; Choose whether to hide the login window or not
IF INGROUP("MEGANET2\Domain Admins")
USE Z: \\massive\everything
SETCONSOLE("show")
ELSE
; Nobody cares about seeing the login script except admins
SETCONSOLE("hide")
ENDIF
; Delete all previously connected shares
USE * /delete
SETTITLE("Logging on @USERID to @LDOMAIN at @TIME")
; Set the time on the workstation
$Timeserver = "\\massive"
Settime $TimeServer
; Map the home directory
USE H: @HOMESHR ; connect to user's home share
IF @ERROR = 0
H:
CD @HOMEDIR ; change directory to user's home directory
ENDIF
; Everyone gets the N drive
USE N: \\massive\network
</pre></div></div><br class="example-break"><div class="example"><a name="ch8kix3"></a><p class="title"><b>Example 10.17. Kixtart Control File File: setup.kix, Part A</b></p><div class="example-contents"><pre class="screen">
; My setup.kix is where all of the redirection stuff happens. Note that with
; the use of registry keys, this only happens the first time they log in ,or if
; I delete the pertinent registry keys which triggers it to happen again:
; Check to see if we have written the abmas sub-key before
$RETURNCODE = EXISTKEY("HKEY_CURRENT_USER\abmas")
IF NOT $RETURNCODE = 0
; Add key for abmas-specific things on the first login
ADDKEY("HKEY_CURRENT_USER\abmas")
; The following key gets deleted at the end of the first login
ADDKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
ENDIF
; People with laptops need My Documents to be in their profile. People with
; desktops can have My Documents redirected to their home directory to avoid
; long delays with logging out and out-of-sync files.
; Check to see if this is the first login -- doesn't make sense to do this
; at the very first login
$RETURNCODE = EXISTKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
IF NOT $RETURNCODE = 0
; We don't want to do this stuff for people with laptops or people in the FURN
; group. (They store their profiles in a different server)
IF NOT INGROUP("MASSIVE\Laptop","MASSIVE\FURN")
$RETURNCODE=EXISTKEY("HKEY_CURRENT_USER\abmas\profile_copied")
; A crude way to tell what OS our profile is for and copy the "My Documents"
; to the redirected folder on the server. It works because the profiles
; are stored as \\server\profiles\user\architecture
IF NOT $RETURNCODE = 0
IF EXIST("\\massive\profiles\@userID\WinXP")
copy "\\massive\profiles\@userID\WinXP\My Documents\*"
"\\massive\@userID\"
ENDIF
IF EXIST("\\massive\profiles\@userID\Win2K")
copy "\\massive\profiles\@userID\Win2K\My Documents\*"
"\\massive\@userID\"
ENDIF
IF EXIST("\\massive\profiles\@userID\WinNT")
copy "\\massive\profiles\@userID\WinNT\My Documents\*"
"\\massive\@userID\"
ENDIF
</pre></div></div><br class="example-break"><div class="example"><a name="ch8kix3b"></a><p class="title"><b>Example 10.18. Kixtart Control File File: setup.kix, Part B</b></p><div class="example-contents"><pre class="screen">
; Now we will write the registry values to redirect the locations of "My
Documents"
; and other folders.
ADDKEY("HKEY_CURRENT_USER\abmas\profile_copied")
WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Explorer\User
Shell Folders", "Personal","\\massive\@userID","REG_SZ")
WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Explorer\User
Shell Folders", "My Pictures", "\\massive\@userID\My Pictures", "REG_SZ")
IF @PRODUCTTYPE="Windows 2000 Professional" or @PRODUCTTYPE="Windows XP
Professional"
WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Explorer\User
Shell Folders", "My Videos", "\\massive\@userID\My Videos", "REG_SZ")
WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Explorer\User
Shell Folders", "My Music", "\\massive\@userID\My Music", "REG_SZ")
WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Explorer\User
Shell Folders", "My eBooks", "\\massive\@userID\My eBooks", "REG_SZ")
ENDIF
ENDIF
ENDIF
; Now we will delete the FIRST_LOGIN sub-key that we made before.
; Note - to run this script again you will want to delete the HKCU\abmas
; sub-key, log out, and log back in.
$RETURNVALUE = EXISTKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
IF $RETURNVALUE = 0
DELKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
ENDIF
</pre></div></div><br class="example-break"><div class="example"><a name="ch8kix4"></a><p class="title"><b>Example 10.19. Kixtart Control File File: acct.kix</b></p><div class="example-contents"><pre class="screen">
; And here is one group-oriented script to show what can be
; done that way: acct.kix:
IF INGROUP("MASSIVE\Acct_Admin","MASSIVE\HR")
USE I: \\MEGANET2\HR_PR
ENDIF
; Set up printer
$RETURNVALUE = existkey("HKEY_CURRENT_USER\Printers\,,massive,acct_hp8500")
IF NOT $RETURNVALUE = 0
ADDPRINTERCONNECTION("\\massive\acct_hp8500")
SETDEFAULTPRINTER("\\massive\acct_hp8500")
ENDIF
; Set up drive mappings
USE M: \\massive\ACCT
IF INGROUP("MEGANET2\ABRA")
USE T: \\trussrv\abra
ENDIF
</pre></div></div><br class="example-break"><p>
As you can see in the script, I redirected the My Documents to the user's home
share if he or she were not in the Laptop group. I also added printers on a
group-by-group basis, and if applicable I set the group printer. For this to
be effective, the print drivers must be installed on the Samba server in the
<code class="filename">[print$]</code> share. Ample documentation exists about how to
do that, so it is not covered here.
</p><p>
I call this script via the logon.bat script in the [netlogon] directory:
</p><pre class="screen">
\\corpsrv\netlogon\kix32 \\corpsrv\netlogon\logon.kix /f
</pre><p>
I only had to fully qualify the paths for Windows 9x, as Windows NT and
greater automatically add [NETLOGON] to the path.
</p><p>
Also of note for Win9x is that the drive mappings and printer setup will not
work because they rely on RPC. You merely have to put the appropriate settings
into the <code class="filename">c:\autoexec.bat</code> file or map the drives manually.
One option is to check the OS as part of the Kixtart script, and if it
is Win9x and is the first login, copy a premade
<code class="filename">autoexec.bat</code> to the <code class="filename">C:</code> drive. I
have only three such machines, and one is going away in the very near future,
so it was easier to do it by hand.
</p><p>
<a class="indexterm" name="id372323"></a>
At this point I was able to add the users. This is the part that really falls
into upgrade. I moved the users over one group at a time, starting with the
people who used the least amount of resources on the network. With each group
that I moved, I first logged on as a standard user in that group and took
careful note of the environment, mainly the printers he or she used, the PATH,
and what network resources he or she had access to (most importantly, which ones
the user actually needed access to).
</p><p>
I then added the user's SambaSamAccount information as mentioned earlier,
and join the computer to the domain. The very first thing I had to do was to
copy the user's profile to the new server. This was very important, and I really
struggled with the most effective way to do it. Here is the method that worked
for every one of my users on Windows NT, 2000, and XP:
</p><div class="procedure"><ol type="1"><li><p>
Log in as the user on the domain. This creates the local copy
of the user's profile and copies it to the server as he or she logs out.
</p></li><li><p>
Reboot the computer and log in as the local machine administrator.
</p></li><li><p>
Right-click My Computer, click Properties, and navigate to the
user profiles tab (varies per version of Windows).
</p></li><li><p>
Select the user's local profile <code class="constant">(COMPUTERNAME\username)</code>,
and click the <code class="literal">Copy To</code> button.
</p></li><li><p>
In the next dialog, copy it directly to the profiles share on the
Samba server (in my case \\PDCname\profiles\user\<architecture>.
You will have had to make a connection to the share as that
user (e.g., Windows Explorer type \\PDCname\profiles\username).
</p></li><li><p>
When the copy is complete (it can take a while) log out, and log back in
as the user. All of his or her settings and all contents of My Documents,
Favorites, and the registry should have been copied successfully.
</p></li><li><p>
If it doesn't look right (the dead giveaway is the desktop background),
shut down the computer without logging out (power cycle) and try logging
in as the user again. If it still doesn't work, repeat the steps above.
I only had to ever repeat it once.
</p></li></ol></div><p>
Words to the Wise:
</p><div class="itemizedlist"><ul type="disc"><li><p>
If the user was anything other than a standard user on his or her system
before, you will save yourself some headaches by giving him or her identical
permissions (on the local machine) as his or her domain account <span class="emphasis"><em>before</em></span>
copying the profile over. Do this through the User Administrator
in the Control Panel, after joining the computer to the domain and
before logging on as that user for the first time. Otherwise the user will
have trouble with permissions on his or her registry keys.
</p></li><li><p>
If any application was installed for the user only, rather than for
the entire system, it will probably not work without being reinstalled.
</p></li></ul></div><p>
After all these steps are accomplished, only cleanup details are left. Make sure user's
shortcuts and Network Places point to the appropriate place on the new server, check
the important applications to be sure they work as expected and troubleshoot any problems
that might arise, and check to be sure the user's printers are present and working. By the
way, if there are any network printers installed as system printers (the Novell way),
you will need to log in as a local administrator and delete them.
</p><p>
For my non-laptop systems, I would then log in and out a couple times as the user
to be sure that his or her registry settings were modified, and then I was finished.
</p><p>
Some compatibility issues that cropped up included the following:
</p><p>
Blackberry client: It did not like having its registry settings moved around
and so had to be reinstalled. Also, it needed write permissions to a portion of
the hard drive, and I had to give it those manually on the one system where
this was an issue.
</p><p>
CAMedia: Digital camera software for Canon cameras caused all kinds of trouble
with the registry. I had to use the Run as service to open the registry of
the local user while logged in as the domain user, and give the domain user
the appropriate permissions to some registry keys, then export that portion
of the registry to a file. Then, as the domain user, I had to import that file
into the registry.
</p><p>
Crystal Reports version 7: More registry problems that were solved by recopying
the user's profile.
</p><p>
Printing from legacy applications: I found out that Novell sends its jobs to
the printer in a raw format. CUPS sends them in PostScript by default. I had
to make a second printer definition for one printer and tell CUPS specifically
to send raw data to the printer, then assign this printer to the LPT port with
Kixtart's version of the net use command.
</p><p>
These were all eventually solved by elbow grease, queries to the Samba mailing
list and others, and diligence. The complete migration took about 5 weeks.
My userbase is relatively small but includes multiple versions of Windows,
multiple Linux member servers, a mechanized saw, a pen plotter, and legacy
applications written in Qbasic and R:Base, just to name a few. I actually
ended up making some of these applications work better (or work again, as
some of them had stopped functioning on the old server) because as part of
the process I had to find out how things were supposed to work.
</p><p>
The one thing I have not been able to get working is a very old database that
we had around for reference purposes; it uses Novell's Btrieve engine.
</p><p>
As the resources compare, I went from 95 percent disk usage to just around 10 percent.
I went from a very high load on the server to an average load of between one
and two runnable processes on the server. I have improved the security and
robustness of the system. I have also implemented
<a href="http://www.clamav.net" target="_top">ClamAV</a> antivirus software,
which scans the entire Samba server for viruses every 2 hours and
quarantines them. I have found it much less problematic than our ancient
version of Norton Antivirus Corporate Edition, and much more up-to-date.
</p><p>
In short, my users are much happier now that the new server is running, and that
is what is important to me.
</p></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ntmigration.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="DMSMig.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="RefSection.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 9. Migrating NT4 Domain to Samba-3 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Part III. Reference Section</td></tr></table></div></body></html>