Health Analyzer does a great job warning you about possible problems on your platform, however it is extremely hard to stay on the good side (meaning it does not reward you with a red bar in Central Administration) without turning off a couple of rules.
I met with the Drives used for SQL databases are running out of free space message a few times and the other day reading the official documentation and feeling a bit confused and disappointed I decided to check out what this is about under the hood.
Recently I tried to install SharePoint 2013 in my test environment based on the multiple servers for a three-tier farm scenario, where my SQL Server is on another machine and I got the following error during SharePoint 2013 Products Configuration Wizard:
Failed to create the configuration database
Exception: Microsoft.SharePoint.SPException: This SQL Server instance does not have the required “max degree of parallelism” setting of 1. Database provisioning operations will continue to fail if “max degree of parallelism” is not set 1 or the current account does not have permissions to change the setting. See documentation for details on manually changing the setting.
I encountered this during farm creation on the first SharePoint server installation.
In my test environments I always have to create a couple of users to be able to do performance or functionality tests. Powershell really helps me with this task and I just want to archive this for later.
In the next few paragraphs I show you my method to create hundreds of test users on Windows Server 2012 with Powershell.
Back in time when I had to install additional Windows Components on a 2003 Server the Windows Comopnents Wizard asked me to insert the install disk or point to a folder which contains the install files. In Windows Server 2008 this was changed and all files were copied to the C:\Windows\WinSxS folder so when I decided to install a feature or a role all files were already on the machine. Unfortunately these files cannot be removed but in Windows Server 2012 you have this option to save space, have smaller server footprint, and even satisfy your security officer: this is called features on demand.
The recycle bin feature in SharePoint 2010 comes handy when any accidental deletion occurs, you can easily move the items back, even your users can restore files from there. It is important to understand that a document’s life does not end when a user deletes it and this can affect the storage behind your SharePoint farm. Therefore the recycle bins during in planning phase are often misunderstood and underestimated (especially when you size storage and set up quotas).