Citrix states in their article: CTX108174

CTX108174 - Hotfix MPM250W009 - For Metaframe Password Manager 2.5

This document was published at: http://support.citrix.com/article/CTX108174

Document ID: CTX108174, Created on: Dec 16, 2005, Updated: Jan 12, 2006

Products: Citrix MetaFrame Password Manager 2.5

Attachment: MPM250W009.msi (2.8 MB)

Hotfix readme name: MPME250W009.HTM
Hotfix package name: MPM250W009.MSI
For: MetaFrame Password Manager, Version 2.5
Replaces: MPM250W001, MPM250W003, MPM250W004, MPM250W005, MPM250W006, MPM250W007, MPM250W008
Date: December, 2005
Languages supported: English (US), German (DE), Spanish (ES), French (FR), Japanese (JA), Italian (IT)
Readme Version: 1.2

Note: You can apply this hotfix to Password Manager 2.5 with or without the Italian language pack installed. For more information and installation instructions for the Italian language pack, see the Italian language pack readme.

Where to Find Documentation

MetaFrame Password Manager includes several documentation files to assist you in your use of the product. The documentation files are available in Adobe Portable Document format (PDF) from the \Documentation folder of the MetaFrame Password Manager CD-ROM. The files are also available from the Citrix Web site at http://www.citrix.com/support. To view, search, and print the documentation, you need Adobe Reader 5.0.5 or later with Search. You can download Adobe Reader for free from the Adobe Web site at http://www.adobe.com/.

Note(s) about this Release

• This hotfix requires Windows Script Host 5.6 or later

Issue(s) Resolved in this Hotfix

Caution! Several items in this hotfix require you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

1. This feature enhancement introduces the ability to log an event in the Event Viewer if an identity verification question is not answered correctly.

To enable this enhancement, select LogEvents in Agent Settings > Event Manager of the Password Manager Console and make sure you select to log all re-authentication events. With this new feature, each failed attempt to answer an identity verification question is logged in the Event Viewer.

