SharePoint 2016 APR 2017 Update

Featured


Hi All,

Just thought of utilize the SharePoint recent server role changes. Installed the SharePoint APR 2017 using below link in my test server which installed in Azure Cloud.

April 2017 CU for SharePoint Server 2016 is available for download

Before install the CU APR 17

2017-04-15 00_22_07-PTC003 - 52.169.202.124_3389 - Remote Desktop Connection

After installing the CU APR 17

2017-04-15 01_11_39-PTC003 - 52.169.202.124_3389 - Remote Desktop Connection

We will get the all new server role option in the CA. Just click the role which you want, I just changed the WFE as Frond-end with Distributed cache and Application server as Application with search with simple UI..

SharePoint 2016 Service Accounts Recommendations

Tags

,


Service Accounts are a very important to installing every version of SharePoint. Let’s take a look at the SharePoint 2016 Service Accounts that I recommend and used.

Account Description Local / Application Permissions Local Security Policy
SP_Admin This account will be used to Install and configure the SharePoint farm initially. After the initial setup, you can grant the farm administrator rights to your SharePoint Administrators account so they can log in and manage SharePoint with their own account. Domain User Back up files and directories
Local Administrator on the SharePoint Servers Debug Programs
Member of the following SQL Roles Manage auditing and Security log
Restore files and directories
DB Creator Take ownership of files or other objects
Security Admin
SP_Farm Runs the SharePoint Timer and Administration Service Domain User Allow log on locally
Member of the following SQL Roles Adjust memory quotas for a process
Impersonate a client after authentication
DB Creator Log on as a batch job
Security Admin Log on as a service
Replace a process level token
SP_Services Runs the Application Pool for most of your Service Applications. There are some service applications that require more rights and a dedicated Service Account is recommended. We’re converting those a bit lower in this blog post! Domain User Adjust memory quotas for a process
Log on as a batch job
Log on as a service
Replace a process level token
Impersonate a client after authentication
SP_Pool Runs the Application Pool for your Web Applications. Domain User Impersonate a client after authentication
Log on as a batch job
Lon as a service
SP_Crawl The Default Content Access Account for the Search Service Application. This account is sued to crawl the content of your SharePoint Web Applications. Domain User
This account needs to have Read Access on all your Web Applications (given automatically)
SP_Sync Used to synchronize profiles between AD and SharePoint Server 2016 Domain User Needs to have “Replicate Directory Changes” in the Active Directory  Tutorial here
SP_C2WTS Used to run the Claims to Windows Token Domain User Act as part of the operating system
Service Local Administrator on all SharePoint Servers running the C2WTS service Impersonate a client after authentication
Log on as a service
SP_SuperUser Object cache account (Super User). Must not be an account that will ever be used to log in to the site. Domain User
Full Control on your Web Applications
SP_SuperReader Object cache account (Super Reader). Must not be an account that will ever be used to log in to the site. Domain User
Full Read on your Web Applicationss
SP_SQLAdmin This account will be used to Install and configure the SQL Server initially. After the initial setup, you can grant the SQL Admin rights to your SQL Administrators account so they can log in and manage SQL with their own account. Domain User Back up files and directories
Local Administrator on the SQL Server Debug Programs
Manage auditing and Security log
Restore files and directories
Take ownership of files or other objects
SP_SQLEngine This account will run the Database Engine service Domain User Log on as a service
Replace a process-level token
Bypass traverse checking
Adjust memory quotas for a process
Perform Volume Maintenance Tasks (Only If you want to enable Instant File Initialization)
SP_SQLAgent This account will run the SQL Server Agent Service Domain User Log on as a service
Replace a process-level token
Bypass traverse checking
Adjust memory quotas for a process

Microsoft Flow (SharePoint 2013/2016)


Microsoft Flow is a preview( as of now) product to help you set up automated workflows between your favorite apps and services to synchronize files, get notifications, collect data, and more. After you sign up, you can quickly start to automate your work.

Find the more details about SharePoint Modern Lists and Microsoft flow in below video.

 

Happy Learning!

SharePoint Search 2013: The remote server returned an error: (503) Server Unavailable.

Tags

, ,


Today I got the new issue in SharePoint Search 2013 that, remote server (503) error.

2016-06-11 07_10_48-PWWBW2-HCCSP02 - Remote Desktop

Opps! What happen to my search application. Let’s check the following steps to resolve the issue.

503 indicates that the application pool is stopped that is hosting a site.  In this case, it’s the SharePoint Web Services Virtual directory hosting the Search Admin web service.  I selected the virtual directory, right clicked, and chose Advanced Settings and the GUID for the application pool is present.

Try starting the application pool and refreshing the page.  If it still fails and the application pool is stopped.

2016-06-11 06_32_32-PWWBW2-HCCSP02 - Remote Desktop

