Microsoft Office 2010 Known Issues with Citrix XenApp

Summary

This article contains information about issues and their known workarounds for Office 2010 products that users must be aware of in conjunction with the following Citrix products:

  •  XenApp 4.5
  • XenApp 5.0
  • XenApp 6.0

Note: Citrix Systems is committed to ensure compatibility with the latest Microsoft products.

Non-Support Issues

  • WISP 2007 does not support SharePoint 2010 (223873).
  • XenApp 5 and 4.5 Installation Managers do not support Office 2010.
    Workaround
    : Citrix recommends using Application Streaming feature of XenApp 5 and 4.5 to install Office 2010 to your XenApp server. Also the IM of XenApp 6 does support Office 2010 (227705).

Workaround for Installation Manager on XenApp on 2003

Use a .wfs script for an unattended installation. Run source location\setup.exe, and then add the command line /adminfile “source location\adminfile.msp”. Once this is created, edit the script to add the lines to the section from where the information was removed:
ConfigActions=T, Run UnInstall
[Run UnInstall]
ShellExecute=source location\setup.exe,T,open,%TEMPDIR%,/config “source location\uninstall.xml” /uninstall ProPlus,NORMAL

Issues

The following error message is displayed after starting Offline Word (234902):

Insufficient memory, Windows Word cannot display the requested font

This issue occurs because fonts are not downloaded properly.

Impacts – This issue impacts XenApp 6.

Workaround: Issue happens initially when users start the applications, but as the applications are started (multiple launches) then issue becomes less frequent.

The following issues are to be addressed in next release of Offline client Streaming

  • App icon resolution in Citrix offline applications container is corrupted for Office 2010 applications in laptops. (234641). This issue impacts XenApp 6.
  • Opening local document with the stream to client application through offline access crashes the application, intermittent. (234653). This issue impacts XenApp 6.
  • Outlook 2010 Attachment preview of word document is not displayed properly, Seamless. (233642). This issue impacts XenApp 5 and 6.

KMS configuration using Provisioning Services

Introduction

The purpose of this document is to help an administrator configure Provisioning Services 5.6 SP1 (PVS) target Devices that are using Microsoft Key Management Server (KMS) in the best way to fit their environment. KMS can be configured on a vDisk Image with the help of PVS to apply volume licenses for Microsoft Server 2008, Microsoft Server 2008R2, Windows 7 and Windows Vista, as well as Office 2010.

In PVS the option for KMS can be easily configured while building vDisk’s with the Imaging Wizard; alternatively it can be configured at any time using the Console or MCLI/Powershell command-line interfaces

The Product Administrator’s Guide, Section “Managing Microsoft KMS Volume Licensing” provides further details on KMS configuration for a PVS vDisk.

II. KMS Configuration Scenarios:

The following section outlines the steps to configure KMS in various scenarios to accommodate your deployment environment. Please make sure to read all the scenarios to verify which one best fits your deployment and follow the steps accordingly. It is recommended that you complete all steps in the right order for a successful configuration.

KMS configuration can be done in the following ways depending upon your environment:

Customers can configure KMS for both Windows & Office Customers can configure KMS for Only Windows Customers can configure KMS for Only Office

The Scenario’s below will help you to configure KMS accordingly.

Download the whitepaper here.