3

It is not SharePoint issue rather it is Office problem. You can disable this warning going by going to trust center settings of excel. Click the File tab. Click Options. Click Trust Center, and then click Trust Center Settings. In the Trust Center, click Macro Settings. Make the selections that you want. Click OK. Read more here: Change macro settings ...


2

Looks like you are working with Office 2016. It has Modern Authentication enabled by default. There is a Registry-Key EnableADAL - try to disable it on your client. But be aware, this will break lots of cool stuff with Office365. This is one of the many reasons why i do not like FBA: It's cheap, but has tons of drawbacks. Office-Integration is one of them. ...


2

100% ACK to Waqas recommendation: Do not install Office on a productive SharePoint-Server. But: We had the same problem as you when installing Developer-VMs. They need Office to test their work. Microsoft has two installer-modes for Office-Applications: MSI and Click-to-Run. You cannot install a Click-to-Run Office on a SharePoint-machine as SharePoint is ...


2

I dont think, office go well with SharePoint on same server because they have conflicting binaries and SharePoint is also from office family. We always recommend do not install Office on SharePoint server, rather install it on client machine or create another VM and install it there.


2

This can be resolved by disabling Microsoft SharePoint Foundation Support in the Office 2013 applications via Control Panel > Programs and Features > Office 2013 application > Change > Add/Remove features. I've posted detailed steps in a similar thread here: Open with Access grayed out


2

The Document Information Panel that you've used in Office 2013 and prior was removed in Office 2016 as the DIP was an InfoPath control, which is no longer updated nor ships with Office. A replacement was made by Microsoft for the Office Click to Run version available via Office 365 (and is not currently available in the Office Volume Licensing version). ...


1

Check the possible solution Here


1

Out of curiosity, I have tried using Edge. Created CT. Added a column to CT Removed column from CT. All worked fine. But the Remove button has a JavaScript onclickevent: javascript:if(!ConfirmDelete()) return false;_....) I think, your Edge blocks a popup (confirm) window and this is why it seems that nothing is happening when you click "Remove" ...


1

Here is the real solution that worked for me on two SharePoint 2016 farms with FBA. Turns out that SecurityTokenService has SuppressModernAuthForOfficeClients property set to $false by default. If we set it to $true and restart IIS - the miracle happens and Office accepts my credentials from now on. $sts = Get-SPSecurityTokenServiceConfig $sts....


1

In addition to Waqas Sarwar post you can use Microsoft License Advisor for high-level estimation of server license and CAL cost


1

For pricing you have to contact the MSFT or the any partner. But You need a license for each running instance of the SharePoint You need a CAL for every person or device which access sharepoint. Check this and may be contact via Chat to get price.SharePoint 2016 licensing There is one more thing, if you want to share the file with external user then In ...


1

SP Designer 2013 is the SP recommended tool for now. I'm using it for SP 2013 and SP Online, no issues.


1

Yes, it's compatible but you should first install SharePoint Designer 2010 before installing Office 2016. So in your case, to can install and work with SharePoint Designer 2010 beside Office 2016, try to do the following: Uninstall Office 2016. Install SharePoint Designer 2010 (preferred x64). Install Office 2016.


Only top voted, non community-wiki answers of a minimum length are eligible