3 Replies Latest reply on Jan 15, 2015 12:01 AM by greber

    FileMaker on Microsoft APPV

    greber

      We use Citrix Metaframe as Client platform for our several hundred users (Microsoft Windows Server Software 2008R2).

       

      We first used FileMaker 12.04 as a package installation on all our Citrix Servers and everything works well.

       

      About a year ago, we switched to Microsoft APPV installation (application virtualization). This works well, except that printing is very slow.

      Printing of 6500 indiviualized letters:

      regular installation 5 Min.

      APPV installation:   2:30 h

      (Just creating the printfile in the print queue, actual printing takes longer depending on the printer).

       

      This slow print file creation muss have something to do with the interaction of the filemaker APPV installation with the connection to the print queue. You can actually see that one page printing on APPV takes several seconds, while with a regular installation on a Windows client more than 1000 letters are created per Minute.

       

      Any idea why APPV is so slow?

       

      Thank you for your advice.

       

      Bernhard

       

      PS: i already consulted Micorsoft and implemented the following switch, however no change in performance.

       

      http://social.msdn.microsoft.com/Forums/de-DE/eb6aa26c-cf0e-42c6-aff0-9a113eedb9f4/slow-printing-from-ts-from-an-appv-virtualized-application?forum=mdopappv

       

      • Well, there is one switch that fixes this issue

      Can someone
      tell me the consequense of allowing local interaction? The switch below seems to resolve the print issue

        <POLICIES>

      <LOCAL_INTERACTION_ALLOWED>TRUE</LOCAL_INTERACTION_ALLOWED>

      </POLICIES>

       

      http://technet.microsoft.com/de-de/library/cc843805.aspx goes into more detail.

        • 1. Re: FileMaker on Microsoft APPV
          mikebeargie

          This article covers local interaction very well:

          http://blogs.technet.com/b/appv/archive/2007/09/20/a-look-under-the-covers-the-local-interaction-allowed-tag.aspx

           

          The main consequence of overriding it is the possible introduction of application conflicts, because your application goes from being run in it's own container to being linked with the local system.

           

          I would run a small test of five users printing to the same printer at the same time to make sure there are no application conflicts with the tag enabled. But it should be fine for your use case.

           

          I actually remember enabling this tag for the same reason in a Hyper-V deployment of FM12 a few years ago.

          • 2. Re: FileMaker on Microsoft APPV
            greber

            Thank you Mike for your answer, however we habe already set the local interaction tag, however we do not realize any performance changes.

             

            Bernhard

            • 3. Re: FileMaker on Microsoft APPV
              greber

              What happened in the meantime: we realized, that we still had a Filemaker 10 installation on Citrix with APPV, so we run a test with the ex/imported data for Version 10, and realized that the speed was similar to a local FileMaker 13 installation!

              Now also FileMaker 13 is installed on Citrix with APPV and we must realize, that Version 13 again is similar to a local installation (7 Min 73 APPV versus 4 Min 50 for 6239 A4 letters). On FileMaker 12 we had about 2 hrs 30.

              Always with <LOCAL_INTERACTION_ALLOWED>TRUE</LOCAL_INTERACTION_ALLOWED>

               

              Conclusion: Something wrong with the FileMaker Windows Version 12 in the sense, that it is very slow on Citrix APPV.

               

              Bernhard