Install or Upgrade to Citrix Director 7.x Using Director .msi file

Note: If you are installing Director for the first time, follow New Installation instructions. If you are upgrading from an existing Director 7.x version to Director 7.y, follow the Upgrade Instructions.

New Installation of Director 7.x

Prerequisites:

Installation steps:

  1. Install Director 7.x from the .msi file.
  2. Install the CitrixGroupPolicyManagement .msi file available in the Citrix Policy folder in XenDesktop DVD.

Post-installation steps:

  • To configure Director with the Delivery Controller, run the command:

    “C:inetpubwwwrootDirectortools>DirectorConfig /ddc <FQDN/IPAddress-of-DDC>”

  • For a successful log on to Director, register ASP.net with IIS. To do this, run the command:

    C:inetpubwwwrootDirectortools>DirectorConfig.exe /registerdotnet”

  • Create a rule in the Windows Firewall to allow communication from Port 80, 443, 2513, 5985

Upgrade from Director 7.x to Director 7.y

Prerequisites:

  • If you are upgrading from Director 7.0, 7.1, or 7.5, install .Net 4.5.1

Installation steps:

  • Install Director 7.x from the Director .msi file.

Post-installation steps:

  • Run the command:

    “C:inetpubwwwrootDirectortoolsDirectorConfig.exe /upgrade”

Note: You must run the command with elevated administrative rights to be successful. Running this command is a prerequisite for availability of the latest Director configuration settings.

For more information, see Knowledge Centre article, CTX137990 – Citrix Director – DirectorConfig Tool.

List of required IIS features

To install IIS features, go to Server Manager, select Add Roles and Features, and select the following features from each category:

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

Apart from the IIS server role, enable the following features from the Features section in Server Manager:

.Net Framework 4.5 Features:

  • WCF Services:
  • HTTP Activation
  • TCP Port sharing

Windows Process Activation Service:

  • Process Model
  • Configuration APIs
How Do I Articles

Related:

7021548: IIS 64-Bit Mode Error When Building Verastream .NET Web Application Project

Use the following information to check or change the IIS mode, and configure Web Builder to match.

IIS Configuration on Windows Server 2008 or Windows 7

Use the following steps to check or change the IIS mode on Windows Server 2008 or Windows 7:

  1. Run the IIS Manager by opening Start > Control Panel > System and Security > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) Manager. The steps may vary depending on your operating system.
  2. In the Connections frame, open Application Pools and select your web site pool.
  3. In the right pane, under Edit Application Pool, click Advanced Settings.
  4. In the Advanced Settings dialog, in the “(General)” section, select “Enable 32-Bit Applications.”
  5. Set this value to False to run in 64-bit mode, or set it to True to run in 32-bit mode.

IIS Configuration on Windows Server 2003 or Windows XP

Use the following steps to check the IIS mode on Windows Server 2003 or Windows XP.

  1. Open Control Panel > Administrative Tools > Computer Management > Services and Applications > Internet Information Services (IIS) Manager > Web Sites. The steps may vary depending on your operating system.
  2. Right-click your web site and click Properties.
  3. On the Home Directory tab, under Application settings, click Configuration.
  4. In the Application extensions list, scroll down to extension .aspx and mouseover its Executable Path.
  5. The mouseover popup text indicates the .NET Framework directory that is being used.
    Mode
    Microsoft .NET Framework Directory
    32-bit
    C:WindowsMicrosoft.NETFrameworkv2.0.50727
    64-bit
    C:WindowsMicrosoft.NETFramework64v2.0.50727

Alternative IIS Configuration using Command Line Utility

Use the following information to check or change the IIS mode in a Command Prompt window. Note: On Windows 7 and later operating systems, you must install “IIS 6 Management Compatibility” to run the Adsutil.vbs utility. See also Technical Note 10081.

To determine the IIS mode, enter:

cscript %SYSTEMDRIVE%inetpubadminscriptsadsutil.vbs get W3SVC/AppPools/Enable32bitAppOnWin64

If the command returns False (0), IIS is in 64-bit mode. If it returns True (1), IIS is in 32-bit mode.

If you prefer to change IIS from 64-bit mode to 32-bit mode, run the following commands to register 32-bit ASP.NET with IIS and enable IIS 32-bit mode:

C:WindowsMicrosoft.NETFrameworkv2.0.50727aspnet_regiis.exe –i

cscript.exe C:inetpubAdminScriptsadsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 1

Configuring Verastream Web Builder

Once you have checked or changed the IIS mode, follow the steps below to configure Web Builder to match.

  1. In Web Builder, click Options > Web Builder Settings.
  2. In the left pane, select Microsoft Tools.
  3. In the .NET Framework directory field, browse to and select the appropriate directory, and then click Open > OK.
    Mode
    Microsoft .NET Framework Directory
    32-bit
    C:WindowsMicrosoft.NETFrameworkv2.0.50727
    64-bit
    C:WindowsMicrosoft.NETFramework64v2.0.50727
  1. Build your Verastream project.

Note: Once a Verastream project is built, it can run in either a 32- or 64-bit version of IIS. It is just the build process that needs to be configured to use the correct .NET Framework version.

Web Builder uses the .NET Framework aspnet_regiis.exe registration tool to install ASP.NET and update IIS.