[From MPM250W001][#86964]

2. The agent was taking an excessive amount of time to perform application detection routines for Lotus Notes email deletion information windows.

This fix optimizes the detection routines.

[From MPM250W001][#89268]

3. This feature enhancement introduces an additional identity verification option. Identity verification is the mechanism used to authenticate users when they attempt to change their primary password or logon method. Previously, the only identity verification option was for users to answer their verification question. With this feature enhancement, you can give users the following identity verification options:

o A choice between answering their verification question and entering their previous primary password

o Entering their previous primary password only

After you install this hotfix on all computers running the console and the agent, by default, users have a choice between answering their verification question and entering their previous primary password for identity verification. No further action is required.

To give users the previous primary password option only:

Note: This option is not recommended if you use smart card authentication with DPAPI in mixed server operating system environments (environments with two or more Windows operating systems). Data encrypted with DPAPI on one operating system can be decrypted on the same operating system only; therefore, smart card authentication in mixed server operating system environments may fail. If you use smart card authentication and if the Smart card Source For Key Authenticator agent setting is set to Profile/DPAPI, which is the case by default, the Verification Question option must be selected.

A. In the Password Manager Console, select Agent Settings > Authenticator. Clear the new option, Verification Question.

B. Make the modified agent settings available to agents. For information about making agent settings available to agents, see the Password Manager Administrator's Guide.

Note: This hotfix does not update the original product documentation that came with Password Manager, Version 2.5. Therefore, the MetaFrame Password Manager Administrator's Guide and the MetaFrame Password Manager Agent Help do not reflect this feature enhancement.

[From MPM250W003][#96061]

4. URLs to Web applications needed to be case-sensitive. Case-insensitive URLs were not recognized.

With this fix, URLs continue to be case-sensitive by default. However, you also have the option to accept case-insensitive URLs on a per-Web-application basis.

To accept case-insensitive URLs:

A. Define the Web application as usual in the Password Manager Console. Export the Web application to an .ini file and open the .ini file in a text editor. In the .ini file, locate the logon section and add the following entry:

CaseInsensitiveURL=1

B. Save your changes and close the .ini file.

C. Import the modified .ini file to the console and deploy it to the agents.

[From MPM250W004][#76378]

5. In MetaFrame Secure Access Manager, certain CDAs would activate Password Manager, even if the CDAs were not defined.

[From MPM250W004][#81646]

6. Password Manager did not recognize logon windows after initial logon in Jolly Giant QWS3270 emulators. This was caused by a DLL returning a non-standard error code that was ignored by Password Manager.

[From MPM250W004][#84620]

7. Users could cancel the First Time Use wizard by clicking the "x" in the upper right corner.

With this fix, you have the option to remove the "x" button to prevent users from canceling the wizard. To do this:

A. Install this hotfix.

B. On the agent, create the following registry value at HKEY_LOCAL_MACHINE\Software\Citrix\MetaFramePasswordManager\Extensions\SetupManager:

Name: ForceFTU
Type: DWORD
Data: 1

C. Restart the agent.

[From MPM250W004][#87196]

8. Password changes failed to take effect for host applications with
change password screens that had only one entry field. This was caused by the way in which the logic that identifies the Change Password window was implemented.

[From MPM250W004][#87503]

9. Password policies were not working for host applications. This was caused by the incorrect way the agent was reading password policies from the host application's configuration file.

[From MPM250W004][#91653]

10. Password Manager now offers support for WinHLLAPI-compliant terminal emulators, such as PassportWinHLLAPI and Passport. To add support for such terminal emulators, add the following entry to their respective section in the mfrmlist.ini file:

LoadWinHllapi=1

Note: Always make certain that similar or conflicting emulator definitions are not in the mfrmlist.ini file on the agent. For example, a ZephyrPC entry will keep PassportWinHLLAPI from functioning properly.

[From MPM250W004][#92812]

11. The agent submitted credentials to the host emulator screen even if you clicked Cancel on the logon screen. This was caused by a timing issue within the agent.

With this fix, an additional check is performed just before credentials are submitted.

[From MPM250W004][#93475]

12. The ForceCredStorage agent setting was enforced for Windows and Web applications, but not for host emulator applications. The ForceCredStorage setting, when enabled, does not give users the option to decline storing their credentials.

With this hotfix, the setting is enforced for Windows, Web, and host emulator applications.

[From MPM250W004][#96655]

13. This fix introduces support for running the agent on Windows NT 4.0 Terminal Server Edition.

[From MPM250W006][#90805]

14. While accessing the local credential store, the agent would deadlock on occasion and did not recognize applications launched subsequently.

[From MPM250W006][#92147]

15. This hotfix introduces an enhancement to the password sharing feature. Password sharing lets you use the same credentials for multiple applications by placing the applications in Password Sharing Groups. With this feature enhancement, you can configure multiple credential sets for each application in a Password Sharing Group. Only the first set you configure is shared with the other applications in the same group. Credential sets for the same application you configure later are not shared until all credential sets for that application are first deleted.

[From MPM250W005][#97400, 103821]

16. When a power change event, such as Stand by or Hibernate, occurred, the agent no longer controlled browser windows that were opened before the event occurred. This happened because, upon receipt of a power change notification from the operating system, Password Manager restarted the browser helper object, which handles browser windows, but dropped browser windows that were opened before the power change notification was received.

[From MPM250W006][#98745]

17. In deployments consisting of Presentation Server 3.0 and Password Manager 2.5, the "CLIENTNAME" environment variable did not appear when launching published application.

[From MPM250W006][#100641]

18. Even with advanced logging enabled, Japanese characters were not logged. This occurred because Japanese characters were treated as ANSI characters.

After installing this hotfix, you must delete or rename the existing log file so that a new log file is saved in UTF-8 format, which recognizes Asian language characters.

[From MPM250W006][#101161]

19. If the User Workspace>MetaFrame Password Manager>Do not use MetaFrame Password Manager policy was enabled and more than nine users connected to a server, enforcement of that policy failed.

[From MPM250W006][#100743]

20. Although the console supports application- and form-level customization of form auto-submit configurations for Web applications, the agent honored only application-level configurations, ignoring form-level custom configurations. Therefore, it was not possible to enforce form-level auto-submit behavior if it was different from the one configured at the application level.

[From MPM250W006][#100786]

21. The agent experienced a fatal error when reading an application definition if the length of the application path exceeded 1024 characters.

With this hotfix, the agent no longer experiences a fatal error but ignores the offending application.

[From MPM250W006][#101700]

22. Password Manager created the registry keys egoStore_SyncState, TimeStampLow and TimeStampHigh in the following locations:

o HKEY_CURRENT_USER\Software\Citrix\MetaFrame Password Manager

o HKEY_USERS\.DEFAULT\Software\Citrix\MetaFrame Password Manager

The entry at HKEY_USERS\.DEFAULT\Software\Citrix\MetaFrame Password Manager was made in error. This fix corrects the issue by not recreating the incorrect registry entries after you delete them manually.

[From MPM250W006][#102117]

23. A security issue was identified that potentially allowed users to bypass the ‘reveal passwords’ policy. This occurred because of the way Password Manager displayed stored passwords. This fix modifies the way that passwords are displayed to prevent this problem from occurring. For more details, see the security bulletin at: http://support.citrix.com/kb/entry.jspa?externalID=CTX105800.

[From MPM250W006][#102123]

24. Loading Web pages in Internet Explorer caused Password Manager to access files in the user profiles directory, unnecessarily utilizing the file server and often causing heavy server utilization. This occurred because Password Manager re-parsed the application definition file, located in the user profiles directory, every time it accesses a Web page.

This fix corrects the issue so that the definition file is cached and only read at startup and when its contents change.

[From MPM250W006][#103826]

25. First-time users of Password Manager 2.5 in a Terminal Server environment could not configure the Identity Verification Question. This occurred because the following registry key was incorrectly created during installation:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Citrix\MetaFrame Password Manager. For this fix to correct the issue, you must remove this registry key.

[From MPM250W006][#104070]

26. Choosing the Repair option for Password Manager Agent 2.5 from the Add/Remove Programs Control Panel overwrote the newer binaries installed by hotfixes for the product. This invalidated the hotfixes.

[From MPM250W006][#106843]

27. Earlier hotfixes for Password Manager that combined agent and console components displayed a message stating that the console was not installed if the installer could not find the console installed on the computer on which you were installing the hotfix. The message is now logged as an Application event in the Microsoft Management Console.

[From MPM250W006][#106844]

28. This is a usability enhancement aimed at
simplifying the user experience: The string "Formerly Generic Question" was removed from the Default Verification Question. The question now reads as follows:

"What is your identity verification phrase?"

[From MPM250W006][#107819]

29. This is another usability enhancement aimed at simplifying the user experience: After applying Hotfix MPM250W004, disabling the Verification Question option from the console worked only for users who had not previously configured their verification question. Previously configured users continued to be able to recover their credentials by way of the verification question. This behavior may have been confusing to administrators.

This fix introduces a code change so that disabling the Verification Question option takes effect for all users.

[From MPM250W006][#109431]

30. You could not use the previous password to authenticate if that password was blank. The issue occurred because of a requirement that the previous password not be blank; the OK button in the dialog box was disabled if the password text box was left blank. This fix removes the requirement that the previous password not be blank and adds support for using blank passwords as previous passwords; the OK button is enabled even if the password text box is left blank.

[From MPM250W007][#104473]

31. When switching between console and console RDP sessions, users were prompted for their identity verification question. This fix corrects the issue in that Password Manager now prompts users for their password if the operating system of the computer running the agent cannot provide it.

[From MPM250W007][#105025]

32. Password Manager failed to recognize certain Web sites, such as http://www.my_company.com. The issue occurred because Password Manager could not parse input fields with the same name.

[From MPM250W007][#115502]

33. After logging on to an undefined Web application and answering the agent's question, “Would you like MetaFrame Password Manager to remember your logon information for this web application?” with Never, you were unable to manually invoke the agent to work with the application from the tray icon. The issue occurred on systems where Hotfix MPM250W006 was installed.

[From MPM250W007][#115503]

34. Password Manager did not handle console applications, such as cmd.exe. The issue occurred because Password Manager could not hook into console applications and, therefore, missed events such as window creation events on such applications.

This fix corrects the issue by introducing an additional hook that is able to catch such events and thus handle console applications.

[From MPM250W007][#115569]

35. For network logon dialogs that do not show unique Server Name fields, Password Manager was not able to distinguish the difference between different network logon dialogs connecting to different servers. The issue occurred because Password Manager required the Server Name field to be unique for different server connections. Additionally, the credential matching code contained a logic error that prevented it from distinguishing between undefined applications (by the administrator) and unconfigured applications (by the user).

[From MPM250W007][#116067]

36. Under rare circumstances, a user was prompted for re-authentication for each detected application; yet after each re-authentication event, Password Manager would not fill in the credentials and continue to prompt the user to re-authenticate at each subsequent logon attempt. The issue occurred because of timing issues related to the re-authentication code path that may have resulted in continuous re-authentication failures on some machines.

[From MPM250W007][#116068]

37. Password Manager did not work properly with certain Web pages. The issue occurred when the Web page contained forms with Submit image buttons whose source (SRC) property contained variable session IDs. Password Manager could not process variable session IDs. The problem was caused by the Web page's image submit button. The SRC property of the IMG button contains a session id that changes all the time. But Password Manager can recognize only one session id during which the Web page is defined.

This fix corrects the issue by ignoring the SRC property and using a sub-string match instead.

[From MPM250W007][#117334]

38. A number of text elements in the agent's user interface were modified to be more user friendly.

[From MPM250W007][#118720]

39. During each synchronization interval Password Manager took focus from running applications. The issue was caused by a hidden dialog created by the process that was running with a FOREGROUND property set.

This fix corrects the issue by removing the FOREGROUND property from the hidden dialog.

[From MPM250W008][#99949]

40. The identity verification and previous primary password dialog boxes did not consistently take focus; instead they were covered by the published application that triggered them. This was confusing to users.

This fix corrects the issue by ensuring that the identity verification dialog box hides the application's logon window upon launch until the identity verification process is complete. At that time, the application's logon window is revealed.

[From MPM250W008][#104474]

41. On occasion, the application form was not automatically submitted after answering the identity verification question even if the auto-submit feature was enabled. The issue occurred if the submit credential button of a 32-bit Windows application's logon window was assigned a control ID other than 1 and the OK control in the application form was not mapped to the submit credential button. The issue occurred because Password Manager, by default, activated button control ID 1.

This fix corrects the issue as follows:

• If the OK control is not assigned in the application form, Password Manager uses a virtual Enter key rather than a virtual button click to submit credentials.

• If the OK control is assigned, Password Manager uses that control ID to submit credentials via a virtual button click.

[From MPM250W008][#104487]

42. This fix adds support for a new WinHLLAPI initialization requirement. Password Manager did not work with WinHLLAPI-compliant host emulators that require re-initializing of the HLLAPI dll at the time the host application launches. The issue occurred because Password Manager initialized HLLAPI dlls when the agent started up, not when the host application was launched.

To enable WinHLLAPI re-initialization when the host application is launched:

A. Define the host application as a Windows application.

B. For that Windows application, manually add the following field "NotifySSOMHO=1" to the application definition.

C. Define the host application as usual.

D. Deploy both the Windows definition and the host definition to the sync point.

E. On the agent, in the mfrmlist.ini file located in the agent's Programs Files directory, add the following field "LoadWinHllapi=1" to the HLLAPI definition.

F. Restart the agent. />

[From MPM250W008][#110030]

43. On occasion, user input and credential submission were mixed if users were typing while auto-submission of credentials was in progress; as a result, authentication failed.

This fix corrects the issue by ensuring that the credential field is parsed of unrelated user input before credentials are submitted.

[From MPM250W008][#110221]

44. On occasion, the carriage return was not delivered to the application's logon window when the identity verification window was used to confirm credentials and the auto-submit feature was set to use a virtual ENTER key to submit user credentials. As a result, user intervention was necessary to submit the credentials. The issue occurred when the application's logon window failed to receive keyboard focus at the time the carriage return was delivered.

This fix corrects the issue by ensuring that the application's logon window gets keyboard focus before delivering the carriage return or logon/change password credential information.

[From MPM250W008][#112669]

45. This feature enhancement allows administrators and users to specify whether or not to launch the agent upon logon outside Presentation Server environments. The previous default behavior was for the agent to automatically launch at logon time.

To allow users to prevent the agent from starting up upon logon, you must set the following registry entry on the agent: HKEY_LOCAL_MACHINE\Software\Citrix\MetaFrame Password Manager\Shell
Name: AllowUserDisableAgentStartup
Type: DWORD
Data: 1 (0 will disable this option for users)

Assuming that the administrator has allowed users to prevent the agent from starting up upon logon as described above, users may do so by creating either one of the following new registry values: HKEY_CURRENT_USER\Software\Citrix\Password Manager\Local Settings
Name: RunAgent
Type: DWORD
Data: 0 (all other values enable the agent startup at logon)

HKEY_LOCAL_MACHINE\Software\Citrix\MetaFrame Password Manager\Shell
Name: RunAgent
Type: DWORD
Data: 0 (all other values will enable the agent startup at logon)

Note : If both RunAgent values above are present in the registry of a particular user, the value in HKEY_CURRENT_USER takes precedence over the value in HKEY_LOCAL_MACHINE.

[From MPM250W008][#112682]

46. Note: This fix applies only to agents running on Microsoft Windows XP Professional and Windows Server 2003.

On occasion, users were unexpectedly prompted to re-authenticate after unlocking their workstations. The re-authentication prompt was triggered by the re-authentication timer. The timer is set to prompt users for re-authentication every eight hours unless the user re-authenticates sooner, at which time the timer is reset. The issue occurred because the process of unlocking the workstation was not communicated to the agent as authentication; as a result, the timer was not reset.

This fix corrects the issue so that the timer is reset when the user unlocks the workstation and does not prompt for re-authentication sooner than eight hours after the most recent re-authentication.

[From MPM250W008][#116286]

47. If an administrator decided to make the applist.ini a read-only file so that users could not change it, Password Manager failed to properly merge the file with the entlist.ini file to create the aelist.ini (application definition) file. As a result, all entries in entlist.ini were missing from aelist.ini.

[From MPM250W008][#116377]

48. This feature enhancement adds an option to the Agent setting configuration page that allows administrators to exclude the default applications specified in the applist.ini file from the applications handled by Password Manager. This added option is available under Agent Settings > AccessManager > EnableDefaultApplications.

Note: To maintain maximum performance, any time you change the EnableDefaultApplications setting, you must restart the agent for the changes to take effect.

[From MPM250W008][#117168]

49. On the Change Password wizard window, trying more than once to change the password for an application by clicking Back in effect overrode the current password after the first attempt, even if you eventually cancelled the change password request. Using the automatically generated password feature led to a permanent change of the current password without the application's consent; as a result, subsequent logon attempts were bound to fail.

This fix corrects the issue by allowing users an unlimited number of cancellations and retries.

[From MPM250W008][#120827]

50. On computers running German language Windows operating systems, a password policy to exclude Umlaut characters, such as Ä, Ö, Ü, ä, ö, ü, and ß did not work. The issue was caused by missing logic in the password policy to remove the excluded characters from the pool of available password characters; as a result, the password validation check on the excluded characters would erroneously succeed.

[From MPM250W008][#120854]

51. Password Manager may have stopped handling a host window after the user clicked Cancel in the Logon Chooser dialog box. The issue occurred because the Cancel button click was not properly communicated to the agent, effectively blocking its operation for that window.

[From MPM250W008][#121794]

52. If the minimum and maximum lengths specified for passwords were identical, Password Manager ignored the values for "maximum numeric characters allowed" and "maximum special characters allowed." The issue occurred because the minimum number of generated numeric and special characters for the password was not computed correctly.

[From MPM250W008][#121814]

53. The focus of the previous password credential recovery dialog box was on the Cancel button rather than the Previous Password text field.

This fix corrects the issue by putting the focus in the Previous Password text field.

[From MPM250W008][#121815]

54. Password Manager may have stopped handling a host window after the user clicked Cancel on one of the Change Password wizard pages. The issue occurred because the Cancel button click was not properly communicated to the agent, effectively blocking its operation for that window.

[From MPM250W008][#121817]

55. When multiple Web forms were defined, the agent configuration wizard displayed a combo box of a defined Web form as a text box. The issue occurred because of a code error in the new application wizard initialization code.

[From MPM250W008][#122202]

56. Quickly and repeatedly clicking Refresh in the Logon Manager dialog box prevented Password Manager from handling defined Web applications. The issue occurred if the refresh requests happened while the application definition file was still being created.

[From MPM250W008][#122714]

57. Attempting to silently install a hotfix more than once resulted in the hotfix being uninstalled. The issue was caused by a code error in the hotfix install design.

[From MPM250W008][#123634]

58. When you removed an adminoverride object for a user from the
console, the settings it provided were not entirely removed from the user's side.

[From MPM250W009][#105034]

59. On occasion, host emulator screen detection failed. The issue was caused by an error within the host emulator's screen matching code.

This fix corrects the screen matching code.

[From MPM250W009][#115656]

60. If you had Hotfix MPM250W008 installed and configured the agent to be disabled at startup and to delete Password Manager files from the user profile at shutdown, the memory mapping (.mmf) file was not deleted. The issue occurred because the agent could not check for the DeleteOnShutdown setting if it was configured to exit on startup.

With this fix, the .mmf file is deleted at shutdown.

[From MPM250W009][#125654]

61. Client CPU consumption increased unexpectedly for 30 to 60 seconds, leaving the client unresponsive during that time. The issue occurred when Password Manager was attempting to detect the fields on a Web page that contained a large number of forms with input fields.

This fix addresses the issue by introducing an AllowUnknown setting in the Password Manager Console. The setting lets you control whether or not users can add their own application definitions in addition to those configured by an administrator. With the AllowUnknown setting enabled, the agent no longer attempts to detect the credentials fields of a Web page unless the page is explicitly defined as a Web application in the console.

To enable this setting after applying this fix:

A. Shut down the agent.

B. Open the console.

C. Select Agent Settings > AccessManager, select the AllowUnknown option, and select Support agent-listed applications only.

D. Deploy the updated Agent Settings.

E. Start the agent.

Note: If you update the Agent settings while the agent is running, you must shut down and restart the agent.

[From MPM250W009][#126054]

62. If the Password Manager Console was installed on systems running Version 2.0 of the .NET Framework, the console may have behaved erratically, producing errors at various stages of operation. The issue occurred because the console only supports Versions 1.0 and 1.1 of the .NET Framework.

With this fix, the console prompts you to install the required version of .NET Framework rather than behaving erratically.

[From MPM250W009][#127190]

Installation Instructions

Note: This hotfix is packaged with Microsoft Windows Installer. You can deploy the hotfix package to a group of servers using Microsoft Active Directory Group Policy Object or using Citrix Installation Manager. For more information, see the Citrix Server Administrator’s Guide or the Citrix Installation Manager Administrator’s Guide.

1.

Download the hotfix package from the Hotfixes and Service Packs page of the Citrix Web site at http://www.citrix.com.

2.

Copy the hotfix package to an empty directory on the hard drive of the Password Manager Console and/or Agent.

3.

Close all applications.

4.

Run the executable.

5.

Shut down and restart the server.

Note: To install this hotfix silently, use the /q option after the executable. For example:

msiexec /I MPM250W009.MSI /q

Using the /q option without additional options automatically restarts the server.
For additional information about msiexec, see the Microsoft Web site at http://www.microsoft.com/. Search on keyword msiexec.

Uninstallation Instructions

1.

From the Start menu, select Setting > Control Panel.

2.

In Control Panel, double-click Add/Remove Programs.

3.

Highlight the hotfix you want to uninstall and click Remove.

4.

Follow the directions on-screen.

File(s) Updated

Agent.mst

3,584

01/24/2005

10:39a

appmgr.dll

323,584

11/17/2005

02:29p

appmgr.vrs

184,320

11/17/2005

02:36p

EventMgr.dll

122,880

11/17/2005

02:34p

Filesync.dll

102,400

11/17/2005

02:33p

LicenseAdmin.exe

163,840

11/17/2005

02:35p

LicenseAdmin.exe.config

165

11/17/2005

02:22p

LicenseCommon.dll

126,976

11/17/2005

02:35p

LicenseDB.dll

73,728

11/17/2005

02:35p

MPMUpdateCachedMSI.vbs

3,044

03/03/2005

05:18p

MPMUpdateRegistryXML.vbs

674

03/03/2005

05:19p

Registry.xml

29,879

08/18/2005

04:33p

resource.dll

65,536

11/17/2005

02:29p

setupmgr.dll

106,496

11/17/2005

02:30p

setupMgr.vrs

57,344

11/17/2005

02:36p

SSOAdmin.exe

5,427,200

11/17/2005

02:36p

SSOAdmin.exe.config

165

11/17/2005

02:22p

ssobho.exe

245,760

12/14/2005

01:45p

SSOGina.dll

102,400

11/17/2005

02:31p

ssohook.dll

23,552

11/17/2005

02:28p

ssoLauncher.exe

47,616

11/17/2005

02:25p

ssomho.exe

217,088

11/17/2005

02:27p

ssoShell.exe

245,760

12/13/2005

02:08p

ssoShell.vrs />

258,048

12/13/2005

02:12p

support.dll

110,592

11/17/2005

02:25p

syncmgr.dll

172,032

11/17/2005

02:33p

WindowsEvent.dll

118,784

11/17/2005

02:34p

Copyright © 2005 Citrix Systems, Inc. All rights reserved.
Citrix, MetaFrame, and MetaFrame XP are registered trademarks, and Citrix Presentation Server is a trademark of Citrix Systems, Inc. in the United States and other countries.
All other trademarks and registered trademarks are the property of their respective owners.