We recently had to find out which sites were using InfoPath forms across the estate, with the simple script below, it exported all sites and location where an #InfoPath form was present. The script writes out to a CSV file. Edit the items within bold
If you quickly want to add users to site collection admins across #SharePoint run the following PowerShell script. The script will ask you to fill in the Domain\User and also the Web Application in which you want to run against.
Edit the URL at the bottom
Recently I had an issue where my #SharePoint list #workflows wouldn’t run and were in suspended state. The reason for the suspended state was an item already existed in the destination folder where the workflow was supposed to move the file to.
I’ve finally taken the plunge into the unknown for me, an all singing, all dancing NAS box. This comes in the form of the Synology DS918+
Going back to the hostname site collection creation and creating the default user groups, there is another way in which the groups can be created if you didn’t want to use PowerShell. This is done by simply typing http://sitename/_layouts/15/permsetup.aspx From here you can create the default groups from the web interface.
If you have created a hostname site collection via PowerShell you may have noticed that the default user groups “Site Owners, Site Visitors, Site Members” aren’t actually there. This is because when the site is created with PowerShell these groups aren’t actually created.
A hostname site collection is a nice looking URL rather than your boring silly long ones that are created as standard within your SharePoint farm. Example: Standard: http://sharepoint/sites/something Hostname: http://something
The below will allow you to copy across item information from one SharePoint list and display them within a task list for approval. You will need to make sure you have “jquery-3.2.1.min.js” somewhere on your SharePoint site.