Per definiton: „Use the Feature Delegation page to configure the delegation state of IIS Manager features for sites and applications on your web server. When you configure the delegation state of a feature from IIS Manager, you specify whether the feature’s related configuration section is locked or unlocked in the server-level configuration files (ApplicationHost.config and root Web.config) for IIS 8.5. When you lock a feature, configuration can only be read and written in the server-level configuration file for that feature. However, you can unlock a feature when you want configuration to be read and written in lower-level configuration files, such as a Web.config file in your site or application.”
It happened once that i needed to provision a Sharepoint 2013 farm including MS SQL Server Reporting Services (SRSS). I had some issues – maybe you found this post ‘cos of that – which i would also share and give a hint on the solution.
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 security is important; working for a huge company sometimes causes problems. You get less right, because of the security. If you a normal user, and you would like to check if one of the user enabled for OCS without Admin rights or Universal Server Administrator right. A normal domain user can check it, because the AD readable for all AD users.