Summary
Citrix Presentation Server 4.0 supports the synchronization of USB-tethered PDAs running Microsoft Windows that use ActiveSync as the synchronization agent. This document describes how to configure ActiveSync for PDA synchronization.
CTX114161 - ActiveSync 4.5 and Windows Mobile 5 with Presentation Server 4.5 Hotfix Rollup Pack 01
Important: Verify which versions of ActiveSync are supported by the PDA.
ActiveSync 4.0 and later are not supported on the 32-bit version of Presentation Server 4.0. ActiveSync 4.0 and later contain programmatic changes that render these versions of ActiveSync incompatible with the 32-bit version of Presentation Server 4.0. ActiveSync 4.0 is supported on the 64-bit version of Presentation Server 4.0. See CTX105744 - Readme for Citrix Presentation Server 4.0 for Microsoft Windows Server 2003 x64 Edition to integrate ActiveSync 4.0 with Presentation Server 4.0 for Microsoft Windows Server 2003 x64 Edition. Please note that the procedures in CTX105744 will only work on the 64-bit version of Presentation Server and do not enable support for ActiveSync 4.0 and later on the 32-bit version of Presentation Server.
Caution! Internal testing has shown that Windows Mobile 5 is currently not compatible with the PDASync feature on any version of Presentation Server 4.0. Citrix is currently investigating this issue.
This article will be updated when any new developments occur.
Notes:
- Do not plug PDAs into the server console while ICA sessions are connected. Although PDA users in ICA sessions are isolated from each other, they might have access to the PDA on the server console. In addition, if one unplugs the PDA from the server console, all the PDAs in ICA sessions are disconnected. If the PDA Devices policy rule is disabled (by default), or there is no PDA attached to the client device, a session user might access a PDA physically connected to the server.
- Symbian operating system-based PDAs and Blackberry PDAs are not supported.
- ActiveSync does not need to be installed on every client.
- A device driver for the PDA must be installed on the local client workstation so that the client’s operating system can recognize the PDA device. It may be recommended that the driver version be verified to coincide with that of the MetaFrame Server.
- ActiveSync must not be running on the server console when ICA client users with access to ActiveSync connect.
- ActiveSync 3.x is not supported from the server console. It is only supported through published applications.
- ActiveSync 4 is not supported on Citrix Presentation Server 4.0 for 32-bit Windows.
- No version of ActiveSync is supported on Citrix MetaFrame Presentation Server 3.0 or earlier.
Enabling PDA Synchronization
- following hotfixes or their current equivalents add support of the PDA Synchronization feature to Presentation Server, Advanced Edition:
- Hotfix PSE400W2K012, or its equivalent, for Presentation Server 4.0 for Windows 2000.
Hotfix PSE400W2K3012, or its equivalent, for Presentation Server 4.0 for Windows 2003.
Step by Step Integration
Citrix Technical Support confirmed this article with the following set-up:
• Server: Windows 32-bit 2003 Service Pack 1 with Presentation Server 4.0 and Hotfix Rollup Pack 01
• Client: Windows 32-bit 2003 Service Pack 1 with Presentation Server 4.0 and Hotfix Rollup Pack 01
• ActiveSync version 3.8 on the Server and Client
Server Side Configuration for Presentation Server 4.0 for 32-bit Windows
Note: See CTX105744 - Readme for Citrix Presentation Server 4.0 for Microsoft Windows Server 2003 x64 Edition to integrate ActiveSync 4.0 with Presentation Server 4.0 for Microsoft Windows Server 2003 x64 Edition.
Recommended Installation Process:
- Install Microsoft Office 2003/2002/2000 and make sure to include Outlook. It is important to ensure this step is completed first.
- If applicable, install Office Service packs.
- Open the properties of a policy, within the Citrix Management Console.
- Enable the rule Client Devices > Resources > PDA Devices > Turn on automatic virtual COM port mapping.
- Disable the rule Client Devices > Resources > Ports > Turn off COM ports (or set it to “Not Configured”).
- Ensure the Policy is applied to an appropriate filter:
- Publish both Outlook.exe and WCESMgr.exe as published applications.
- To make ActiveSync available as a published application, specify Wcesmgr.exe, not Wcescomm.exe, as the application to be launched. Wcescomm.exe is the notification area process.
Note: ActiveSync is not a multi-user or Terminal Services aware application, but Presentation Server 4.0 utilizes the new virtual IP feature in combination with additional program enhancements to create Terminal Services compatibility. Although virtual IP is used to enable PDA synchronization with ActiveSync, no explicit virtual IP configurations are required by an administrator for PDA synchronization to function.
Client Side Configuration
Client with USB ports such as Win9x, XP Pro
Tethered USB cable support for PDA devices
- If already using ActiveSync with the PDA device on the client workstation, ensure to backup all data before continuing to step 11. Citrix Technical Support did not have a client machine with ActiveSync. When adding ActiveSync 3.8, the following steps were chosen. Perform a hardware reset on the PDA device. In most cases the plug-n-play device driver is sufficient in the client OS, but it is recommend to fully install ActiveSync 3.x on the client OS in addition to installing the plug-n-play device driver. Note: This is only needed to obtain the plug-n-play device driver. After this process is completed you can uninstall ActiveSync 3.x from the client OS.
On the Select Synchronization Settings screen, the defaults were chosen.
Continue choosing Next, then Finish.
ActiveSync on the Client should Look for Changes:
ActiveSync on the Client should Connect:
- Wcescomm.exe is the notification area process. If the PDA is plugged into the USB port on the client, ActiveSync may synchronize to the device. WCESMgr.exe is also listed as a running process. To prevent this from occurring on a permanent basis, on the client device, do the following (else manually kill the processes for initial set-up and troubleshooting):
a. Using the System Configuration Utility (msconfig), remove the ActiveSync options from the Startup tab.
b. To prevent ActiveSync from recreating the startup entries, delete the following registry value:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\
Run: H/PC Connection Agent
The above processes, on the client machine, have been terminated.
- Using Program Neighborhood Classic, Program Neighborhood Agent, or Web Interface version 9.x or later, connect to the published Outlook. If applicable, configure the Outlook Profile. Then connect to the published ActiveSync. Ensure Outlook.exe is launched on the same system as WCESMgr.exe. ActiveSync makes calls directly to functions within Outlook. If Outlook load balances to a system other than ActiveSync, ActiveSync fails to make these calls. CTX159159 – Troubleshooting and Explaining Session Sharing.
The Server, inside the ICA session, asked to set up ActiveSync. The following options were chosen:
On the Select Synchronization Settings screen, the defaults were chosen.
Continue choosing Next, then Finish.
ActiveSync, running inside the ICA session should Look for Changes:
ActiveSync inside the ICA session should Connect:
Citrix Technical Support chose:
- Ensure that the WCESMgr.exe and WCESCOMM.exe processes are not running on the server console. If needed, run MSCONFIG.exe and remove these processes from the Startup tab.
Verify the processes are not running.
- For Web Interface connections, configure the PDA Sync settings within the Web Interface site. Edit the settings for Manage client connection settings and select the options for Enable PDA sync and Allow user to customize PDA sync.
- When running ActiveSync as a non-seamless, published application, if you close the main ActiveSync window, you cannot completely log off the ICA session until the PDA is removed. Because the PDA remains in the USB cradle, the Wcescomm.exe process, on the server, is still active, and although one may not see the notification area icon, one cannot close the session until this process is closed.
Note: After logging off, the processes are still running inside the session.
The Client Side Connection Center shows the session as active.
After removing the PDA from the Client Side cradle, the session ends.
The Client Side Connection Center shows the session has ended.
Troubleshooting PDA Synchronization with ActiveSync
- ActiveSync 4.0 and later are not supported on the 32-bit version of Presentation Server 4.0. ActiveSync 4.0 and later contain programmatic changes that render these versions of ActiveSync incompatible with the 32-bit version of Presentation Server 4.0. ActiveSync 4.0 is supported on the 64-bit version of Presentation Server 4.0. See CTX105744 - Readme for Citrix Presentation Server 4.0 for Microsoft Windows Server 2003 x64 Edition to integrate ActiveSync 4.0 with Presentation Server 4.0 for Microsoft Windows Server 2003 x64 Edition. Please note that the procedures in CTX105744 will only work on the 64-bit version of Presentation Server and do not enable support for ActiveSync 4.0 and later on the 32-bit version of Presentation Server.
- PDA synchronization malfunctions when Presentation Server is set to Advanced edition. To enable support for PDA synchronization in the Advanced edition, apply Hotfix PSE400W2K3002 for Windows 2003 or PSE400W2K002 for Windows 2000.
- PDA synchronization with ActiveSync malfunctions within a Conferencing Manager session. This is a known issue.
- Do not use the default ActiveSync driver that ships with Windows XP. For optimal performance, install the most recent version of ActiveSync.
Do not isolate ActiveSync. ActiveSync installs a service and isolation environments do not support isolated services, so if ActiveSync is installed in an isolation environment, it fails. Isolation environments can be configured on Presentation Server to isolate other applications without impact on ActiveSync. CTX106633 - Microsoft ActiveSync Fails When Installed Into an Isolation Environment
- Disable COM port connections through ActiveSync. If you modify the connection settings within ActiveSync to allow COM port connections and then disconnect and reconnect the PDA in rapid succession, the PDA connects, but you cannot start Wcesmgr.exe until the currently running Wcesmgr.exe terminates or a one minute time-out occurs. This is a third party issue with ActiveSync and can occur on a console outside of an ICA session as well.
To Disable COM Port Connections for All Users
Modify the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services
by specifying :
• Value: REG_DWORD:ConnectTypesAllowed
Settings:
o Allow serial cable or infrared connection to a COM port: 0x00000002
o Allow network (Ethernet) and Remote Access Service (RAS) server connection with the desktop computer: 0x00000004
o Allow USB connection with the desktop computer: 0x00000008
The per-user key is created the first time ActiveSync is used by the respective user, at which point all key values are populated using the defaults in HKEY_LOCAL_MACHINE.
Note: Users can enable ActiveSync COM port connections again by modifying the options in Connection Settings.
More Information
CTX106633 - Microsoft ActiveSync Fails When Installed Into an Isolation Environment
CTX106319 - MetaFrame Presentation Server 4.0 Administrator's Guide, page 299
CTX107059 - Advanced Concepts Guide , pages 123, 135-137
CTX106472 - Web Interface Administrator's Guide, pages 16, 17, 29, 62, 84, 94, 99
CTX106223 - Client for 32-bit Windows Administrator's Guide - Version 9.0, pages13, 53
