October 20, 2010

Deploying Adobe Reader X


For a Reader XI version of this document see: Adobe Reader XI Deployment.

Adobe Reader X is here and with the new protected mode feature to improve security you should be considering your deployment plans now.

Note: These instructions are based on the US English version of Reader, so you may need to adjust some specifics to suit your environment and language.

Licensing Your Deployment

Although Adobe Reader is free you’ll need to agree to and obtain a license to distribute it in your own environment. Obtaining a license is simple, you’ll just need to answer a few questions such as the number of copies, how you will distribute Reader, which platforms and some information on your company including contact information. The same license can be used for distributing Flash player and Adobe AIR. To apply for the license go to the Adobe Runtimes / Reader Distribution License Agreement.

Obtaining the Adobe Customization Wizard

Unfortunately Adobe doesn’t use the same installer across all of their products – the installers for the Acrobat products are different to the Creative Suite products. For anyone who’s attempted deployment of the CS products would probably consider this a good thing.

To start customising Reader before deploying, you’ll need access to the Adobe Customization Wizard. The Customization Wizard X hasn’t changed much since the Customization Wizard 9, so if you have experience deploying Adobe Reader 8 or Reader 9, you’ll be comfortable customising and deploying the new version.

The Adobe Customization Wizard X should be available from here – Adobe Customization Wizard X. Otherwise you can use this direct download link: Adobe Customization Wizard X. An FTP site is also available – Adobe FTP site.

The Customization Wizard should be installed to an administrative workstation and it will allow you to create a custom Windows Installer transform that can configure the Reader installation, including settings to:

  • Optimise the behaviour of the installer by including silent installation, multilingual, and custom setup choices
  • Remove previous versions of Acrobat and Reader
  • Suppress the EULA, registration prompts, and the Getting Started window
  • Customise key application preferences — turn off automatic updates, add and set default job options, and customize collaboration and security settings
  • Remove shortcuts from the desktop and the Start menu
  • Edit each Adobe Acrobat application’s registry and installer tables
  • Customize file attachment handling within PDF files, including specifying which file types you want to block
  • Add or edit files that will be installed, including customized JavaScript or plug-ins
  • Preconfigure and lock Enhanced Security settings

Downloading the Reader X MSI

When creating a custom installer for Reader, always start with the latest version which you may need to obtain from the Adobe Reader download page. For an installer that you can extract and doesn’t include Google Chrome or Toolbar download the EXE installer from Adobe’s FTP site:

Note: if you need to download the latest installer, always grab a copy from the Adobe site to guarantee you have a source you can trust

Once you’ve downloaded the Reader installer, extract the setup files so that you can create a custom transform file. To extract, run the following command line:

AdbeRdr1010_en_US.exe.exe -nos_o"C:\Folder" -nos_ne

Replace C:\Folder with the path to a local folder. If you don’t specific the -nos_o switch, the files will be extracted here:

  • %ProgramData%\Adobe\Setup (Windows Vista and above)
  • %ALLUSERSPROFILE%\Application Data\Adobe\Setup (Windows XP / Windows Server 2003)

Once extracted, you should have the following files required for Reader deployment:

  • AcroRead.msi
  • setup.exe
  • Setup.ini

Creating a custom Transform for Reader X

Here I’ll step through creating a custom installation for Reader, providing some recommended settings for your deployment and add links to further information that you may need to consider for your specific environment.

Step 1 Personalisation Options: Open the Customization Wizard, click File / Open Package… and browse to AcroRead.MSI located in the folder that contains the extract Reader setup files. You can change the installation path if required:

Adobe Customization Wizard - installation path

Step 2 Installation Options: there a few options to consider here:

  • Default viewer for PDF files – if you are installing both Acrobat and Reader on the same machine, which application do you want to open PDF files by default.
  • Enable Optimization – Windows Installer will defrag the installation post install, leave this option enabled. [Windows Installer property: ENABLE_OPTIMIZATION]
  • Enable Caching of installer files on local hard drive – a copy of the Reader install files will be stored on the target machine ( in %ProgramFiles%\Adobe\Reader 10.0\Setup Files or %ProgramFiles(x86)%\Adobe\Reader 10.0\Setup Files). If you are deploying Reader with a deployment solution or virtualizing Reader, I recommend disabling this option. [Windows Installer property: ENABLE_CACHE_FILES]
  • Run installation – run the installer Unattended by default unless your specific deployment requires the installer to run completely silently (you can control this on the command line as well).
  • If reboot required at the end of installation – choose Suppress reboot and control reboots with an external process (such as a script or your deployment solution).

