SharePoint Destination

  Situation : Created a web application and chosen “Default zone” for Trusted Identify Provider authentication “iTrust” – (SAML Authentication) Note: Trusted Identity Provider Authentication enables federated users in this Web application. This authentication is Claims token based and the user is redirected to a login form for authentication.   Issue: Site is working fine but “Search” didn’t work. When checked for the reason, found that the default zone should be windows authentication which makes ‘Search” work. Resolution: -          -   Need to create standard default zone windows authentication (Though this is not required – as the site created is for federated authenticated external users with SAML authentication). -           -  Then extend the windows default zone application into Trusted Identity provider “Extranet/Any available zone” site.   Step1: Default zone windows authentication web application -          --  Create a new webapplication and provide th

  Situation After implementing “iTrust” – SAML authentication while creating external facing sites(DMZ Area) – office files didn’t work.   Task/Analysis Microsoft Office 2016 clients use modern authentication by default. In certain configurations, modern authentication isn’t supported by the Office 2016 clients with SharePoint Server 2016, such as when it is used for Active Directory Federation Services (AD FS) 3.0 installations. SharePoint administrators can now configure SharePoint Server 2016 to suppress modern authentication in Office 2016 clients .   Action To configure SharePoint Server 2016 to suppress modern authentication in Office 2016 clients, follow these steps to run Microsoft PowerShell commands in the SharePoint 2016 Management Shell:   When you install SharePoint Server 2016, the user account from which you ran the installation is granted the appropriate permissions to run Microsoft PowerShell cmdlets. If any users have not been added to run a Microsof

 Sometime back in my project , I couldn't deploy wsp packages anymore. After some analysis found there are lot of one time job were running and it was blocking wsp deplopyment. Here I have provided the steps to resolve it, -   In Central Admin checked in Farm Solution Management the status was stuck on Deploying​ -   Stopped the SharePoint Admin and SharePoint Timer services       -   Checked and found multiple One-time jobs​, deleted those using the scripts below: -           Get-SPTimerJob | where{$_.DisplayName -eq $null} | foreach-object {$_.Delete()}Get-SPTimerJob | where{$_.schedule.description -eq "One-time"} | ForEach-Object{$_.Delete()} -           Checked if the timer service is ON using the script -           $farm   = Get-SPFarm -           $disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"} -           if ($disabledTimers -ne $null) -           { -           foreach ($timer in $disabledTimers) -