eWEEK Labs Walk-Through: Likewise Enterprise 4.0

The graphical interfaces for Likewise Enterprise depend on the open-source implementation of Microsoft’s .Net Framework, Mono.

I used Likewise Open to join an Ubuntu 7.10 client to a Windows Server 2003 domain.

I had the option of extending my AD schema to include the Unix-friendly attributes that Microsoft introduced with Windows Server 2003 R2, or of leaving my AD schema alone.

I opted to extend the schema of my test AD deployment.

I installed the Likewise Enterprise client software on a CentOS 5 machine and prepared to join the collective.

Likewise Enterprise has a tool for joining domains that resembles the interface found in Windows.

I created a single Cell for mapping Linux user information with AD. In a more complicated environment, I would have created multiple Cells to link AD to multiple NIS (Network Information System) services.

To prepare my test user for cross-platform authentication and management, I visited a new, Likewise-specific tab that the product added to my Windows Server user properties dialog.

I used Likewise Enterprise to create and apply a Group Policy governing my CentOS client’s SELinux service.

The GNOME Project has studded its namesake desktop environment with granular configuration controls; Likewise opens the door to managing these controls via Group Policy.

When the GNOME project moved to a one-window-per-folder model for its Nautilus file manager, many complained. I used Group Policy to mandate a reversion to Nautilus’ old ways.

I fired off a quick report containing information on my inaugural Linux-based AD user.

The GNOME configuration schema files live in the SYSVOL alongside Microsoft’s Windows templates.