We have so many different ways to achieve something using PowerShell. In this blog post, we’ll have a look at how we can create Site Collections in SharePoint Server using an XML file and PowerShell (of course!) Create the XML file XML (eXtensible Markup Language) files have their syntax, so it’s important to be familiar with it. If you’re not, have a look at the Introduction to XML provided by w3chools.
Fast Site Collection Creation is a new feature in SharePoint 2016, that enables Site Collections to be created in a much faster way that in previous versions. This feature actually uses a copy of a site template which is stored in the content database, with all the site’s features already enabled. If a SharePoint administrator has a requirement for creating 50 Team Sites, enabling Fast Site Collection creation is a time saver in the long run.
Very quick post today. Or rather a tip that I use every time I have a new SharePoint Farm 🙂 When we need to access the Term Store, we need to click on Manage Service Applications, then click on the Managed Metadata Service Application, and then we have access to the Term Store. If we want to access the User Properties, we need to go to the Service Applications, click on the User Profile Service Application, and then select what we wish.
Today is all about SharePoint taxonomy with PowerShell PnP! In a nutshell, taxonomy is a hierarchical group of term sets & terms, that is provided by SharePoint when configuring the Managed Metadata Service Application (MMS). Creation of terms is done via the Term Store in SharePoint Server (when MMS is configured), and is also available in SharePoint Online. For more information about SharePoint taxonomy, get started with the following links:
SQL Aliases are optional (but recommended), and are a great way to configure your SharePoint environment. They allow for flexibility in case the SQL instance is changed, or the server names/IPs change then it’s possible to only “re-point” to the new servers. This way, there’s no need to reinstall SharePoint for the new server/instance. SQL Aliases are configured on each SharePoint Server. This is very important to remember! Let’s dive in and configure our aliases.
PowerBI itself comes into multiple flavors, and also carrying a few types of configuration along with it. Especially with Office 365. In this blog post, we’ll look at adding (linking) PowerBI Pro to an Office 365 tenant, but we should also go through a bit of description. PowerBI flavors As mentioned previously, PowerBI options and features vary depending on the version we choose: PowerBI free, PowerBI Pro, and PowerBI Premium.
Adding Visio Pro Online to an Office 365 tenant is done the same way as it is for Project Pro Online. So we are going to follow the same process, which is (again) pretty straight forward. Comparison If you don’t know which Visio Online flavor you need, the Compare Visio Options page will help you decide. Connect to Office 365 We will connect to the tenant first.
Recently I was browsing the TechNet Forums like I usually do a few times a week, and I’ve seen a question a user was asking, which intrigued me. Quote When we save a subsite as a template, can we re-use it to create a Site Collection? I thought that was a good question, especially in SharePoint Online (where things are a bit “restricted”), and I’ve never had this request either so… What’s the best way to know if that’s possible?