For organizations looking to eliminate the Novell client, this session provides a detailed look at what's required to meet that goal. We'll discuss the pros and cons of the Novell client and any pitfalls that eliminating it might create for other Novell products. We'll also show you the significance of Domain Services for Windows and how it can co-exist with a Microsoft Active Directory infrastructure. We'll even perform a test implementation and review what tools are used to manage the mixed environment.

1. Life Without the
Novell Client™
Some ideas to consider . . .
Lothar Wegner Greg White
Sr. Technology Sales Specialist Sr. Technology Sales Specialist
Novell, Inc. Novell, Inc.
lwegner@novell.com gwhite@novell.com

2. Overview
What does the Novell Client do? ™
– The Novell Client is one of the key ingredients to maintaining
the NetWare Core Protocol on your network.
®
> What does NetWare Core Protocol do?
– It is responsible for delivering of NetWare services involving
traditional access to Novell Storage Services , eDirectory and ™ ™
ZENworks for Desktop v/4.x thru v/7.x.
®
– If you are eliminating the Novell Client, you have to replace
these client services with something else.
– Managing services using ConsoleOne will still require the
®
Novell Client software.
> Of latest version of Novell products, only GroupWise still requires it.
®
2 © Novell, Inc. All rights reserved.

3. Novell Client ™
Why would getting rid of Novell Client be a good thing?
– Simplified workstation deployment in a mixed environment
– Reduced administration
– Eliminate end-user complexity in a mixed environment
– Application or service compatibility
– Politics
3 © Novell, Inc. All rights reserved.

4. Novell Client ™
Why is getting rid of Novell Client software a “bad idea”?
– It complicates the network setup and mandates the use of CIFS
and the LDAP protocol.
– For users of ZENworks v.4.x thru v.7 it will require the use of a
®
proxy server.
– In some cases without the client, it might slow file access down.
> Traffic now has to go thru LDAP to SAMBA or CIFS to be processed correctly.
– Reduced functionality – IE Salvage
4 © Novell, Inc. All rights reserved.

5. Novell Client ™
Things to consider before you decide if getting rid of the
Novell Client is good for your environment:
– If the network environment has strong dependencies upon the
Novell login scripts, you might want to reconsider. Without the
®
Novell client there are no eDirectory login scripts.
™
– Purge and salvage no longer work for the client-less user.
– Users also lose the ability to set the delete inhibit and rename
inhibit Novell Storage Services file system rights.
™
5 © Novell, Inc. All rights reserved.

6. Removing the Novell Client ™
• Novell CIFS ®
• Domain Services for Windows
6 © Novell, Inc. All rights reserved.

7. Novell CIFS in OES 2
®

8. Novell CIFS Conceptual Overview
®
Novell CIFS runs on the Open Enterprise Server 2 SP2
Linux server, uses Novell eDirectory services for user
™
authentication, and allows the Windows SMB client to
access the data files on an OES 2 SP2 server
8 © Novell, Inc. All rights reserved.

9. Novell CIFS Features and Capabilities
®
CIFS implementation supports the following features
on OES 2 SP2 Linux
– Support for Windows 2000, XP, 2003, Vista Enterprise, Vista
Business, and Vista Ultimate (32-bit/64-bit), and SLED
– Support for new Novell Windows 7 client
– Cross-Protocol File Locking support with AFP, CIFS, and NCP
– Auditing support for file access activities
– Novell OES 2 Distributed FileSystem (DFS) Support
– Support for Novell eDirectory Universal Password
™
– Support for NTLMv1 authentication mode and SMB Signing
– Supports the Novell Trustee Model for file access
– Does not require Linux User Management (LUM) enabling
9 © Novell, Inc. All rights reserved.

10. Novell CIFS Overview ®
Access Methods Authentication File Storage Services
CIFS
Any CIFS / SMB Client
(such as Windows Explorer)
CIFS server
processes
eDirectory users
have automatic
access to Novell
WebDAV
CIFS file services
Web Folders
(Windows Explorer or OES 2 server
Internet Explorer browser)
eDirectory
LDAP server
10 © Novell, Inc. All rights reserved.

