This post of is part of my Install SharePoint 2013 Three-tier Farm project.
In this post I’ll show my best practice for an new SQL Server to run SharePoint properly.
Let’s get started with local user rights.
So far Micosoft doesn’t offer the same amount of cmdlets to manage a SharePoint Online instance as they do for an on-premise installation.
As many other SharePoint administrators I can’t wait to get new cmdlets. Luckily Jeffrey Paarhuis recently published a project on Microsoft Codeplex and showed how simple it is to manage a SharePoint installation just with client-side libraries and functions.
Seconds later I’ve migrated his functions into my project: https://codeberg.org/janikvonrotz/PowerShell-PowerUp
I’ll introduce you the new:
Recently I’ve started developing with Node.js. As a beginner I had to set up an IDE which meets my requirements such as debugging code. I’ve tried several IDE’s such as Microsofts’s WebMatrix or Eclipse Node.js extension. But all of them literally sucked, they were are a pain to install or didn’t work properly.
Luckily I came along this project: https://github.com/node-inspector/node-inspector
Right now I’ve led the company internal SharePoint projects for about one year.
I’ve experienced that most of the SharePoint project leaders struggle with same problems.
In order to save you from this unnecessary experience I’ve shared my most important success factors of a SharePoint project:
Recently I’ve change the url for one of my GitHub projects.
As you might know, I’ve used this url in several posts. In order to make this obsolete links I have to replace them in every posts.
This post of is part of my Install SharePoint 2013 Three-tier Farm project.
A clean SQL Server maintenance plan should include three processes, backup, integrity check and index optimize.
You could simply set up a SQL Server maintenance plan within the SQL Server management studio. But be aware that there are better solutions, E.g. Ola Hallengren’s SQL Server Maintenance Solution is my absolutely favourite.
I’ve tried many ways to assign permissions for an Active Directory group on a Exchange (2010) mailbox, but it’s simply not possible.
Fortunately nothing’s impossible with PowerShell.
The following script can handle this issue by:
This is an simple example for an Apache vHost SSL vHost configuration:
<VirtualHost 192.168.0.1:443>
DocumentRoot /var/www/
SSLEngine on
SSLCertificateFile /path/to/certificate.crt
SSLCertificateKeyFile /path/to/keyfile.key
</VirtualHost>