Domain Services for Windows: Best Practices for Windows Interoperability

Domain Services for Windows:Best Practices for Windows InteroperabilityNicel KMDavid ShepherdEngineering ManagerSenior Technical Specialistmnicel@novel .comdhepherd@novel .com Agenda" What is Domain Services for Windows (DSfW)?• Features in DSfW• Prerequisites for Successful Deployment• Deployment Options• Demonstration• DSfW in OES2 SP2 and beyond• Third Party Applications Support2© Novell, Inc. All rights reserved.What is Domain Services for Windows? What is Domain Services for Windows?• Domain Services for Windows (DSfW) is a suite of technologies• Provides AD style authentication to users, applications• eDirectory™ users can access AD resources and applications with a cross forest trust in place• Seamless (need to depict that it doesnt change becos of dsfw) access to OES services like file and print services present on NSS or POSIX file systems4© Novell, Inc. All rights reserved. DSfW: What Does It Achieve?eDirectory™ TreeActiveDirectoryForesteDirectoryDSfWCross Forest TrustResource AccessDSfWiManagerAD Style AuthenticationeDirectoryApplicationsUserClientless AccessAdd/Modify UserMMCWindowsUser5© Novell, Inc. All rights reserved.Features in DSfW Features in DSfW• AD protocol support• Domain Emulation/Samba support• Manageability – MMC/iManager• Authentication7© Novell, Inc. All rights reserved. Features in DSfW (cont.)• need more information here.8© Novell, Inc. All rights reserved.Prerequisites forSuccessful Deployment Understand What You Are Trying To Achieve• What is DSfW going to be used for?– Application support. Check that the Windows based application is going to work with DSfW. Do you need a Trust to a real AD Domain for this to work correctly? What is the support position on the proposed solution?– Windows 2003 and 2008 are not yet supported as member servers but do seem to work• DSfW into an existing Tree– eDirectory™ versions need to be up to date. At least one existing eDirectory 8.8 Server should be in the tree with the rest at 8.73.10 or later. Put at least one OES2 Linux Server in place to begin with with any NetWare 6.5 Servers on SP8®– Time synchronization is key. Kerboros is also time sensitive10© Novell, Inc. All rights reserved.Document Outline

• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ
• ÿ