QuickBooks Enterprise 9.0

    General discussion

    • Application Name:
            QuickBooks Enterprise
    • Application Version:
    • Company Name:
    • Sequencer Version:
            4.5 and 4.6
            Previously sequenced on 4.1 SP1/4.2 using "similar" methods.
    • App-V Client Version tested on:
            4.5 SP1, 4.6
      Operating System sequenced on:
            Windows XP
            The package requires the .net framework 2.0 and Adobe Flash 9.0 (or above).  It also installs two services.  Because of this, the recipe is only good for the 4.1 SP1 or above. 
            A mounted drive on another machine, used to hold a “company file” (which is what Intuit calls the database), is suggested here in order to share the data file external to the package.  Users will need read/write access to the database on this mounted drive.  To support a single user, the database could be left in the package, however be aware of the impact this may have in a roaming profile situation if the user pkg file remains in the profile.  The files placed here require about 10MB upon install and will grow with use.
    • Client Operating Systems successfully deployed to
            Windows XP
            Windows Server 2003 Terminal Services
    • *Posted by non-Microsoft Employee: Tim Mangan, TMurgent Technologies
    Steps to sequence the application:
    <Step 1 (setup)>

    Prior to entering the sequencer, mount a server share as a drive.  This drive letter should be the same as will be used on the client.  (This is not a hard requirement, we simply use this as a way to ensure that when a user uses the File menu to open a company file it will be default to the right folder).

    Also install the dependencies, as appropriate.
    <Step 2 (Monitoring)>
    Start the Installer.

    Select Check Updates option.  As of our testing, no additional updates to the installer were available.

    If the prerequisites are not met, the installer should say that it wants to install the .net framework 2.0 and Flash 9.  Go ahead and let it do it.  After, you can continue with the installation.

    You will need to accept the license agreement.

    Enter the license and product keys that you received with the product. 

    Change the install folder to the Asset Folder (the 8.3 compliant named folder on the SFT_MNT drive).  Service and support shortcuts are optional, as is the Google Desktop option.

    Finish the installation (the dialog suggests it might take 5 to 20 minutes; they are not kidding).

    Launch the product for the first time.  .  If the product asks you to register the product  at any time in the sequencer, select “Remind Me Later”.

    Select to create a new “Company File” (the database; this can be a test database or the real thing).  Input information into the interview wizard; at the end you will create the “Company File” on the mounted share.

    If a survey box pops up, you may want to check the “do not show again” box.

    When the Online account dialog appeared, we closed the window.  This might be appropriate to complete during sequencing in some situations.

    Perform any other customization appropriate for your organization.  When done, shut down the application.

    We generally recommend launching and shutting down the application a second time.  Use “Remind Me Later” for both the registration and online account popups (if they appear).  The program should automatically open up to the Company File you created.

    Delete the following files at this time:
          C:\Documents and Settings\All Users\Application Data\Intuit\Entitlement Client\V5\

    Note that these instructions assume you do not launch the application at the end of the wizard.  If you choose to launch, you will need to remove these files from the VFS\CSIDL_COMMON_APPDATA are in the files tab of the sequencing editor later on instead.
    <Step 3 Remainder of Wizards>


    <Step 3 Remainder of Wizards>



    • Known Issues/limitations:

      Intuit Licensing

      The installer will generate a license file which would normally be captured as part of the package that is tied to both the user license key and the specific PC being sequenced on.  While we do not know how the vendor ties to the specific PC, it is reasonable to assume it includes something such as the first NIC MAC address.  We don’t care how they do this as we are not trying to defeat it, just work with their licensing system.

      We will install the product and run it.  Before closing out the installation monitoring we will remove this license file.  After completing the sequencing, we will run the package on the target client.  If we did not remove this license file, the client would fail with an error at startup.  We have found that we cannot repair this on the client if we leave this license file in the package.  Instead, with the file removed the client will start up and the file can be recreated by registering the software on that machine.  This will create a new license file that will be saved in the user’s package in his/her profile.  This would be sufficient for a desktop client, however, we want to deploy on Terminal Services so we want to license it ourselves for the Terminal Server.  We run the package without the license on the terminal server and then use a trick to extract this license file from the user profile package. We then reopen the sequence for upgrade and copy this new license file back in.  After that we can deploy the new package version for use on the client Terminal Server.

      This trick of pulling the new license file from the user profile and adding in back into the package would not be needed if we were deploying on a desktop/notebook PC.  We use this trick in the recipe because we intend to deploy on a Terminal Server and do not wish each user to have to perform the registration.  We need to note that the package will only work on one PC.  This means that if you have multiple terminal servers you will need to restrict users of this package to a single terminal server.
    • Approximate sequencing time:
            45 minutes.
    • Other (Optional fields)
      Package Size:
            800 MB (plus external database), 500MB with compression.
      App-V friendly copy protection scheme?  
            See Issues/Limitations
      Additional Notes/Links:

      Custom scripts to assist in the process:

    Descriptive Tags:

    ·        App-V, Intuit, QuickBooks




    Note that a QuickBooks Updater is added to the user’s “startup” folder; you probably want to remove this application when in “Configure Applications”.

    • <Step 4 Sequence Editor>
      4.5 and 4.6 Specific only:   Uncheck the Enforce Security Descriptors box on the Deployment Tab.  This option is not available on earlier sequencer, which results in the same behavior as when this box is unchecked.

      In the Virtual File System Tab, you may find at the bottom of the display a number of file and folder references that are associated with the mounted drive that the database was created on.  

         * For example, if the mounted folder was P: you might see “;P:00000xxx”. 
            *    If the mount was to a share on system foo, you may find another set under a “foo” folder. 

      Delete these mappings.  To do so, click on the highest level folder of the group and hit the delete key.  Do this for each group.

      4.1 and 4.2 Specific only: In the File tab, there may be the actual files created on the mounted drive.  These will appear at the end of the VFS area.  It would be OK to delete these from the file tab in order to shrink the size of the sft, except that when we tried to do this on 4.1SP1 the sequencer died.  So we left these files in, where they will not be used.  These files do seem to appear in the 4.5 and above sequencer.


    • Edited by Manita Sharma Thursday, April 8, 2010 6:18 PM Added company name
    Tuesday, March 16, 2010 3:43 PM

