I am trying to deploy an add-in with add-in commands on the desktop version of office 365, using the Centralized Deployment method.
I followed the instructions for Centralized Deployment and the addin appears as "on" in the Office 365 admin center. I used both "Everyone" and "Specific User/Group", but when I open the Word application and go to Add-ins, under "Admin Managed" I see no addins , and the message "No add-ins currently available." The addin is'nt visible neither on Word 2016 Desktop (with subscription) nor Word Online. I have also tried deploying addins from office store using the same method (Centralized Deployment) but they also don't show up.
I have Word version 1708 (8431.2270), and I am using a developer subscription.
Do you have any suggestions to fix it or know why it is not working? Thank you.
Also,
I noticed that I am getting a 403 Error when refreshing the Admin Managed tab (when calling https://euc-word-edit.officeapps.live.com/we/AddinServiceHandler.ashx)
I solved, by enabling Exchange, and my manifest had an issue.
I changed <CustomTab id="HelloWorld" x:type="CustomTab"> to <CustomTab id="HelloWorld"> and it worked.
Related
We have a client that uses SCCM to deploy Excel to their users and according to them, they package other add-ins with Excel so that when it's installed they have access to these add-ins.
We have an Office Add-in (specifically Excel), not the VSTO or COM add-ins, a web Office Add-in.
I've done some research and I'm struggling to find a solid answer as to if it's possible to deploy the add-in with SCCM? So far my deduction is no, but I thought let me confirm with the professionals.
And then is there any other solution on how to deploy the add-in otherwise?
Please note the following restrictions on their end
Locked the Office store, users cannot install an add-in from the Office store
Don't have access to the Admin Center to deploy the add-in
What I have tried ?
I have tried using Power Shell to upload office add-in by referring following link,
Use the Centralized Deployment PowerShell cmdlets to manage add-ins
but I ended up receiving,
PS C:\WINDOWS\system32> New-OrganizationAddIn -ManifestPath 'D:\Manifest\manifest.xml' -Locale 'en-US'
Extracting Add-In's manifest...
**The Add-In you are trying to upload supports Single Sign On and to upload the Add-In you need to use Office 365 Admin Center.
Press Enter to consent to the Add-In in Office 365 Admin Center.**
If there are any issues you can go to
https://portal.office.com/adminportal/home?assetid=lob&mktcmpid=powershell#/Settings/ServicesAndAddIns
And go to Settings > Services & Add-Ins
Also, the URL mentioned in above message, which is, https://portal.office.com/adminportal/home?assetid=lob&mktcmpid=powershell#/Settings/ServicesAndAddIns is old. We no longer upload add-in from this endpoint.
Additionally, I do have referred,
Deploy and publish Office Add-ins
As, since it is an Outlook add-in, it cancelled out uploading it via SharePoint app catalog.
Is there any other way that I can do it using command shell or rest APIs ?
Additionally, is there any restriction to upload add-in which supports Single sign on via PowerShell ?
I recently implemented an Outlook plugin for my enterprise and now I want to deploy it to all of the users on the enterprise. Is there a way to deploy the add-in installer to all of the users on the Active Directory, maybe using Outlook Exchange?
I checked this page, and looks like the guys at commvault nailed that.
Any ideas?
You can't deploy add-ins via email with Exchange, if that's what you are hoping for. If your add-in is packaged in a Windows Installer setup file, then you can use traditional Windows Desktop Application deployment methods to distribute your add-in.
Our Excel 2007 VSTO solution (built in Visual Studio 2010 SP1 using C# 3.5) is published via ClickOnce.
Clients deploy by clicking a URL using Internet Explorer that looks something like:
http://ourserver.com/ouraddin.vsto
It sometimes causes the Program Compatibility Wizard to pop up post-install and display "This program might not have installed correctly ..."
Does anybody know any workarounds?
I found this post which talks about modifying the manifest files, but that seems to apply to regular ClickOnce solutions not VSTO.
How to prevent "This program might not have installed correctly" messages on Vista
I tried using the MageUI app to open the VSTO file and look for a way to embed the supportedOS tags but there was nowhere to put it.
I also found documentation on editing VSTO manifests, but would prefer not going down this route unless absolutely necessary as one would think the publish wizard out of the box should just work.
http://codeidol.com/csharp/c-sharp-in-office/Deployment/Editing-Manifests/
Perhaps there is a way to modify the source VSTO ClickOnce schemas in the build system to avoid editing the manifests as a post-build task?
Any insight would be greatly appreciated!
Thanks,
Chris
I developed a sample application in visual studio 2010. I created an Empty SharePoint Project and gave the local site url for debugging. Checked "Deploy as Farm" as the trust level of the SharePoint solution. Added a visual webpart and also a class to the solution. I am able to build and successfully run the application using visual studio. In my local machine am using SharePoint foundation 2010 to debug the SharePoint application.
Now i want to deploy this application in the SharePoint server 2010 which is in a virtual machine.
1. I copied the .wsp file of the application i created to the virtual machine.
2. From the central administrator in the VM I created a web application and the site collection.
3. Then using Site Actions -> Site Settings -> Solution(Galleries), choose the .wsp file for uploading. it showed a "Warning: You should only activate this solution if you trust this solution. An activated solution can read, modify and delete your data. " and the activate button is disabled.
Then I tried to do same in my local machine on a different site collection. Here Activate button is enabled but when clicked it threw exception
Server Error in '/' Application.
This solution contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution 'aee60282-765d-4c9f-b67a-5981f18a6d3b' failed validation, file manifest.xml, line 10, character 4: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'FeatureManifests, ActivationDependencies' in namespace 'http://schemas.microsoft.com/sharepoint/'.
What could be this error?
The "TemplateFiles" element refers to items that will be copied onto the web server. This is allowed for farm solutions (which are deployed via CentralAdmin), but is not allowed for sandboxed solutions (which are deployed via the Solution Gallery).
When you deploy your wsp with visual studio, you deploy it as farm solution.
When you deploy your wsp from site settings into solution galery, you deploy it as user solution (sandbox solution) with some limitations :
first, avoid using out of the box visual webparts, it's prohibited !
Deploy your wsp by writing powershell script.
A good starting point here :
patrickboom.wordpress.com/2010/05/31/using-powershell-to-deploy-sharepoint-solutions-wsp-2/
Le_Fredo is correct here, when attempting to deploy a WSP file into the site collection directly under the site settings, you won't be able to. I found this article from microsoft to be extermely helpful
http://technet.microsoft.com/en-us/library/ff607688(v=office.14).aspx