| Yes, you read that correctly: OES2 SP 1 now | | | | an Active Directory domain. OES2 SP 1 allows you |
| includes Domain Services for Windows (DSFW). | | | | to create a one-way interdomain trust between |
| This innovative idea was announced two years | | | | the DSFW and AD domains. |
| ago at BrainShare and is finally here. In a nutshell, | | | | ⢠You want to streamline your |
| this technology allows eDirectory servers running | | | | workstation deployments by removing the Novell |
| OES2 (Linux kernel) to appear as Active Directory | | | | Client. If you maintain multiple images for |
| Domain controllers. This is not about | | | | workstations depending on the services your |
| synchronization as we have done with Identity | | | | users need, you may have users who have to |
| Manager. It is about enabling your users access to | | | | access services such as file and print from the |
| AD authentication and services using their | | | | Novell side of the house. Instead of relying on the |
| eDirectory user name and password. For instance, | | | | Novell client, with DSFW your users can |
| OES2 SP 1 will help when: | | | | authenticate using native Windows. |
| ⢠Your eDirectory users need to access | | | | |