We looked at the overall use case of Domain Services for Windows in my last post. Let's have a look at the design goals of this product to get a clear understanding of the use cases. The design goals listed below were carefully chosen.
- One of our main design goals was to provide seamless integration between windows and SuSE Linux Enterprise Server10 SP1 (SLES10-SP1). Windows administrators should be able to use Microsoft Management Console ( MMC ) for creating and managing users. The same time, Novell administrators will be able to use Novell tools such as iManager to create or manage objects.
- Another design goal was to re-use existing open source components as much as possible. However, there are some enhancements implemented in some components to get to get the complete functionality. For eg. MIT Kerberos with enhancements to support authorization data field used to contain user validation information or PAC, NTP with netlogon extensions etc.
- Customers having windows and Novell network should be able to leverage the features of this product without re-creating their user identities. So, it was essential to support existing eDirectory deployments and have the same users log-on to both windows and SLES environments.
As you have noted already, seamless integration with Windows world, use of open source components and integration with existing Novell resources keeping eDirectory as the identity vault were the key design goals.