Novell OPEN ENTERPRISE SERVER - CONVERSION GUIDE 12-2010, Implementation Manual

Page: 292 / 296

292 OES 2 SP3: Planning and Implementation Guide
2
Use auto-created common proxy user in eDirectory configuration for the OES services.
3 Use iManager to create a system user (proxy user) to be used for the OES services.
4
Use the Yast install to configure the Novell AFP and Novell CIFS services as follows:
4a Use an auto-generated common proxy user for all the services.
4b
Specify the contexts under which to search for the AFP or CIFS users.
5 If the AFP/CIFS/Samba user objects are present on NetWare servers, upgrade Novell Security
Services version 2.0.6 in order to upgrade to NMAS 3.2 on NetWare.
Subsequent Servers in a Tree (Example 1)

“S2, S3, S4” on page 292

“S5” on page 292

“S6” on page 292

“S7” on page 292

“S8” on page 292

“S9” on page 293
S2, S3, S4
Administrators need to decide whether these servers should be installed on a new domain or as
additional domain controllers during capacity planning and deployment design. Follow the
OES 2
SP3: Domain Services for Windows Administration Guide to deploy S3 and S4 in the tree.
S5
1
Use an auto-generated common proxy user for all the services.
S6
Use the same procedure as for S5.
S7
Use the same procedure as for S5 and S6.
S8

AFP and CIFS on NetWare don’t require proxy users or password policies for service access.

NMAS needs to be upgraded to 3.2+, if this server hosts the only writable replica for a partition
with AFP or CIFS users.

If this NetWare box is migrated to OES2 SP2, the AFP and CIFS users are enabled for
Universal Password. They need to either use a plain text authentication method, or log in
through NCP (Novell Client) to synchronize their NDS passwords to the Universal Password.
AFP can auto-synchronize the Universal Password if the default DHX authentication method is
used.