[THIN] Re: New MFXP FR2 hotfix

I could really use this too. Users here have been complaining about the
Outlook/IE bug and I've been telling them it's a new security feature.

-----Original Message-----
From: Rowlandson, John [mailto:John.Rowlandson@xxxxxxxxxxxxx]=20
Sent: Friday, September 27, 2002 12:56 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] New MFXP FR2 hotfix





I've just got a private hotfix (#29) for the network printing issues
with FR2. you can now turnoff direct printer mapping :)


It also fixes 15 other things....


Issues Resolved in this Hotfix
------------------------------
 1. Occasionally, if users attempted to log on immediately
    after logging off, they could not print to the
    default autocreated printer because another user's
    printer was set as the default printer.

    Installation of this hotfix resolves the issue.
    [From Hotfix XE102W019][#250207]

 2. In an ICA session, if users clicked on a URL in an
    application such as Microsoft Outlook and a Web browser
    was already open, the session did not navigate to the
    new URL.

    This occurred because a backup registry value used to
    establish DDE communication with the Web browser was
    set incorrectly.

    With this hotfix, the registry value is set correctly
    and the URL will open correctly in a running Web
    browser.
    [From Hotfix XE102W023][#257855]

 3. When disconnecting from an ICA session on certain WBT
    devices, some modules remained active on the WBT
    devices.

    With this hotfix, the modules no longer remain as an
    active session on the WBT devices.
    [From Hotfix XE102W026][#249791]

 4. Users were unable to change window focus by toggling
    the window icons on the taskbar.

    Installation of this hotfix resolves the issue.
    [From Hotfix XE102W026][#253398]

 5. When setting the seamless flag to 0x01 in the
    following registry key, seamless session sharing was
    not being disabled as it should have been:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
    \Citrix\Wfshell\TWI\SeamlessFlags

    A path was not reading or using the registry flag to
    determine whether or not to share the session.

    A modification to the path now disables session sharing
    as intended.
    [From Hotfix XE102W026][#258522]

 6. NOTE: This hotfix item does not apply to the Japanese
    language version of MetaFrame XP 1.0 for Windows 2000.

    When using Microsoft Word 2000, the AutoText ToolTip
    window occasionally disappeared for several seconds.
    Users sometimes noticed the AutoText ToolTip window
    blinking. This occurred when icon request messages
    were sent to both the Word 2000 document window and
    the ToolTip window. The solution is to exclude
    messages that request icon changes in these two
    windows.

    To enable this feature, add the two registry entries
    detailed below.

    A. Open the Registry Editor and navigate to the
       following registry key:

       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
       \Control\Citrix\wfshell\TWI

    B. From the Edit menu, choose Add Key and add a key
       with the following information:

       Key Name: OpusApp

       Note that you do not need to enter a value in the
       Class text box.

    C. Open the OpusApp key you just created.

    D. From the Edit menu, choose Add Value and add a
       value with the following information:

       Value Name: ClassName
       Data Type: REG_SZ
       String: OpusApp

    E. From the Edit menu, choose Add Value again and add
       a value with the following information:

       Value Name: Type
       Data Type: REG_DWORD
       Data: 00000100
       Radix: Hex

    F. Navigate back to the TWI registry key:

       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
       \Control\Citrix\wfshell\TWI

    G. From the Edit menu, choose Add Key and add a key
       with the following information:

       Key Name: _WwM

       NOTE: This Key Name is case-sensitive. To type this
       Key Name, you must type an underscore, an uppercase
       "W," a lowercase "w," and then an uppercase "M."

    H. Open the _WwM key you just created.

    I. From the Edit menu, choose Add Value and add a value
       with the following information:

       Value Name: ClassName
       Data Type: REG_SZ
       String: _WwM

       NOTE: This Key Name is case-sensitive. To type this
       Key Name, you must type an underscore, an uppercase
       "W," a lowercase "w," and then an uppercase "M."

    J. Choose Add Value again and add a value with the
       following information:

       Value Name: Type
       Data Type: REG_DWORD
       Data: 00000100
       Radix: Hex

    With this change, the AutoText ToolTip and the
    insertion-point cursor displayed in Microsoft Word
    2000 no longer blink.
    [From Hotfix XE102W026][#242516, 253407]

 7. Sometimes Microsoft Terminal Server experienced a
    fatal system error. This occurred when some portion
    of the MetaFrame XP data store became corrupt and
    a Citrix Dll received incorrect data. The Citrix
    Dll could not process the incorrect data.

    The program has been modified so that even if the
    MetaFrame data store becomes corrupt, the Microsoft
    Terminal Service will remain running.
    [From Hotfix XE102W029][#258382]

 8. Users were sometimes asked if they wanted to make
    Internet Explorer their default browser the first
    time they launched it in an ICA session. If the users
    clicked "Yes," content redirection did not always
    work in that session.

    This problem occurred because the code in a .dll
    did not change the following registry value as was
    intended:

    HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer
    \Main
    Value Name: Check_Associations
    Value Type: REG_SZ
    Value: no

    The code has been moved to an executable and the
    registry value is now always changed. Users are no
    longer asked if they want to make Internet Explorer
    their default browser and content redirection works
    properly.
    [From Hotfix XE102W029][#43971]

 9. Printing to an ICA Client device's networked printer
    through an ICA session was sometimes slower in
    Feature Release 2 than in Feature Release 1. This
    occurred when the Feature Release 2 server and the
    ICA Client were separated by a wide area network
    (WAN) and the networked printer was on the client
    side of the network.

    Another problem occurred when the Feature Release 2
    server and the ICA Client device were on two separate
    networks and both networks had a networked printer with
    the same name. Print jobs that intended to be printed
    on the networked printer on the client side were
    instead sent to the networked printer on the Feature
    Release 2 server network instead.

    When a Feature Release 2 server is separated from the
    ICA Client by a wide area network (WAN) and the
    networked printer is on the ICA Client side of the
    network, printing is slower when the server connects
    directly to the networked printer, rather than when
    a Feature Release 2 server creates a client print
    queue for the networked printer. This occurs in the
    first example above because print data is sent using
    Microsoft's SMB protocol. In the second example, print
    data is sent using Citrix' ICA protocol, which offers
    data reduction.

    The hotfix introduces a registry switch so that you
    can toggle which functionality you want - direct
    connection to network printers from a Feature Release
    2 server or the network printers created as client
    printers that print through the ICA Client device.

    WARNING! 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.

    Navigate to the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
    \Citrix\ClientPrinterAutoCreate

    Value Name: fCreateNetworkPrinter
    Value Type: DWORD
    Value: 1 (to have network printers created as client
              printers)
    Value: 0 (to retain the Feature Release 2 behavior)

    With this feature enabled, network printers are
    created as client printers in the ICA session.
    [From Hotfix XE102W029][#258358]

10. When logging on from an ICA Client that has networked
    printers, a Dr. Watson sometimes occurred when
    autocreating the client printers. This occurred
    because an executable file was not checking for a
    null pointer.

    The executable file has been updated so it will check
    for the null pointer and ICA Clients with networked
    printers can logon to an ICA session without error.
    [From Hotfix XE102W029][#43913]

11. If an ICA Client device has printers whose print
    drivers are not approved on the server, an error
    event is sent to the server's application event log.
    The following message appears by the ICA Client device:

    "Printer Creation."
    "One or more printers could not be created due to a
    driver that has not been approved for use on this
    server. Please contact your system administrator."

    The program has been modified so the error message
    no longer appears.
    [From Hotfix XE102W029][#44092, #42983]

12. If a user in an ICA session had client printers
    created with the Universal Print Driver, the user
    could not print to those printers after reconnecting
    to the ICA session.

    When reconnecting, the server negotiates with the
    client about using the printers created with the
    Universal Print Driver. This negotiation did not
    take place.

    This hotfix updates the server's ability to negotiate
    print capabilities with the client when reconnecting.
    [From Hotfix XE102W029][#258138]

13. If a user reconnected to an ICA session from a client
    device that was not the one used for the original
    connection, the printers on the new client device did
    not get autocreated.

    Now if the client device used to reconnect to an ICA
    session is different from the one used for the
    original connection, printer autocreation will occur.
    If this feature is on when a user disconnects, all
    print jobs and printers are deleted. When the user
    reconnects, the client printers are autocreated.

    NOTE: The program does not know the difference
    between a disconnection caused by the user's intent
    or one caused by network problems. If sessions
    can be dropped constantly because of network
    problems, Citrix recommends that you do not turn
    this feature on.

    To turn this feature on, navigate to the following
    registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
    \Citrix\ClientPrinterProperties
    Value Name: fReconnectionPrinterReconfig=3D3D1
    Value Type: REG_DWORD

    Restart the system after you change the registry for
    the change to take effect.

    To turn this feature off:

    Navigate to the above registry key.
    Value Name: fReconnectionPrinterReconfig=3D3D0
    Value Type: REG_DWORD

    Restart the system after you change the registry for
    the change to take effect.
    [From Hotfix XE102W029][#258464]

14. Task Manager showed that Wfshell.exe leaked one
    handle each time a user reconnected to an ICA
    session. Wfshell.exe did not close the handle after
    reconnection.

    Wfshell.exe has been modified so that it will close
    the handle after reconnection. This eliminates the
    handle leak problem.
    [From Hotfix XE102W029][#258464]

15. After installing or upgrading to MetaFrame XP,
    Feature Release 2/Service Pack 2, some applications
    experienced a problem when launching a Web browser.
    Symptoms of the problem were that a Web browser
    would not open, that the browser opened a URL
    passed to it incorrectly, or certain attachments
    that can be opened in a browser did not open.

    The problem occurred because the following registry
    key was backed up and changed to the MetaFrame
    server FTA executable after Service Pack 2 was
    installed. Also, some applications may be hard
    coded to look for popular Web browsers such as
    Iexplore.exe or Netscape.exe:

    HKEY_CLASSES_ROOT\http\shell\open\command

    This hotfix introduces a registry flag that gives you
    the ability to turn off the file type associations
    created by the MetaFrame server FTA and restore them
    to their original values.

    To disable the file type associations for server FTA,
    you need to create the following registry key for SFTA:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SFTA
    Value Name: DisableServerFTA
    Value Type: DWORD
    Value: 1
    [From Hotfix XE102W029][#44560, #44539, #45000]

16. Internet Explorer sometimes did not open in the same
    window size as it did when it was last run. This was
    caused by Content Redirection launching an instance
    of Internet Explorer using the SW_SHOW Windows flag.

    With this hotfix, Content Redirection launches an
    instance of Internet Explorer using the SW_SHOWNORMAL
    Windows flag.

    Internet Explorer opens with the same size window as
    when it was previously opened.
    [From Hotfix XE102W029][#44535]
**********************************************
This weeks sponsor Kevsoft Corporation=20
TScale by Kevsoft Corporation=20
Support 30% to 40% more users on your server farm
without buying new hardware! =20
http://www.kevsoft.com/
***********************************************

For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm
**********************************************
This weeks sponsor Kevsoft Corporation 
TScale by Kevsoft Corporation 
Support 30% to 40% more users on your server farm
without buying new hardware!  
http://www.kevsoft.com/
***********************************************

For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm

Other related posts: