Domain Services for Windows streamlines user and group management and simplifies infrastructure complexity in mixed environments. This technology allows Microsoft Windows users to access OES services using native Windows and Active Directory protocols. By allowing eDirectory servers running on Open Enterprise Server to behave as if they were Active Directory servers, this technology enables companies with both directory services deployments to achieve better coexistence between the two platforms. Users can work in a pure Windows desktop environment and still take advantage of some Open Enterprise Server back-end services and technology, without the need for a Novell Client on the desktop.

1. Understanding Domain Services for Windows. We will show the possibilities and impossibilities of the solution. You will learn that DSfW is not a replacement for Identity Manager and offers an excellent solution to integrate Windows and eDirectory environments.
2. Installing Domain Services for Windows in a new tree. We will explore the possibilities which DSfW has to offer, as with DSfW your eDirectory tree will appear as a Windows domain on the network, which might be useful to establish trust relations with other servers in the network.
   
3. (Re)designing an existing tree for DSfW - The most useful implementation of DSfW is in an existing tree. We will discuss a number of design guidelines, to make sure that DSfW will run smoothly in your existing tree. We will also discuss how to set up name-mapped child domains and non-name-mapped child domains.
4. File Services in a DSfW environment - Your DSfW environment can offer Windows access to native Microsoft Windows clients, combined with file sharing which is based on the Novell NSS file system.
   
5. Modifying the client environment for DSfW - Using DSfW means that you no longer need the Novell client on end-user workstations. We will explain how to set up a user workstation to interact smoothly with a DSfW environment and how to join a domain and how to set up an environment where the Novell client is no longer required.
6. Integrating DSfW with Active Directory - If the networks of two different companies have to join together, using DSfW might be a good solution. By establishing a two-way trust between your AD environment and DSfW you can set up such an integrated environment, where AD users can access eDirectory resources, and eDirectory users can access AD resources.
   
7. Connecting applications to DSfW - Amongst the most important reasons why companies are interested in DSfW, is the integration possibilities that are offered for different applications. We will discuss how to integrate your companies applications with a DSfW environment, but also what you can do if the integration of your application doesn't work out well.