My first post of the year, and it’s starts with a couple of Q&A’s.
Q: Where is the IIS administration.config file located?
A: It is under System32\inetsrv\config folder.
Note, this file can’t be edited using a text editor of any sort. It can be edited using code, the ServerManager class.
The ServerManager class requires the Microsoft.Web.Administration.dll
Q: Where is the Microsoft.Web.Administration.dll located?
A: It is under System32\inetsrv folder.
Ok, if this starts happening to you, then check the AAM entry and your IIS bindings. In my case, we had earlier changed a name resolution in DNS, I then proceeded to update AAM to include this new name. Tested it by connecting to the site, opening document etc etc and everything worked as intended.
Sadly, we started to get the mentioned error. After checking DNS and AAM again, it then dawn on me that I had not included this new name entry in my IIS Site bindings. Once I set this, the error disappeared with no IISReset required.
The most annoying thing has kept happening this whole week. I kept getting Http Error 503 Service Unavailable every single time I try to access a site after provisioning it. I double checked to make sure the internal firewalls were turned off. I then proceeded to check that the ports used were available and listening.
Doing a Bing search I came up with tons of post relevant to the identity account used on the application pool. I went through every single one of the suggestions but came up blank. I finally found this, and gave it a go. The post basically suggest disabling IPv6 on your server. It worked for me, and I hope it helps you as well.
Installing a Web Server role via-Server Manager is a perfectly simple task. However, how do we determine which modules and dependant features would be required? This is the part that can be tricky.
Some administrators prefer to install the Application Server role and be rid of hassles. A process which is perfectly acceptable, but not something I quite agree with. Besides, in the context of security “less is always more” or should I say safer.
Below is a list of modules that I find to be “just nice”, hopefully it can be used as a guide going forward, for your SharePoint setup.
- Static Content (Common HTTP Features) – allows SharePoint to publish static web pages.
- Default Document (Common HTTP Features) – enables the configuration and return of a page automatically that is not explicitly requested through a SharePoint site url.
- Directory Browsing (Common HTTP Features) – not required under normal circumstances, but it does allow for the browsing of a SharePoint site directory.
- ASP.NET (Application Development) – a module that will be required by your SharePoint developers. Features include support for database access, security etc etc.
- .NET Extensibility (Application Development) – programming framework that can be used to perform modifications to IIS functionality. Also shares dependant features with ASP.NET module.
- ISAPI Extensions (Application Development) – supports dynamic web content development using ISAPI. Also shares dependant features with ASP.NET module.
- ISAPI Filters (Application Development) – custom code that can be development to process specific web request. Also shares dependant features with ASP.NET module.
- HTTP Logging (Health and Diagnostics) – provides logging of SharePoint site activity. The most basic form of logging in IIS.
- Logging Tools (Health and Diagnostics) – Provides simple utilities for managing SharePoint site logs.
- Request Monitor (Health and Diagnostics) – not really required, but it does provide the ability to monitor SharePoint site health.
- Basic Authentication (Security) – Provides Basic authentication for SharePoint.
- Windows Authentication (Security) – Provides NTLM integrated authentication for SharePoint.
- Request Filtering (Security) – Screens and filters all incoming request into server. Also shares dependant features with ASP.NET and .NET Extensibility.
- Static Content Compression (Performance) – Functionality that reduces bandwidth by compressing static content before transmitting it to client. It also stores content that is accessed frequently, thus improving performance.
- Dynamic Content Compression (Performance) – Can assist in reducing bandwidth, although it places a high overhead on the server processor. Each SharePoint environment will vary, and it will be wise to pay close attention to the content that is being transmitted before enabling or disabling this module.
- IIS Management (Management Tools) – Installs IIS Management console, for easy GUI management.