11. Novell CIFS and Novell Samba
®
Comparison
Feature Novell CIFS Novell SAMBA
Password policy is
required to allow cifs A Samba-compatible Password Policy is required for
Authentication
users to authenticate to compatibility with Windows workgroup authentication.
eDirectory
It is recommended (but not required) that you create Samba
shares on NSS data volumes. NSS is fully integrated with
NSS is the only file
eDirectory for easy management and using an NSS volume
File system support system supported for this
allows you to take advantage of the rich data security model
release.
in NSS. You can use either iManager for the nssmu utility to
create an NSS volume on an OES2 Linux server..
LUM and Samba
LUM and Samba Users must be enabled for LUM and Samba and assigned to
enablement are not
Enablement a Samba group.
required.
Must be the same user
name and password on Must be the same username and password on both
Username and Password
both workstation and in workstation and in eDirectory
eDirectory
11 © Novell, Inc. All rights reserved.

12. Novell SAMBA Overview ®
Access Methods Authentication File Storage Services
CIFS
Any CIFS / SMB Client
(such as Windows Explorer)
Samba server
processes
Samba users
are enabled
for Linux User
WebDAV
Management
(LUM)
Web Folders
(Windows Explorer or OES 2 server
Internet Explorer browser)
eDirectory
LDAP server
12 © Novell, Inc. All rights reserved.

13. Samba Differences in OES 2 Linux
• The open source Samba software is included as part of SLES 10
which is the base operating system for all OES 2 Linux services
– OES 2 uses this base Samba software, but configures it differently and installs additional
software to take advantage of enhanced services available only provided from OES 2 Linux
• The main differences between base Samba and OES 2 Linux are:
– Samba OES 2 Linux is configured to exclusively use the Novell eDirectory LDAP server
®
™
for secure user authentication
> OES 2 Linux does not support Samba running in NT 4 domain mode
– On OES 2 Linux, Samba shares can be created on native OES 2 NSS volumes or on native
Linux POSIX file systems configured as OES 2 NCP Volumes that are controlled by the full
Novell Trustee Model
– Samba on OES 2 Linux should be managed using the iManager Samba Management plug-
in provided with OES 2
– Although Samba can also provide Windows print services, OES 2 print services are
provided by Novell iPrint, not by the Samba services
13 © Novell, Inc. All rights reserved.

14. Comparing CIFS on NetWare and ®
CIFS on OES 2 SP2 Linux
Feature NetWare 6.5 OES 2 SP2 Linux
64 bit Support No Yes
DFS for NSS Yes Yes
OpLocks Yes Yes
Cross Protocol Locks Yes Yes
NSS Support Yes Yes
File and Record Locking Yes Yes
Domain Emulation Yes Future
Multi-Processor / Multi-Core No Yes
Multi File System Support No Future
NTLMv2/Kerberos No Future
14 © Novell, Inc. All rights reserved.

15. Demonstration

16. Domain Services for Windows in OES2

17. Removing the Novell Client - DSfW ™
iFolder 3.8 Enhanced Identity Novell Cluster Business
Upgrade Manager 3.5 Services Continuity
User & IT Utilities Bundle Edition Cluster
Productivity
Domain SAMBA & AFP stack CIFS stack iPrint
Services for NetAtalk
Interoperability Windows
POSIX Dynamic Archive & Novell Storage DFS w/
File Storage Storage Versioning Services Junction
Technology (NSS) Support
Networking & Auto YaST Windows NetStorage DNS & DHCP Novell
Client eDirectory
Management (64-bit)
Sentinel ready 3rd Party Novell Client Novell Novell Remote
NSS Auditing Linux Apps iManager Manager
XEN Virtualization
Av. on NW & SLE kernels
Av. only on SLE kernel SUSE Linux Enterprise Server
®
17 © Novell, Inc. All rights reserved.