Adobe Customization Wizard - installation options

Step 3 Files and Folders: additional files (such as a JavaScript file to restrict menu items) can be added here:

Adobe Customization Wizard - files and folders

Step 4 Registry: add additional Registry values here to control the Reader installation. You can browse the local computer’s Registry to make adding entries simpler.

There are two edits I recommend making – browse to Destination Computer / HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run and modify these startup items, if they exist:

  • Adobe ARM
  • Adobe Reader Speed Launcher

Right-click each of these entries and choose Modify. Set Action to Remove value. This will prevent the installer from adding these entries and starting unnecessary processes at user logon. This step is very important for Terminal Server / Remote Desktop Session Host environments to reduce the processes that will run in each user’s session.


Step 5 Shortcuts: for whatever reason, Adobe deems in necessary to add a superfluous shortcut for Reader to the desktop. Don’t forget to remove that here – if you don’t remove the shortcut in the transform, it will be created when you patch Reader.

Adobe Customization Wizard - shortcuts

Step 6 Server Locations: the Server Locations settings allow you to configure additional server location paths to ensure source resiliency for the Windows Installer package.

Adobe Customization Wizard - server locations

Step 7 Security: further information on Adobe Reader and Acrobat security can be found here: Acrobat 9 Security Administration Guide. Options to consider include:

  • Enhanced Security Settings: Standalone and Browser (choose Enable & Lock)
  • Prevent end-user to add trusted Files and Folders
  • Prevent end-user to add trusted Hosts

Adobe Customization Wizard - security

Step 8 Digital Signature: the Digital Signature settings allow you to specify the security options (verification, creation, reasons) for digital signatures. Read more about Digital Signatures in the security guide and this document: Digital Signature Validation Cheat Sheet

Adobe Customization Wizard - digital signatures

Step 9 EULA: here you can suppress the display of the End User License Agreement when the user first launches Reader. [Windows Installer property: EULA_ACCEPT]

Adobe Customization Wizard - EULA

Step 10 Online and Features: access to several features can be controlled here:

  • Disable all updates: this will prevent the Adobe Updater from running automatically (but won’t prevent it from installing). The Check for Updates menu option will also be removed.

Warning: It is extremely important to disable Adobe Updater on shared systems such as Terminal Server/Remote Desktop Servers – a standard user can initiate a reboot of a computer if Updater applies a Reader update. This is because the update is applied using Windows Installer which runs in the System context.

  • Browser integration can be controlled here – you can force Reader to open PDFs outside of the browser rather than embedded in the browser window
  • Various menu items and features (such as Purchase Adobe Acrobat, Digital Editions) can be disabled
  • The Product Improvement Program can be disabled
  • The integration in Reader can be disabled

Adobe Customization Wizard - online features

Step 11 Comments and Forms: control and set options for comments in PDFs and forms.

Adobe Customization Wizard - comments

Step 12 File Attachments: control the launching of file types from PDF documents. You may want to set this option:

  • Default Action for Unspecified File Types: Never launch files of Unspecified Types

Adobe Customization Wizard - file attachments

Step 13 Launch Other Applications: the Launch Other Applications settings allow you to specify additional applications to be installed with Reader.

Adobe Customization Wizard - launch other applications

Step 14 Direct Editor: if you want to make further edits to the transform file you can do so here; however I often prefer to save the transform and open it with a 3rd party MSI editor.

Adobe Customization Wizard - direct editor

To disable the Adobe Acrobat Update Service introduced with Reader 10.1, navigate to the ServiceInstall table and take one of two actions

  • Drop the row ServiceInstall1 to prevent the install of the service
  • Change the value of StartType to 3 (manual) or 4 (disabled)

Disabling Additional Menu Items

After creating a custom installation there are a few menu items (less than previous versions) that you may want to remove for end-users:

Adobe Reader X - additional menu items

These menu items are:

  • Help / Online Support… / Knowledge Base
  • Help / Online Support… / Adobe Support Programs…
  • Help / Online Support… / Adobe User Community…
  • Help / Online Support… / Accessibility Resource Center…
  • Help / Online Support… / Generate System Report…
  • Help / Repair Adobe Reader Installation

