![]() Connecting to a Windows Active Directory tree requires more work, and synchronization services between eDirectory and Active Directory uses Samba, which requires extensive initial manual installation when used with eDirectory. It also is possible to migrate Windows NT domain information into eDirectory with a little effort. Subsequent importation of LDAP schema and data from our 3,000-user database was very fast (less than 5 minutes on NetWare 7 minutes on SuSE Linux). Initial configuration of eDirectory on either platform, while unattended, takes time (about 45 minutes for a baseline eDirectory configuration on SLES 9). We found the network installation process to be much quicker than installing the OES software from the distribution CDs. Our tests showed excellent installation compatibility for both kernel foundations across an array of server platforms (see "How we did it" ). Novell says that a cross-platform, full 64-bit version set of OES services is scheduled to arrive early next year. ![]() ![]() We found that performance of Web-based transaction tasks was only slightly faster (ranging from no appreciable increase to a 7% rise in throughput on SLES 9 OES) than the versions of NetWare 6.5 (DocFinder: 8326) and SLES 9 (DocFinder: 8327) we've tested in the past. While both foundation kernels will run on 64-bit CPUs (which we tested and found no anomalies), both OES application sets are limited to 32-bit use and are only supported by Novell at that level. The odd client out is Novell's Desktop System client, based on Linux, which doesn't have a peer client-side connectivity method that generic Linux, MacOS and Windows clients do. OES provides maximum security measures available for these clients, including easy logon script support and encrypted server communication. Unlike with the Windows 2003 server editions we've tested, Linux and MacOS clients aren't second-class clients. On the Linux side of OES, where iManager leaves off, SLES 9's Yet Another Setup Tool (YaST) takes over for driving operating system-specific configuration and administration detail such as hardware management, low-level settings and DNS/DHCP tasks. This application uses browser real estate efficiently but begs for a high-resolution screen. The downside that still remains for both NetWare and Linux users - even with OES - is that connectivity to Windows Active Directory and NT domains creates a duplicate layer of directory services because that integration requires the installation of Samba proxy services to make the necessary connections.īoth versions of OES can be managed by iManager 2.5, a browser plug-in that gets to the heart of virtually all OES services worth mentioning - especially Novell's evolved eDirectory. Novell has made the eDirectory services largely congruent across both kernels. The OES glue that binds the two base operating systems together is eDirectory, which is easier to implement, manage and administer than the open source OpenLDAP directory service. On the flip side, Linux-based IT organizations can now plug into a cohesive, mature, encrypted authentication infrastructure that's commercially supported worldwide.Ī single OES license entitles the user to build two servers of either foundational type and cluster them together. NetWare shops can now peer Linux applications and services with NetWare-hosted eDirectory and Novell-based identity-management services. ![]() With OES you get a choice: traditional NetWare (Version 6.5 with Service Pack 3), or traditional Linux (SuSE Linux Enterprise Server 9 with Service Pack 1).
0 Comments
Leave a Reply. |