I would like to create an Outlook add-in which receives push notifications from a remote server (this server isn't associated with the Exchange Server). Do Outlook add-ins have the API/functionality to support push notifications?
Related
I have Windows server 2016. set up rules on Outlook for specific email Subject to save attachment upon receive into specific folder and upload the attachment data into AS400 database. The rules and code is working fine but the problem is when email received the rules apply during server log off, the VBA code windows will left open. However the program is still running fine. The only problem for me is VBA code windows left open when rules trigger during Windows Server Logged off.
Keep running Outlook on the server side is not really a good idea. If you deal with Exchange profiles only you may consider developing a gateway for processing incoming emails instead. Outlook is a client-side application and designed running by a user. Here is what MS states for such scenarious:
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.
Read more about that in the Considerations for server-side Automation of Office article.
We're developing an Outlook addin that is specific and proprietary to our organisation. So we'd rather not put it on AppSource and we'd rather not put the addin source files (all the js,css etc) on a publicly accessible url even if we can keep the manifest file private.
Is there a way, through centralised admin and deployment, to distribute this Outlook addin to our staff, using Group policies, and still keep all the addin files privately hosted somewhere?
Yes, you can deploy an add-in by side-loading the add-in manifest xml file using Centralized deployment.
Yes, you can host add-in files privately but make sure the add-in host is accessible from your Outlook client.
If add-in is bound to work only when the user is connected to a particular network/VPN, it is good to educate the user that the add-in is unavailable outside the network boundary.
For on-premises and online environments that do not use the Azure AD identity service, you can deploy Outlook add-ins via the Exchange server.
Outlook add-in deployment requires Office 365, Exchange Online, or Exchange Server 2013 or later. Outlook 2013 or later.
To assign add-ins to tenants, you use the Exchange admin center to upload a manifest directly, either from a file or a URL, or add an add-in from AppSource. To assign add-ins to individual users, you must use Exchange PowerShell. For details, see Install or remove Outlook add-ins for your organization on TechNet.
Read more about possible ways in the Deploy and publish Office Add-ins article.
I recently was working through a lab integrating BizTalk Server 2010 with SharePoint Server 2010. The idea was to have an InfoPath form submitted to an http end point. BizTalk would receive the InfoPath form, transform it, and then upload the form to a SharePoint document library.
This would make use of a send port configured to use the SharePoint Services Biztalk Adapter.
However, when I submitted the InfoPath form, it successfully submitted to the HTTP endpoint, but it did not upload to the SharePoint library. Further digging produced the following error:
Error details: The Windows SharePoint Services adapter runtime does not have permissions to invoke the adapter Web service. In order to fix this issue, you have to add the ADVENTUREWORKS\BizTalkHost Windows account to the "SharePoint Enabled Hosts" Windows group on the Windows SharePoint Services machine. This operation will allow BizTalk host instances running under ADVENTUREWORKS\BizTalkHost Windows account to invoke the adapter Web service in order to send and receive messages to or from SharePoint sites. The group membership will not take effect until you restart the BizTalk host instance.
This error was triggered by the Windows SharePoint Services receive location or send port with URI wss://biztalkdemo:80/LoanApplications.
Windows SharePoint Services adapter event ID: 12458".
Once I added ADVENTUREWORKS\BizTalkHost Windows account to the "SharePoint Enabled Hosts" Windows group on the Windows SharePoint Services machine facing same issue and infoPath is not able to transfer from BT to share point library and message got dehydrated?
Other question regarding share point adapter configuration for CreditOrderSharePoint -- in the configure pipeline dialog box, in the processingInstructionOptions box, type 1 and then insert the processing instructions you specify in the xmlAsmProcessingInstruction box -- type ---
<?mso-infoPathSolution solutionVersion="1.0.0.21" productVersion="14.0.0"
PIVersion="1.0.0.0"
href="http://biztalkdemo/LoanApplications/Forms/template.xsn"
name="urn:schemas-microsoft-com:office:infopath:LoanApplications:http---
LoansProcessor-LoanApp" language="en-us" ?><?mso-application
progid="InfoPath.Document" versionProgid="InfoPath.Document.2"?>
So where do I get this information ?
ADVENTUREWORKS\BizTalkHost service account also need to be added to SharePoint site:
1.Go to your SharePoint site http://BIZTALKDEMO/
2.Go to Site Settings
3.Go to Site Administration
4.Click on Manage site groups
5.Click on Contributors
6.Add Members...(ADVENTUREWORKS\BizTalkHost)
7.Add \Sharepoint Enabled Hosts
8.Restart BizTalk host instance from the Admin MMC
We have developed a Outlook Add-in and want to share the add-in over network and deploy on user machine who does not have Admin rights. what is the best way to share the VSTO files over network since sending as email attachment is blocked.
You can develop a per-user add-in and then create a ClickOnce installer and publish it on a network share instead. See Deploying an Office Solution by Using ClickOnce for more information
I've got a CRM web app running on a remote server that needs to synchronise it's contacts with the in-house Exchange 2003 shared contacts.
Exchange 2003 doesn't appear to support web services. What would the typical approach to this problem be? My initial instinct would be to open port 80 on the Exchange server, run a simple webserver, POST to it and then control Exchange via OLE automation scripting (if that's what people are still calling it!) but there might be a better solution I'm not aware of.
Any suggestions?