Category | PowerShell

One of the most common problems I see in a client built SharePoint environment is multiple site collections comingled in the same content database.  While this isn’t the end of the world, it’s a problem because SLAs, security, and even back strategies are often assigned to specific databases based upon the needs of the users that will be using the site collections hosted in each database.  If a site collection is not hosted in the database that the admin intended because SharePoint simply picks the first available content database with room  the administrator may unwittingly...

---

I have a client who could no longer moves sites using the SharePoint content organizer due to the fact that the enterprise features were enabled, with the enterprise features enabled on all sites, the Drop Off Library prevents sites from being moved.  Unfortunately, simply disabling the Content Organizer feature does not correct the problem, you have to actually delete the library. Problem You can’t delete the Drop Off Library even after you disable the Content Organizer feature. Solution Use powershell to disable the Content Organizer feature, allow deletion of the Drop off Library, and then...

---

Problem When you run powershell on your server you get the following error: The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.   Solution Make sure the logged in user has rights to the SharePoint_Configuration database SharePoint_Shell_Access DB_owner (try reducing the privileges after you get it working in order to support “least privileges”

---