module 5: integrating with the environment. agenda ad integration integration with brokers...
TRANSCRIPT
MODULE 5: INTEGRATING WITH THE ENVIRONMENT
Agenda
• AD Integration• Integration with brokers (automated and non)
DIRECTORY JUNCTIONS
Supported Directories
• Novell eDirectory 4.91• Microsoft Active Directory 2003, 2008, 2008
R2
• But any LDAP directory should work. Unidesk does NOT write AD but instead reads and caches information locally
AD Junctions Setup
• Configured in the Users Tab and can be setup at the root of a LDAP directory or down level
• Must have rights and ability to browse to the DN of the container or OU you wish to set as the directory junction point
• Attribute mapping is setup for AD but can be changed for Novel
Attribute Mapping
SETTING UP AN LDAP JUNCTIONLab
BROKER INTEGRATION
Supported Integrated Brokers
• VMware View 5.0, 5.1, 5.1.1 and 5.2 in Unidesk 2.1– Persona not supported, VMware has a broken filter
driver– View Storage Accelerator not supported
• XenDesktop 5.5, 5.6 (all versions)• Must have AD junction setup prior to broker
integration• This support allows for Unidesk to automatically
add desktops to pools/groups and set maintenance mode on desktops
Non-Integrated Brokers
• Unidesk desktops can be manually added to most brokers. Some of these that we have seen include:
• Dell/Quest vWorkspace• LeoStream• And even one homegrown broker
Adding Desktops to Pools
• Pool selection during desktop creation will allow you to Create New pools or Add desktops to existing pools.
• When adding a desktop Unidesk communicates with a Unidesk Agent installed on the View server or Citrix DDC
• Desktop is added during build and waits for registration just like a normal desktop VM
Admin
Desktop VM
Created
Unidesk Mgmt Appliance
Create Desktop(s)
Virtual Machines added to PoolView
Connection ServerDesktop(s)
Created in vCenter
Agent Starts registers w/ View server
During Builds and Updates the VM is
placed in View’s Maintenance Mode
Client Device
To Enable View or Xen Integration
• Install the VIA_Agent on the View Connection Server or Xen DDC
• Ensure ports are open between Unidesk MA, Desktop and the controller/server
• TCP port 390 is used by default• Ensure Agent for Broker is installed in desktop
(View and XenVDA can both be app layers)
Non-Integrated Brokers
• Simply adding Unidesk desktops to a brokers pool (mainly Persistent desktops) will often work.
• Each desktop is added to the pool/group after it is built.
• Broker should be configured not to change the power state of Unidesk VM
• Non-persistent can be a little bit more tricky and require full integration to Unidesk
REVIEWING VIEW INTEGRATIONLab