All replies

  • Hello Tim,

    Were you able to get this to work in a terminal server (RDS) environment?  We're getting errors like this after registering in one user's rds session:

    [Error 3371,StatusCode - 1118] QuickBooks could not load the license data.


    Friday, August 19, 2011 9:19 PM
  • Yes, works great under TS.  Each version of QB seems to do the licensing slightly differently, so the solutions are all version specific, but basically it comes down to locating the license file and removing it from your sequence.   The user gets prompted the first time they run.  Since that license info will be placed in the user PKG file, you don't want that roaming to another TS server.  So probably publish to only one server.
    Tim Mangan MVP for App-V and Citrix CTP Author of AppV books: "The Client Book" and "OSD Reference Book" ( )
    Friday, August 19, 2011 11:46 PM
  • Hello Tim,

    Thanks for your reply.  Is there a way to publish app-v apps to only one server?  If so, this may be our solution.


    Tuesday, August 23, 2011 8:50 PM
  • If you are using App-V with the "full infrastructure" (server with RTSP), apps are only publishable on a per user basis.  SCCM can push out the virtual apps to specific machines, and of course with the "stand alone client" would work as well.

    Since you are working with TS, if you are also using Citrix, and are using Citrix to publish apps instead of publishing desktops, then you can allow App-V to stream to each machine but only publish this app to a specific machine under Citrix.  This, of course, means that the user might end up with two logon sessions on two different servers simultaniously (one server for the other apps and one server for QB), and if you use roaming profiles you need to worry about profile "last write wins".  Solvable, but a PITA.


    Tim Mangan MVP for App-V and Citrix CTP Author of AppV books: "The Client Book" and "OSD Reference Book" ( )
    Tuesday, August 23, 2011 10:52 PM