Novell OPEN ENTERPRISE SERVER 2 SP2 - ADMINISTRATION, Руководство по внедрению, Страница: 64 / 288

64 OES 2 SP2: Planning and Implementation Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
NOTE: The list of users and groups in Appendix I, “System User and Group Management in OES 2
SP2,” on page 257 is not exhaustive. For example, the
users
group is not listed.
Create Only eDirectory Users and Groups
For OES 2 services, the LUM technology eliminates the need for local users and groups. We
recommend, therefore, that you avoid the problems discussed in this section by not creating local
users and groups.
6.3 CIFS
Š
Section 6.3.1, “Changing the Server IP Address,” on page 64
6.3.1 Changing the Server IP Address
Reconfiguring CIFS in YaST might not take effect if the server IP address was changed on the server
but not in the OES LDAP server configuration.
To work around this:
1 Reconfigure the LDAP server IP address with the IP address changes.
2
Then change the CIFS IP address configuration.
6.4 ConsoleOne Can Cause JClient Errors
ConsoleOne support is now limited to management of GroupWise and ZENworks for Desktops 7.
If you need to use ConsoleOne
®
to manage either of these supported products on OES 2, make sure
you have installed version 1.3.6h or later.
Earlier versions of ConsoleOne cause JClient errors in iManager.
6.5 CUPS on OES 2
iPrint is the print solution for OES 2 and offers more robust and scalable print services than a CUPS
installation can. iPrint actually uses CUPS to render print jobs prior to sending them to the printer,
but for scalability and performance, printing from the server itself is disabled during iPrint
installation.
If you plan to use iPrint, deselect Print Server in the Primary Functions category during the install
and don’t configure CUPS on the OES 2 server.
6.6 eDirectory
Š
Section 6.6.1, “Avoid Uninstalling eDirectory,” on page 65
Š Section 6.6.2, “Avoid Renaming Trees and Containers,” on page 65
Š
Section 6.6.3, “Default Static Cache Limit Might Be Inadequate,” on page 65
Š
Section 6.6.4, “eDirectory Fails to Start Automatically After a Command Prompt Install,” on
page 65