We are pleased to present below all posts tagged with 'script'. If you still can't find what you are looking for, try using the search box.
I know that Office 365 and SharePoint are all that we seem to talk about today on Twitter and everywhere else. But I do still work with some clients using SharePoint on-premises and they needed some help recently. I was finally able to overcome and I want to share my struggle for others to benefit. I’ve seen examples of doing things like this in server-side code but not PowerShell.
If you are still using SharePoint on-premises, then you will almost certainly be using workflows based on the 2010 workflow platform. These would include all of the out-of-the-box workflow reusable templates like Approval and Collect Signatures.
Recently I needed to change the start parameters of a workflow template that was deployed in a site template so there was a copy of the workflow in over 1,000 subsites. Of course I turned to my trusty friend PowerShell.
When you work with SharePoint permissions, you quickly figure out that you want to touch them as little as possible. With a lot of things in SharePoint, permissions inherit top down. So this means that it’s a best practice to always use that inheritance as much as possible. But in today's post, I'll show you how to use PowerShell to change those permissions for all libraries, folders and files in the site!
Welcome back to part 2 of my short series of using AutoSPInstaller to build a 3-tier multiple server SharePoint farm. Last time we looked at all of the work we needed to do to get setup and discussed what our end goal was. Now we can get down to business and start some installation! I’ll walk you through the most critical part – creating your answer file, then the installation itself.
In this 2-part series I am going to take you through all of the necessary steps to use autospinstaller to build a 3 server farm doing remote installations on Windows Server 2012 R2 with SharePoint 2013 recent CU. (When I say all, I am referring to the SharePoint relevant pieces and the autospinstaller.) Continue reading for SharePoint 2013 (2010) installation.
On a recent project, I hit an issue with databases that was interesting. We were restoring a lot of databases over to a development environment from production, as well as the managed metadata database. I had gone through the whole deal, backed up the database in the old server, restored it to the development SQL server, etc. There was an issue with the Managed Metadata service that required to have service application re-created. This lead to a situation where the service application database was unprovisioned, but not deleted.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.