Installing language packs

1.Download a language-specific language pack

2.Install the language pack on every server

3.Run the SharePoint Products Configuration Wizard

 

Configure email integration

Outgoing email enables you to receive:

  • Alerts
  • Invitations
  • Task and workflow emails
  • Administrative notifications

Incoming email

  • Basic scenarios
    • –Email content to SharePoint lists or libraries
    • –Save attachments and email
  • Advanced scenarios
    • –Integration with SharePoint Directory Management Service and Exchange Server
    • –Create distribution groups for SharePoint sites
    • –Add mail-enabled lists to address books

Er zijn 3 opties, maar het beste is om geen eigen smtp server op de SharePoint server te plaatsen ivm spamgevoeligheid.

  • Install the SMTP server role on a server in the SharePoint farm
  • Configure SharePoint to use the SMTP server for outgoing mail
  • Configure the SMTP server to provide authentication credentials and relay the message to an Exchange Server deployment
  • Configure a Receive Connector on the Exchange Server deployment

In this scenario, you install the SMTP server role on a local server as before. You configure SharePoint to use this local SMTP server for outgoing mail. You then configure the SMTP server to authenticate and relay the message to an Exchange Server deployment. You configure a Receive Connector on the Exchange Server, and Exchange relays the now-authenticated mail to the end users.

A good example of when you might use this scenario is if you’re using Exchange Online. Exchange Online does not allow you to relay anonymous SMTP messages. If you want to send your SharePoint mail through Exchange Online you need to configure your local SMTP server to authenticate before relaying SharePoint mail on to Exchange. Note that the Receive Connector points to the intermediary local SMTP server.

 

Configuring Office Web Apps Integration

  1. Create a binding between the SharePoint server farm and the OWA server farm

First, you need to create a binding between the SharePoint server farm and the OWA server farm, and you do this by running the New-SPWOPIBinding cmdlet. Typically all you need to specify is the server name of your OWA deployment

–Use the New-SPWOPIBinding PowerShell cmdlet

 

2. Set the OWA zone to which SharePoint will direct requests

Next, you need to set the OWA Server zone to which SharePoint will direct requests. Depending on how you installed and configured it, OWA Server supports four zones –Internal-HTTP, Internal-HTTPS, External-HTTP, and External-HTTPS. The basic difference is that if you use an Internal zone SharePoint will treat the OWA Server name you configured in the previous step as a NetBIOS name. If you use an external zone, SharePoint will treat the OWA Server name as a fully-qualified domain name. You can also choose whether to use HTTP or HTTPS, and the usual advice applies here – use HTTPS unless it’s a test environment.

–Internal-HTTP

–Internal-HTTPS (default)

–External-HTTP

–External-HTTPS

–Use the Set-SPWOPIZone PowerShell cmdlet

 

Configuring Workflow Integration

SharePoint 2013 supports two workflow platforms:

  • SharePoint 2010 Workflow
  • SharePoint 2013 Workflow

SharePoint 2013 Workflow runs on a separate server product: Workflow Manager 1.0

On the workflow host:

  • Install Service Bus
  • Install Workflow Manager
  • Create a new Workflow Manager farm

–Configuration Wizard

–PowerShell

On the SharePoint farm:

If Workflow Manager is running outside the SharePoint farm:

–Install Workflow Manager Client 1.0 on every SharePoint server

–Import Workflow Manager certificates into SharePoint store

Run the Register-SPWorkflowService cmdlet

–Associates the Workflow Manager deployment with the SharePoint farm