Fixing SharePoint

<<  Back to main post on Search Service Application Before After Script !...Adding a Content Processing Component...! Step 1 : Get Search Service Instance and Start on New Index Server $ssi = Get-SPEnterpriseSearchServiceInstance -Identity "PROD-SPAPP02" In case your Search Service Instance is not Online, run below commands and wait Start-SPEnterpriseSearchServiceInstance -Identity $ssi Get-SPEnterpriseSearchServiceInstance -Identity $ssi Step 2 : Clone Active Search Topology $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone – SearchTopology $active Step 3 : Add New Content Processing Component New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $clone -SearchServiceInstance $ssi Step 4 : Activate the Cloned Search Topology Set-SPEnterpriseSearchTopology -Ident...

<<  Back to main post on Search Service Application Before After Script Step 1 : Get Search Service Instance and Start on New Crawl Server $ssi = Get-SPEnterpriseSearchServiceInstance -Identity "PROD-SPAPP02" In case your Search Service Instance is not Online, run below commands and wait Start-SPEnterpriseSearchServiceInstance -Identity $ssi Get-SPEnterpriseSearchServiceInstance -Identity $ssi Step 2 : Clone Active Search Topology $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone – SearchTopology $active Step 3 : Add New Crawl Component New-SPEnterpriseSearchCrawlComponent -SearchTopology $clone -SearchServiceInstance $ssi Step 4 : Activate the Cloned Search Topology Set-SPEnterpriseSearchTopology -Identity $clone Step 5 : Review new topology Get-SPEnterpriseSearchTopology -Acti...

Hi There...! Bad news for SharePoint admins. Microsoft removed the UI option for adding/removing/updating the SharePoint search topology in SharePoint 2013. It can be done now only and only using PowerShell. :-/ Microsoft describes the PowerShell commands here  to modify it but i could not find it much arranged in first look. However i found a very nice blog by Steve Mann where he described the things very well and saved a lot of hours of SharePoint admins around the globe. I'll try to add more light on his article to making this a little more easy. Here is a before and after of what my farm was initially and what i had after the PowerShell work. Note: The account logged-in on PowerShell (or the server you are logged in and running SharePoint Management Shell) must have db_owner permissions for Search Admin DB in SQL. Otherwise it could give you error in PowerShell. Before After Here are the one by one article to follow. 1. Addin...

<< Back to  main post on Search Service Application  Before After Script Step 1 : Get Search Service Instance and Start $ssi = Get-SPEnterpriseSearchServiceInstance -Identity "PROD-SPAPP02" In case your Search Service Instance is not Online, run below commands and wait... Start-SPEnterpriseSearchServiceInstance -Identity $ssi Get-SPEnterpriseSearchServiceInstance -Identity $ssi Step 2 : Clone Active Search Topology $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone – SearchTopology $active Step 3 : Add New Admin Component New-SPEnterpriseSearchAdminComponent -SearchTopology $clone -SearchServiceInstance $ssi Step 4 : Activate the Cloned Search Topology Set-SPEnterpriseSearchTopology -Identity $clone You are Done...!

Hey Mates, Is your SharePoint 2013 is behaving slow even after a new and fresh installation? This post may help you to find one of its root cause and the fix. I have just installed a fresh copy of SharePoint 2013 in my farm and everything seems to be working perfect. No customizations no other custom solutions, just a very fresh out of the box installation of SharePoint 2013. I have used different service accounts for different purposes like Search Service, User Profile Service, Distributed Cache Service. Noticed the BOLD? The reason i bold  Distributed Cache Service is, it was the reason in my case for slowness in farm and by default SharePoint 2013 configures this service using the same account you have configured the farm, in most cases its the Domain\SPFARM account. And later on SharePoint complains in Health Analyzer that you are using the same account for other services (in current case for Distributed Cache Service) which you are using to run ShareP...

There are two ways to set a failover SharePoint environment. This is also known as SharePoint disaster recovery plan. In case your farm goes down, you should have options to make it up in few seconds, minutes, hours or days depending on the approach which you select. There are three types of standby  plans in SharePoint. The time and immediate effort to get a replacement farm up and running defines the standby type. Cold standby. A secondary data center that can provide availability within hours or days. Warm standby. A secondary data center that can provide availability within minutes or hours. Hot standby. A secondary data center that can provide availability within seconds or minutes. Here we are discussing the Hot standby plans. The first approach, I consider it Hot standby because it immediately shifts to the secondary node of SQL for the desired database in few seconds only without engagement of any team member i.e. SharePoint, SQL or Network guys. This is less expensi...

Below are the top levels steps that should be performed to move all SharePoint 2013 databases as recommended by MSFT . 1.        Prepare the new database server i.e. physical resources, SQL server, User Logins and permissions. 2.        Close all open SharePoint Management Shell windows, stop all SharePoint and IIS related services. 3.        Detach the databases from the current SQL Server instance. 4.        Copy all files that are associated with the databases to the new destination server that runs SQL Server. 5.        Attach the copied databases to the new SQL Server. 6.        Go to new SQL server to confirm TCP/IP port and create an Alias for new SQL server using the same port on all WFE's and APP servers. 7.        Start all SharePoint and IIS related s...