Since the last months Citrix and Novell worked closely together to provide a solution for customers with Novell eDirectory in place. For the Desktop Delivery Controller and the Virtual Desktop Agents Citrix announced an official support statement which could be found here: http://support.citrix.com/article/CTX123281

Costumers with a synched Active Directory / eDirectory only have to be aware of their GINA chaining. http://community.citrix.com/display/ocb/2009/05/07/XenDesktop+and+Novell+eDirectory

For environments where no Active Directory is in place Novell Open Enterprise Server with Domain Service for Windows (DSfW) http://tinyurl.com/yze7y65 have to be installed and configured before XenDesktop.
Due the fact, that DSfW only accepts Kerberos and no NTLM calls the XenDesktop Active Directory Wizard should not be used to prepare the OU.

You'll need to configure the DDC and VDA without using an OU:
http://support.citrix.com/article/CTX118976

I've developed a little cool tool to configure both components using a simple GUI.

On the Desktop Delivery Controller:
1.Set Desktop Delivery Controller without AD OU to enabled
2.Press Set DDC Config Button

On the Virtual Desktop Agents (WinXP,Vista, Win7)
1.Enter the FQDN of the DDC(s)
2.Press SET VDA Config Button

For those of you who would like to set the DDC configuration by using ZENworks or Group Policies I've added an ADM Template (FarmControllers.adm) into the Novell Integration Tool folder.

Download: Novell Integration Tool

Note: This tool is not supported by Citrix Support and if you have any issues try to configure the VDA manually using regedit or leave me a blog comment.

Here is a working integration scenario, how to implement XenDesktop in a synced AD / eDir environment. It should only be used when the Novell Clients needs to be installed on the virtual desktop. In several projects I've used this configuration without any issues.

The trick is the GINA chaining:

Working Scenario:

• Enable Explicit AD Authentication on default Web Interface site
• Set ctxgina registry key to msgina.dll on the Virtual Machine running the VDA.
• Set default NW account context on NW client installed on VDA.
• Log into WI site with synched AD/NDS account and launch virtual Desktop.
• If the NDS account is in the default Context as per the NW client on the VDA itself then all works fine. You do not have to manually enter your NDS account credentials. The synched AD/NDS accounts were passed along the GINA chain.

Novell already released Domain Services for Windows, which is a feature of Novel Open Enterprise Server 2. Strategic Novell customers should consider implementing Domain Services for Windows if they have no synced Active Directory in place.

Novell Domain Services for Windows provides seamless cross-authentication capabilities between Windows/Active Directory and Novell OES 2 Linux servers. It is a suite of integrated technologies that removes the need for the Novell Client when logging on and accessing data from Windows workstations in eDirectory trees. This technology simplifies the management of users and workstations in mixed Novell-Microsoft environments.