If the SQL server 2008 r2 is not connected to the SharePoint 2013 farm , it will not affect the sharepoint 2013 farm when you uninstall the SQL server 2008 r2 from the SharePoint server.
You could uninstall the SQL server 2008 r2 from the SharePoint server as usual.
Then you could follow the steps in the articles below to uninstall SQL server 2008 r2.
As Robert says I easily can implement that utilizing SPTitleBreadcrumb in almost similar manner. Here is my html code in layout page:
That's the actual design of the SharePoint, we can't delete others post from the Micro feed and even i can't delete my own post from the microfeed list. And per my test, I think that Microfeed list can be deleted only by deactivating the SiteFeed feature.
I have completely reconfigured entire SSAs in one step (e.g. moving Search away from a WebFrontEnd server, enabling HighAvailability, ...). This is no problem at all.
The steps are:
Clone your existing topology
Modify the cloned topology
Activate the cloned topology
Optional: Delete the old topology
The entire process is described here in great detail: ...
Go to Subsite with site collection admin access,
Site Settings - > Site Permission -> Check Permission
First thing you should see if user has permission set, if not grant permission from here..definitely you are missing something very basic because it should work without issue.
You can troubleshoot as following:
Deactivate and re-activate the publishing feature and check again.
Go to SharePoint Designer to open this top level site->Lists and Libraries, check if you can view the Pages library.
If you can view the Pages library in SharePoint Designer, try to deactivate the publishing feature, delete the Pages library in SharePoint ...
QueryText is always wild card if you are not specifying any column , it just check for 'Share' keyword in your content and if found will return result, not sure why you need wild card. Wildcard(*) only make sense when you are search values for a particular property.
You can add a * for suffix wildcard matching like below. last one is for phrase search so ...
You need to use PowerShell remoting. Have a look at this: https://www.howtogeek.com/117192/how-to-run-powershell-commands-on-remote-computers/
But with the DSC you should thing about how to automate that process. PS itself has an option for the Pull/Push server which is bit limited. I am using Octopus Deploy (it is 3rd Party Product) to deliver my DSC ...
Please do the following steps as below to troubleshoot this issue:
Restart the "SharePoint Server Search 15" service.
Make sure there is enough memory and disk space.
Reconfiguring Content Processing Component, follow the steps as below:
SharePoint 2013 : How to repair a ...