Warning: It is extremely important to remove the Repair Adobe Reader Installation menu item on shared systems such as Terminal Server/Remote Desktop Servers – a standard user can initiate a reboot of a computer if the repair kicks in. This is because the repair is applied using Windows Installer which runs in the System context.

Just like previous versions, the only way to disable certain UI elements such as menu items and toolbars is to use JavaScript. This is a two step process – first we need to find out the name of the items we want to disable. To do that you will need to place some JavaScript in a file in the JavaScripts folder where Reader is installed. For example this on x64 Windows, place the file here: %ProgramFiles (x86)%\Adobe\Reader 10.0\Reader\Javascripts. Add the following code into the file and save it as ListItems.js

//Open Javascript Console;

//List Toolbar Buttons in the Console
var toolbarItems = app.listToolbarButtons()
for( var i in toolbarItems)
console.println(toolbarItems + "\n")

//List Menu Items in the Console
var menuItems = app.listMenuItems()
for( var i in menuItems)
console.println(menuItems + "\n")

When you start Reader a list of the user interface elements will be displayed:


The list is quite long, but you can use it to control the display of both menu items and buttons.

To hide the menu items listed above, save the following code in HideItems.js in the same JavaScripts folder. When Reader is run, the JavaScript will be executed and the items removed.


// [Help - Repair Adobe Reader Installation]

// [Help - Online Support]

// [Help - Online Support - Knowledge Base]

// [Help - Online Support - Adobe Support Programs]

// [Help - Online Support - Adobe User Community]

// [Help - Online Support - Accessibility Resource Center]

// [Help - Online Support - Generate System Report]

To deliver the script with the Reader package, use the Files and Folders section in the Customization Wizard. Add the files to Destination Computer / ProgramFilesFolder / Adobe / Reader 10.0 / Reader / JavaScripts (see Step 3 above).

Enforcing Protected Mode

Adobe Reader X Protected Mode will assist in reducing the potential security threats when opening or viewing PDF files, so it’s a feature you’ll want to ensure remains enabled on client computers. However, by default, users can turn this feature off – this option is available in the Preferences dialog box under General:

In the user’s context, Protected Mode is controlled with the following Registry value:

  • Key: HKCU\Software\Adobe\Acrobat Reader\10.0\Privileged
  • Value: bProtectedMode
  • Type: REG_DWORD
  • Data: 1

Fortunately, Protected Mode can also be enforced per-machine instead by setting this Registry value:

  • Key: HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\10.0\FeatureLockDown
  • Value: bProtectedMode
  • Type: REG_DWORD
  • Data: 1

With this set, users will be unable to disable Protected Mode. Use the Registry option in the Adobe Customization Wizard (covered in step 4 above) to set this value in your deployment package.

With the release of Reader 10.1, Protected Mode is now supported on Terminal Servers/Remote Desktop Servers.

Finding more Reader Preferences and Policies

To find the complete list of preferences for Reader and Acrobat you should refer to the Administrator’s Information Manager. This tool also contains the Reader and Acrobat Admin and Security guides.

The Administrator’s Information Manager (AIM) is an auto-updating and customizable AIR application containing the Preference Reference. AIM also includes and a growing list of other resources of interest to administrators in enterprise settings.

Additional Reading