18. Domain Services for Windows
Before
• Had to use the Novell Client to get
™
the full benefit of Novell eDirectory
®
™
and NSS
• Had to manage multiple desktop
images. Administrative overhead
• Use different tools to manage
Active Directory and eDirectory
access rights. MMC to manage AD,
iManager to manage eDirectory
• No good way to integrate Active
Directory resources and eDirectory
resources
18 © Novell, Inc. All rights reserved.

19. Domain Services for Windows
After
• Microsoft administrators can now
use MMC to manage access to
Linux servers
• Anyone that wants file access to
Linux servers, no longer need a
Novell Client™
• Single desktop image to manage
• Lower admin costs (consolidation
of access management overhead)
• More quickly update to newer
desktop environments
• Easily drop in a Linux server and
integrate with an Active Directory
Infrastructure
19 © Novell, Inc. All rights reserved.

20. Component Architecture
Domain Services for Windows is built on the
following components
– Novell eDirectory 8.8 SP4
®
™
– Novell Modular Authentication Service 3.2
– MIT Kerberos 1.6
– An Active Directory Provisioning Handler (ADPH) built
inside the eDirectory Agent
– XAD Framework
– RPC Subsystems required by Windows
– SAMBA
– BIND with GSS extensions
– NTP with Net Logon extensions
20 •
© Novell, Inc. All rights reserved.

21. Domain Services for Windows
Architecture
21 © Novell, Inc. All rights reserved.

22. Domain Services for Windows –
eDirectory ™
DSfW will only work with eDirectory 8.8 SP4 on Open
Enterprise Server 2 SP1 or higher
– ADPH enforces the Security Accounts Manager inside the
agent.
> Allocates Security IDs to users and groups
> Validates entries
> Enables existing eDirectory uses to use AD and RFC2307 authorization.
– Configurable interface support for LDAP server.
– Implements Global Catalog search – port 3268 and 3269
> Requests will be chained to other domains
22 © Novell, Inc. All rights reserved.

23. Domain Services for Windows –
Service list
Following services constitute Domain Services for Windows
– /etc/init.d/named – BIND
– /etc/init.d/ntpd - Time Service
– /etc/init.d/ndsd - eDirectory 8.8 SP4
™
– /etc/init.d/xad – rpcd, xadsd, krb5kdc etc.
– /etc/init.d/winbindd – winbind daemon
– /etc/init.d/nmbd – name lookup daemon
– /etc/init.d/smb – samba daemon
23 © Novell, Inc. All rights reserved.

24. Domain Services for Windows –
Provisioning Tools
• Installation
– ndsdcinit tool provisions a new DSfW domain controller in a new
or existing domain
– Extends eDirectory schema with AD schema
™
– Will be run from YaST when the DSfW pattern is selected
• Administration
– iManager
– MMC Active Directory Users & Computers
– Command line tools
– Existing LDAP and NDAP clients should “just work”
24 © Novell, Inc. All rights reserved.

25. Use Case Scenerios
Domain Services for Windows
• Access OES2 file system without a Novell Client on
™
the workstation
• Single username and password for accessing
resources from Linux, AD and other services
• Standardized administration tool in a heterogeneous
environment
• Custom built desktop application that requires an
AD backend
• Integration of Windows desktop into a Linux
environment (vice versa)
25 © Novell, Inc. All rights reserved.

26. Domain Services for Windows
A Summary
• Domain Services for Windows (DSfW) is a suite of
technologies in Open Enterprise Server (OES) 2 SP1
• Provides client–less login to and file access for
Windows workstations in eDirectory trees
™
• Allows Linux servers to behave as AD servers
• Integrates with existing eDirectory deployments
26 © Novell, Inc. All rights reserved.

27. Demonstration

29. Unpublished Work of Novell, Inc. All Rights Reserved.
This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc.
Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope
of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified,
translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc.
Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.
General Disclaimer
This document is not to be construed as a promise by any participating company to develop, deliver, or market a
product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in
making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents
of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any
particular purpose. The development, release, and timing of features or functionality described for Novell products
remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to
make changes to its content, at any time, without obligation to notify any person or entity of such revisions or
changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc.
in the United States and other countries. All third-party trademarks are the property of their respective owners.