If still you are getting the same error, this problem occurs because the application pool identity doesn’t have appropriate permissions in SQL.   For the service account running Search Service Application, you’ll need to ensure this account has the following roles on SQL Server.

db_owner and public roles on the following:

  1. Search Crawl Store Database
  2. Search Service Application Database
  3. Search Property Store Database

WSS_Content_Application_Pools role on the following

  1. SharePoint_AdminContentDatabase
  2. SharePoint_Config Database

Check the permission level in searver like below.

The Search Service Account is missing from the local WSS_WPG group.  Access computer management, local users and groups, and ensure the Search Service Account is a member of this group.

Finally make sure the IIS_IUSRS group isn’t missing from the local security policy.  Specifically, the group needs to be added to the following policies: Impersonate a client after authentication and Log on as a batch job

Office Online Server (Newer version of OWA)


Being office lover, as a administrator we have to know about the newer version of software’s in our passionate technology. Yes! We have a new Office online server for the replacement of Office web apps in SharePoint/Exchange.

What is exactly in Office Online Server? When it is used?

Office Online Server is an Office server product that provides browser-based file viewing and editing services for Office files. Office Online Server works with products and services that support WOPI, the Web app Open Platform Interface protocol. These products, known as hosts, include SharePoint Server, and Exchange Server.

When used with SharePoint Server 2016, Office Online Server provides Word Online, Excel Online, PowerPoint Online, and OneNote Online.

When Exchange Server is configured to use Office Online Server, users of Outlook Web App can preview Office file attachments by using Word Online, Excel Online, and PowerPoint Online. These previews provide rich, full-fidelity viewing of Office files and any comments within them, without downloading the files before viewing them.

A graphic that summarizes the viewing and editing capabilities of Office Web Apps on different kinds of devices. It highlights those that are optimized for touch screens.

Keypoints to know about Office Online Server

  • Office Online Server uses the same minimum hardware requirements as SharePoint Server 2016.
  • The 64-bit edition of Windows Server 2012 R2 is required.
  • Install Office Online Server in its own virtual machine. Don’t install any other server applications, such as SharePoint Server, in this virtual machine.
  • When using Hyper-V for multi-server Office Online Server farms, each virtual machine should be on a separate virtual machine host. This way, the Office Online Server farm will still be available if one of the hosts fails.
  • Don’t install any other server applications on the server that’s running Office Online Server. This includes Exchange Server, SharePoint Server, Skype for Business Server, and SQL Server. If you have a shortage of servers, consider running Office Online Server in a virtual machine on one of the servers you have.
  • Don’t install any services or roles that depend on the Web Server (IIS) role on port 80, 443, or 809 because Office Online Server periodically removes web applications on these ports.
  • Don’t install any version of Office. If it’s already installed, you’ll need to uninstall it before you install Office Online Server.
  • Don’t install Office Online Server on a domain controller. It won’t run on a server with Active Directory Domain Services (AD DS).
  • By default, Online Viewers functionality is enabled after you install Office Online Server
  • Certification part is more important for single and multiple OOS installation. Check the best practice before start installing.
  • Office Online Server can communicate with SharePoint Server, Skype for Business Server, and Exchange Server by using the HTTPS protocol. In production environments, we strongly recommend that you use HTTPS.

 

For more info: Plan for OOS

Next post, we will see how it will deploy in real time!

Web Performance and Load Testing SharePoint 2010 and 2013 Applications

Tags


Web performance tests can be recorded and then run and analyzed against your SharePoint applications. For example, you can create web performance tests that conduct the following operations on your SharePoint application:

SharePoint 2010

  • Site rendering
  • Document library operations
  • Task, calendar and library operations
  • Search content
  • Wikis
  • Customized web parts
  • Workflows
  • Multiple operations from the ribbon
  • Playing the tests against multiple sites and lists
  • Office Web Applications (OWA) – Uploaded and downloaded scenarios [Visual Studio 2012.2]
  • Manage Metadata SA and look up columns in the lists and libraries [Visual Studio 2012.2]
  • Integration of SharePoint and Excel Services [Visual Studio 2012.2]
  • For InfoPath – you can use the plug-in (tool) from CodePlex [Visual Studio 2012.2]

SharePoint 2013 (Requires [Visual Studio 2012.2])

  • All the scenarios listed above for SharePoint 2010
  • Social
  • SharePoint Apps

SharePoint 2013/Viusal Studio 2013 : Sideloading of apps is not enabled on this site

Tags

, , ,


When publishing a SharePoint hosted application to a development site on Office 365 , running SharePoint 2013, you may receive the following error:

“Error occurred in deployment step ‘Install App for SharePoint’: Sideloading of apps is not enabled on this site.

Solution: You need to enable the Sideloading feature on the site.

1. Download and install the SharePoint Online Management Shell for PowerShell

2. Download the script Sideload.ps1 and execute it within the SharePoint Online Management Shell.

Note: This is not recommended for a production site. Deploy applications using the App Catalog on a production site.

Link