Print Friendly
  • Hi Aaron.

    Good article as usual. A certain Matt C recommended a couple of other changes to the standard Adobe Reader installation when deploying in a Terminal Services / Citrix environment. I've now adopted these as part of my standard transform when deploying at customer sites.

    The changes disable Reader's default 2D graphics acceleration and line art and image smoothing (Preferences -> Page Display -> Rendering). With these disabled, scrolling through documents is a lot faster and a lot smoother. These settings require three values to be added to HKCU.

    To turn off 2D graphics acceleration:
    HKCUSoftwareAdobeAcrobat Reader9.0AVDisplay – bUse2DGPUf:0x00000000

    To turn off image smoothing:
    HKCUSoftwareAdobeAcrobat Reader9.0Originals – bAntialiasImages:0x00000000

    To turn off line art smoothing
    HKCUSoftwareAdobeAcrobat Reader9.0Originals – bAntialiaGraphics:0x00000000

    The standard behaviour of these values (when set through the application) is a little strange. Enabling the features removes the values from the registry, instead of simply setting them to 0x1.

    Keep up the good work,


    • Thanks Dan, I'm hoping to update the article in November with some additional recommendations

  • Pingback: Virtualising Adobe Reader X | Aaron Parker()

  • Adam

    I have yet to deploy Adobe Reader updates in my environment. Is the installer smart enough to remove existing versions of Reader and just install X? E.G. I have Adobe Reader 5 on one PC and 6 on another, will it remove 5/6 and install X?

    • I doubt it, like Reader 9, it will only remove v6 and above. See here for how to remove older versions of Reader:

    • kurbycar32

      We had the same problem when we initially pushed adobe reader 9. We had to remove all old versions using an uninstall script, we let it run for about 2 days on an aggressive schedule then pushed adobe 9. The website arron parker recommended has all of the uninstall strings you need.

  • RobVM

    Version X (10.0.0) is now available, although no sign of the new Customization Wizard

    thanks for the post, Aaron, I needed the way to extract the MSI so that I could have the setup.ini file…for some reason the CW wil bark if that file is not in the same folder as the MSI.

  • Looks like my files were extracted to C:UsersAll UsersAdobeSetup{AC76BA86-7AD7-1033-7B44-AA0000000001} or C:ProgramDataAdobeSetup{AC76BA86-7AD7-1033-7B44-AA0000000001}

    • Thanks Al, it looks like the released installer extracts things a little differently depending on whether you use the -nos_ne switch or not

  • Jky

    adberdr1000_en_us.exe -nos_ne

    extracted files could be under C:Documents and SettingsAll UsersApplication DataAdobeSetup or under your the temp folder of your current profile.

    In my case, they were extracted in the all users path.

  • MichelZ

    Is there a timeframe for the Customization Wizard?

  • Shoggi


    I have done above. I'm still struggeling to hide "sticky notes" and "highlight text" in the main toobar. I can't find this setting even with the ListItems.js.

    Any ideas?

  • Andi

    Hi Aaron,

    first of all thanks for the informative article. I have a question concerning the ListItem.js file. I’m not able to get the Toolbar Buttons, the console is empty. Did this work for you?



  • Aaron,

    Did u fake those screenshots or do you have access to a preview version of the Customization Wizard X?


    • Those screenshots are from the beta release of Cutsomization Wizard X.

      • Gary

        For once Google doesn't help with searching for the beta release.
        I too need to deploy Adobe Reader X in my network.

        Please post link to beta release of customization wizard X.

  • Are you attempting to open the Reader X package with the Customization Wizard 9?

  • Jason

    Do you have a link to the beta version?

  • Harry

    Where can we get this beta release of Cutsomization Wizard X?

  • JJJ

    Any chance to get the beta link for download? I need to deploy Reader X in my company.. damn adobe takes too long..

  • davidlim

    Customization Wizard for Acrobat & Reader X is targeted for mid-December release.

  • The beta release of the Customization Wizard X is not publicly available and I certainly would not recommend using it for production deployments. As davidlim points out the release version will be available in mid-December.

    Please don't ask for a copy of the beta version or post links – these comments will be deleted.

  • Harry

    Don't care if it's a beta version. I need to get an image rolled out ASAP and need reader X installed without all of its nasties.

    How did you get your hands on it then mister Aaron?

  • Pingback: Adobe Reader X | Asteriksz's Blog()

  • Phil

    Thanks for the article. It is probably worth pointing out there are a number of potential barriers to deploying this in a corporate environment. For us two key ones are that it clashes with SEP AV (hopefully fixed in an update soon), but perhaps more fundamentally doesn’t support opening pdfs from DFS and NFS shares. Details here, along with other nice gotchas you wouldn’t want to discover just after rolling it out to a few thousand desktops:

  • davidlim

    Adobe Customization Wizard X

  • Maddog

    Is this the beta version?

    • I don't think so, this version actually comes up labelled Customization Wizard X – the beta still said 9.

  • Orge

    You’ll get the Customization Wizard 10.0 here:

  • CypherBit

    My problem is the following (using v10.0 of the Customization Wizard), I'm unable to select Remove previous versions of Reader because they're greyed out.

    I want to remove previous versions of Reader (be it 7.x, 8.x, 9.x) but leave Acrobat on all machines. I can go to Direct EditorPropertyRemove_Previous and change that to NO, but then it won't uninstall any Adobe product (Reader, Acrobat).

    Any assistance, registry hacks, custom editing… would be appreciated.

    • Jbdement

      Will this question ever be answered? I’ve posted on the Adobe Forms too with anyone yet to reply. When I’m installing Reader why would I care about Acrobat? I want to be able to check the box to uninstall previous versions of Reader…….please…..

      • Rlwooley


        Both optios will only activate if you have both Adobe Pro any flavor and Adobe reader installed.

        The default remove Adobe Acrobat removes all Acrobat and the Reader version.

        Hope this helps!

  • SwedenXP

    Hey Aaron,

    Love your guide here – but I have some questions. I have got most things working, but I can´t get the top right blue "Comment" to disapear… any tips? I would also like to take some things out of the toolbar, ie. "add sticky notes" and "highlight text".

    Big thanx in advance


  • Nemo_G

    Any idea how to integrate the additional FontPack1000_Xtd_Lang.msi silently and without caching it in the program directory?

  • Nemo_G

    This is my proposal for unpacking the EXE to a path of your choice ():
    AdbeRdr1000_de_DE.exe -nos_o”” -nos_ne

    (;-) You may of course use *your* preferred language version

    • Thanks Nemo, I'll test it out and update the post.

    • SwedenXP

      I think that "AdbeRdr1000_en_US.exe" works with both winrar and 7-zip. The "AdbeRdr1000_en_US.msi" works only with 7-zip. Both for taking a peak into the file as for extracting it. /SwedenXP

      • Nemo_G

        Why not follow Adobe's recommendations to extract the file?
        Besides that, my above post has been changed (not by me). The command has to read
        AdbeRdr1000_de_DE.exe -nos_o"<AIP_path>" -nos_ne
        where <AIP_path> is the qualified path for the Administrative Installation Point

        • Confused_Angel

          Every time I run the command:
          AdbeRdr1000_en_US2.msi -nos_o”c:adobeinstall” -nos_ne
          I get the error window called “Windows Installer” with the error message:
          Invalid command lien argument. Consult the Windows Installer SDK for detailed command line help.

          I also get that error if I just run AdbeRdr1000_en_US2.msi -nos_ne

          • The -nos_ne switch is only for the EXE. If you are using the MSI you don’t need to extract it

  • Nemo_G

    @Aaron: Will you please change the name of the two posts above from Nemo -> Nemo_G?!
    I posted them before I subscribed. Another guy captured my "Nautilus" (;-)

  • You can download the customization wizard for x from

    danovich –

  • Thank you for this awesome tutorial m8, was able to create a sweet slim install

  • SwedenXP

    Has anone had any luck with “slimming down” Reader X yet?

    I have created a custom install (with help from above guide) and it works great, but it dosn´t make the install any smaller. Have tested with removing some of the api´s after installation and that works fine. But I need help to remove them before installation (in my custom install).


    • Do you mean slimming the package by size or for performance? In my own testing, I’ve found that only milliseconds are gained by removing the plug-ins, so I don’t bother with removing them.

      • SwedenXP

        You might be right.

        Although I did remove the following api´s by hand after install and I think my pdf-files open a little quicker: AcroForm.api, Annots.api, Multimedia.api and PPkLite.api.

        • Take a look at AppTimer to records startup times for Reader with various configurations.

          • Swedenxp

            Thax – I will do that!

          • SwedenXP

            @Aaron Parker

            Tried it as You recommended and You are right – it doesn´t matter that much. But thanx for the tip, the AppTimer is a nice tool.

          • Good to hear 😉

  • Thor

    Hi, when I’m added HideItems.js or any other file to package (Files And Folders – step 3), nothing happend.
    After install is in JavaScripts folder only JSByteCodeWin.bin and nothing more.
    Everything other is OK.
    What I’m doing wrong?
    (Using Adobe Acrobat X package unpacked with 7zip and Adobe Customization Wizard 10)
    Thank you

    • SwedenXP


      Strange… i followed the guide above – and it worked just fine.

    • Rlwooley


      Did you expand the lower target machine file location and drag n drop the file?

      • Thor

        Yes. In top window I’ve found a file on my local comuter. Then in the lower window I’ve choosed Destination Computer / ProgramFilesFolder / Adobe / Reader 10.0 / Reader / JavaScripts.
        Then drag n drop from top window to lower windows – Everything fine (I’ve tried many types of files).
        Then Save Package. If I install MSI, file (in “JavaScripts” folder in Reader folder in Program Files) is missing.

        • Rlwooley

          Save your file in the same folder as your reader msi file and rebuild the package. Ensure that you also include the java .js file with your distuabution folder and see if that helps.

          • Thor

            And how can i make/rebuild MSI? Thank’s for help (You’re obviously right).

          • Re-create or update the the transform – the .js file should be stored within the .MST

          • Thor

            But how can I rebuild MSI from all files (ABCPY.INI, AcroRead.msi, AcroRead.mst,, setup.exe, …..)?

          • You don’t – make all of those files available in the same folder

          • Thor

            If I launch AcroRead.msi – remotely, in Acrobat missing my .js. When I run localy setup.exe, everything’s Ok. Remotely i can to run (deploy) only the msi file, not exe 🙁

  • LE


    I just ran across your site and this posting and was wondering if you could provide specific information on adding an additional toolbar button.

  • Rlwooley

    Works great, have one question, issue though on you menu screen image look at the opening splah=sh screen on the lower left, yours defualts to “add notes to pdf”, mine is defualting to store and share your pdf.

    How does one force the “add notes and comments to pdf” setting.

    • I think that scrolls through various text and links, I haven’t specifically done anything to select that particular item

      • Rlwooley

        thanks will keep digng and testing.

  • EnVisMan

    Trouble with the new 10.0.1…

    Has anyone tried the above recipe on the new 10.0.1 – I have and it works – and I does not (the “about” still shows 10.0.0). Ideas please.

    • The 10.0.1 download includes the 10.0.1 patch as a seperate MSP (AdbeRdrUpd1001_Tier1.msp), you may need to apply this seperately if you are using MSIEXEC to install Reader.

      • SwedenXP

        This is a bit above and beyond my skills… One strange thing is that the 10.0.0 .exe file and the 10.0.1 .exe file contains exactly the same files, modified at exactly the same time, with exactly the same size.

        The complete .exe file of course differs in size… So I´m bit confused

        • If I download and extract the Reader 10.0.1 executable, I get these files:

          * ABCPY.INI
          * AcroRead.msi
          * setup.exe
          * Setup.ini

          These are exactly the same versions as 10.0. This additional file is the 10.0.1 patch:

          * AdbeRdrUpd1001_Tier1.msp

          Depending on how you deploy Reader, this needs to be applied seperately using the MSIEXEC /P command

          • SwedenXP

            Ahaa – so the new ver 10.0.1 isn´t a really a complete 10.0.1 – but why does it differ in size then?

            + I get the use of the updrade file AdbeRdrUpd1001_Tier1.msp – but thanx for the clarification.

            Sum (of all fears) install either 10.0.0 or 10.0.1 – cause they are the same (although they differ in size) and add AdbeRdrUpd1001_Tier1.msp.

            Hoped that 10.0.1 was a complete (already updated version)…

          • How does one get the Group Policy Object to pick up that .msp file and apply it?

            I’ve got Reader deployed using the instructions above, but I can’t find the option to patch it, or work out how to apply the patch to my distribution folder.

  • Joebvlack

    Thanks for the detailed steps. Wondering anyboby able to disappear the top right blue “Comment”, Sticky Notes.

  • An overlooked consideration about Protected Mode is that if you leave it enabled, then by design it will break the OLE integration with MS Office and you will not be able to embed or open embedded PDF’s from Office documents.

    • Thanks Aaron, that’s an interesting limitation

  • Makdaddy8888

    I like your article but did not want to do the JS section so whats the next step after I am happy with the newly editied msi. Do i just save then deploy or do I create a mst?

  • Makdaddy8888

    Do you have a guide on the JS Listitems.js debugger.

    • See the Enterprise resouces on the Adobe site listed in the Resources section on the article

  • Josh

    Aaron, do you know of any way to remove the Comments and email buttons from the menu bar? It appears the ListItems.js example you provided ONLY lists the tool bar items and not the menu bar ones. Any help would be greatly appreciated.

    • No, I haven’t looked into it. If I get some time in March, I’ll see what I can find.