If you've seen some of the demonstrations of the new Citrix Director 7.6 it's pretty cool!
I wanted to provide the director so that other IT staff here could easily terminate specific process / applications. They tend to terminate entire sessions when really only a specific process is necessary (frozen app that crashed - we have one in particular that is troublesome).
Below is how I setup and got it to work. There are actually some pretty decent guides available from Citrix that cover all these steps in decent detail.
http://support.citrix.com/proddocs/topic/xenapp-xendesktop-76/xad-monitor-director-wrapper.html
http://blogs.citrix.com/2014/10/16/citrix-director-7-6-deep-dive-part-2-support-for-xenapp-6-5/
http://support.citrix.com/article/CTX200330
Citrix XenApp 6.5 with Hotfix Rollup Pack 2 and 5.
XenApp servers running Windows 2008 R2 SP1
Citrix Director 7.6.1 running on Windows 2012 R2
We'll need at least the following machines for my mock setup:
1 x Windows 2012 R2 for the Citrix Director. name = Director
1+ x XenApp 6.5 running as the controller (no applications hosted). name = XAController
1+ x XenApp 6.5 session host mode (no xml). name = XA01
Note: you don't have to install any machines as host mode if you don't want to, I have redundant controller's that don't host any apps, and then install all my "app" servers as session host mode.
Setup Citrix Director: (Director)
- Install and configure your Windows 2012 R2 server
- Install IIS
- Web Server
- Common HTTP Features:
- Default Document
- Directory Browsing
- HTTP Errors
- Static Content
- HTTP Redirection
- Health and Diagnostics:
- HTTP Logging
- Logging Tools
- Tracing
- Performance:
- Static Content Compression
- Dynamic Content Compression
- Security:
- Request Filtering
- Basic Authentication
- Windows Authentication
- Application Development:
- .Net Extensibility 4.5
- ASP
- ASP.NET 4.5
- CGI
- ISAPI Extensions
- ISAPI Filters
- Server side Includes
- Management Tools:
- IIS 6 Management Compatibility:
- IIS 6 Metabase Compatibility
- IIS 6 Scripting Tools
- IIS 6 WMI Compatibility
- IIS Management Scripts and Tools
- Management Service
- Install the below features:
- .Net Framework 4.5 Features:
- WCF Services:
- HTTP Activation
- TCP Port sharing
- Windows Process Activation Service:
- Process Model
- Configuration APIs
- Install dotnet 4.5.1
- From the XenApp / XenDesktop 7.6 installation iso download
- Navigate to \x64\Desktop Director\DesktopDirector.msi and install
- go to \x64\Citrix Policy\CitrixGroupPolicyManagement_x64.msi and install
- Open cmd prompt (runas administrator)
- navigate to \inetpub\wwwroot\director\tools\
- DirectorConfig.exe /registerdotnet
- DirectorConfig.exe /xenapp XAController (this is your XenApp Farm's Controller name).
- To add more than 1 name separate with a comma. XAController1, XAController2
- There is no need to enter non-controller XenApp servers here. So Session host mode XenApp servers that do not run the xml service for instance should not be configured in this setting.
- Ensure that your firewall is configured to allow ports 443, 80, 2513
Setup Session Host XenApp Server: (XA01)
- Attach your XenApp 7.6 iso to your server
- Alternately you can copy the following files from your download to a central location:
- \x64\Virtual Desktop Components\ConfigRemoteMgmt.exe
- \x64\Virtual Desktop Components\Interop.NetFwTypeLib.dll
- \Support\DirectorWMIProvider\DirectorWMIProvider_x64.msi
- Install \Support\DirectorWMIProvider\DirectorWMIProvider_x64.msi
- Ensure dotnet 4.0.30319 or higher is installed
- Open a cmd prompt (runas administrator)
- navigate to \x64\Virtual Desktop Components\ (or where you put the files)
- winrm qc
- yes if prompted
- ConfigRemoteMgmt.exe /configwinrmuser "mydomain\securitygroup" /all
- Ensure that port 2513 is open
Remote Assistance: (XA01)
- On the XenApp session host server ensure that the feature "Remote Assistance" is installed.
- Configure the GPO for remote assistance
- computer config/administrator templates/system/remote assistance
- offer remote assistance and helpers.
PrePopulate Domain at Logon: (Director)
- Now we can also prepopulate the domain box at the logon screen
- This site lays it out very nicely. http://blog.citrix24.com/desktop-director-pre-populate-domain-name-logon-page/
- Edit \inetpub\wwwroot\director\LogOn.aspx
- Find the section with the following: asp:TextBox ID="Domain" runat="server" CssClass="text-box"
- Add the following: Text="my.domain.com" readonly="true"
- refresh the screen
Force SSL and redirect Default Web Site: (Director)
- I like to force SSL for most of my sites. Also I like to redirect the Default so I don't have to type in the directories.
- Redirect Default Website
- On Default Web Site open HTTP Redirect
- Check the "redirect requests to this destination"
- Enter the path https://servername/Director (instead of servername you could also use a DNS name that you setup that is easier to remember)
- Check "redirect all requests to exact destination"
- Apply
- Restart the website
- Force SSL
- On the default site open bindings
- Add https
- select the servername ssl cert
- OK
- Highlight the http binding
- Remove
- Restart the website and then test navigation to https://servername
- Also test http://servername and it shouldn't work.
Note:
In order for Citrix Director to work properly in Internet Explorer 11 I found that you have to add it to your trusted sites security zone.