We have Microsoft Office 2013 (to include Access, Excel, Outlook, Powerpoint, Publisher, and Word) installed locally on our thin client images/virtual machines, with exception to OneNote 2013. OneNote 2013 is setup as a published application on the XenApp servers as not everyone needs or uses it. The problem we are seeing is that the locally installed Outlook 2013 and published OneNote 2013 will not communicate with each other, even after verifying that the OneNote Add-In is enabled in Outlook 2013. IF we install OneNote 2013 locally along side the rest of MS Office 2013 to the images/virtual machines, Outlook 2013 and OneNote 2013 will communicate without any issues.  Is there a way around this? Is there any documentation on MS that shows installation requirements in this type of environment? Does OneNote 2013 HAVE TO be installed locally in order to work with Outlook 2013 or is there an add-in or registry entry that will allow the published version of OneNote 2013 to communicate with the installed version of Outlook 2013.

Or is there documentation that shows linking OneNote 2013 to SharePoint 2013 allowing Outlook 2013 to communicate with OneNote 2013 through SharePoint 2013?

Thank you,

Gregory Hall

I haven't found any documentation stating this, but I think this is logical. The connection between OneNote and Outlook must be stored in registry, since you don't have OneNote locally, the connection doesn't exist.