Beginning in VHI version 7.5, a new installation defaults to use the 64-bit .NET Framework for the Legacy .NET Web Application project type. If you upgraded from a pre-7.5 installation, your previous setting is retained.

Related:

7021230: REST Web Console custom tab attribute picker fails to search on name property

This document (7021230) is provided subject to the disclaimer at the end of this document.

Environment

Directory and Resource Administrator 9.1.0
Directory and Resource Administrator REST Services 9.1.0
Directory and Resource Administrator REST Web Console 9.1.0

Situation

Within the REST Web Console the ability exists to customize the user pages. This is done using the customize Web Console option, from within the Web Console. This will allow the DRA Product Administrator the ability to add additional fields to the pages within the Web Console. When adding a new field, that field must be associated with an attribute managed by DRA. The customization wizard provides a search box, allowing the DRA Product Administrator the ability to search for an attribute. This search will allow you to search for an attribute by certain properties. One property is the name of the attribute. When searching by name of attribute, the Web Console will return an error: Error The value name can’t be NULL. Parameter Name: Input.

Resolution

Within the IIS Folder on each Web Server, you will need to edit two specific files. This edit will need to be done on every IIS sever hosting the DRAClient Website.

  • File # 1 — C:inetpubwwwrootDRAClientcomponentslibui-templatesattribute-search-criteria.json
  1. Locate Line 7
  2. Change the text FROM “attributeName”: “name”, TO “attributeName”: “nameValue”,
  • File # 2 — c:inetpubwwwrootdraclientlocaleen-uslocalized.json
  1. Locate line 496
  2. Change the text from “name”: “Name”, TO “nameValue”: “Name”,

Additional Information

The text changes listed above are the exact text to be changed, including the quotation marks. It is recommended to create a backup of both files before making any changes. You will need to restart the IIS sever, and start a new Web browser session; before the changes apply. These changes do not automatically replicate between IIS Severs.

This issue applies only to the product versions listed within the Environment section.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Event ID 5161 — IIS Web Site Availability

Event ID 5161 — IIS Web Site Availability

Updated: March 24, 2009

Applies To: Windows Server 2008 R2

Internet Information Services (IIS) Web sites that use HTTP rely on several important IIS components for their availability. The Windows Process Activation Service (WAS), the World Wide Publishing Service (W3SVC), the HTTP service, all must be running correctly. In addition, a properly running application pool must be available for the Web site’s applications. If any of these components is not functioning, the Web site will not be available.

Event Details

Product: Internet Information Services
ID: 5161
Source: Microsoft-Windows-WAS
Version: 7.5
Symbolic Name: WAS_EVENT_WMS_APPLICATION_NO_APP_ROOT_ERROR
Message: Site %1 has no root application defined, so the site will be ignored.

Resolve
Set the application path for a site

A Web site must have a valid application path. If the application path is incorrect, the site will not start. Set a valid application path for the Web site, then restart the site.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Set a valid application path for the Web site

To set a valid application path for the Web site:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type cd %Windir%\system32\inetsrv\config
  3. Type notepad ApplicationHost.config.
  4. In Notepad, search for the sites section under system.applicationHost, and locate the Web site that is causing the error.
  5. Correct the application path, or add the following to the site configuration so that it has a default path:

        <application path=”/”>

              <virtualDirectory path=”/” physicalPath=”%SystemDrive%\inetpub\wwwroot” />

        </application>

Restart the Web site

To restart the Web site:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the IIS Manager Connections Pane, expand the computer name.
  4. Expand Sites.
  5. Select the Web site that has to be restarted.
  6. In the Actions pane, click Stop to stop the site.
  7. In the Actions pane, click Start to start the site.

Verify

To verify that a Web site is started, you can use either IIS Manager or the appcmd command line utility.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Web site is started by using the appcmd command line utility:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Change the directory to %SystemDrive%\Windows\System32\inetsrv.
  3. Run the following command: appcmd.exe list site -site.name:”Site Name”. If the Web site is started, the output will resemble the following:

        SITE “Default Web Site” (id:1,bindings:http/*:80:,state:Started)

To verify that the Web site is started by using IIS Manager:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the Connections pane, expand the computer name.
  4. In the Connections pane, click the Sites node.
  5. In Features View, look for the Web site name. The Web site status will be indicated under the Status column. If the Web site is started and is using the HTTP protocol, Started(http) will appear.

Related Management Information

IIS Web Site Availability

Internet Information Services (IIS) 7.5

Related:

Event ID 5132 — IIS WAS Configuration

Event ID 5132 — IIS WAS Configuration

Updated: March 24, 2009

Applies To: Windows Server 2008 R2

The Internet Information Services (IIS) Windows Process Activation Service (WAS) configuration manager manages configuration for the application pools and protocol adapters that it maintains. If WAS encounters problems when it reads configuration or reacts to configuration change notifications, configuration changes for the entities it manages may not be processed.

Event Details

Product: Internet Information Services
ID: 5132
Source: Microsoft-Windows-WAS
Version: 7.5
Symbolic Name: WAS_32BIT_MODE_NOT_SUPPORTED_FOR_IIS5_COMPATIBILITY_MODE
Message: Enable32bitAppOnWin64 setting will be ignored because IIS is currently running in IIS5 Compatibility mode.

Resolve

This is a normal condition. No further action is required.

Related Management Information

IIS WAS Configuration

Internet Information Services (IIS) 7.5

Related: