In this short article, I will tell you about Shared Configuration in IIS. Before we start, first thing that you should do is backup the following configuration files for your sites on both servers, administration.config and applicationHost.config.The default location for that files are in C:\Windows\System32\inetsrv\config.  If you got an error you can use the files to restore the configuration back to its original state. 

1. Now, from server1 in IIS Management chopse the server name and on the right Window pane under Management click the “Shared Configuration” icon like the picture below:

2. Next, on the Actions pane select “Export Configuration” as shown on the picture below:

Then Select the location to store the files and provide an Encryption key password (keep track of it for use on server2)

3. Copy the files to a folder location on server2 (administration.config and applicationHost.config)
4. Now, Open the Shared Configuration icon in IIS Manager for server2
5. Tick on the box to “Enable shared configuration”
6. Now, Enter the path to the exported configuration files on server2
7. Next step Click Apply and input the Encryption key password.  You’ll receive the message below.

8. Close and open up IIS Manager, choose the server name, click the Management Service icon and choose Restart under the Actions menu (you may additionally choose to run iisreset at the command line)

Now make sure the sites are in place. you'll disable “Shared Configuration” if everything is setup properly. when you go to disable “Shared Configuration” you will be prompted to choose “Yes” if yo wish to copy the new configuration back to the default folder location or select “No” if you do not want to import the new configuration however instead revert back to your original configuration. Select “Yes” to overwrite your original file configuration with the new configuration.  Check the Event Viewer to assist troubleshoot any problems you run into with the sites.

HostForLIFE.eu IIS 8.0 Hosting
HostForLIFE.eu is European Windows Hosting Provider which focuses on Windows Platform only. We deliver on-demand hosting solutions including Shared hosting, Reseller Hosting, Cloud Hosting, Dedicated Servers, and IT as a Service for companies of all sizes. We have customers from around the globe, spread across every continent. We serve the hosting needs of the business and professional, government and nonprofit, entertainment and personal use market segments.

First, you may have to be compelled to purchase a 2048-bit SSL certificate(s) and configure IIS. you'll got to purchase a multi-domain or wildcard certificate based mostly upon your wants. There are free certificates obtainable for bloggers and non-commercial organizations.

Create certificate request file
First we want to create a certificate request file. Once making the certificate request, we'll copy/paste the contents of the certificate request file into the SSL provider web site. Once their verification we'll be ready to download the resulting SSL certificate files.

Create Certificate Request
On the primary screen of the wizard you may have to be compelled to give the details for your organization. The important part is to specify the Common name as your fully qualified domain name (FQDN) — together with appropriate subdomain. Here i'm simply using “www.example.com”.

Next, make certain to specify the bit length of your certificate to 2048. supported todays standards, this is often the length to decide on. Any shorter isn't secure enough, and any further isn't necessary and can produce unnecessary cpu cycles on your server.

The next step is to specify the file name for the certificate request file. I store all of my SSL certificates and associated files in folder on the C drive: C:\ssl. Then, merely click the finish button.

We will currently open up the resulting .txt file and copy and paste the contents into the SSL provider’s web site. however and wherever you do this can rely on the SSL provider you selected.

Install certificate in IIS
Once you have got completed the certificate signing request, your SSL supplier can notify you once the SSL certificate is prepared and accessible for you to transfer. After downloading the SSL certificate file (csr), complete the certificate request in IIS.

To complete the certificate request, choose the SSL certificate file (crt) and enter the Friendly name. The friendly name is for you to understand that SSL certificate is that in IIS. For best practices, I continuously name these to match the absolutely qualified domain name.

Add HTTPS Binding
The last step is to bind our web site in IIS to the HTTPS port (443). Note that the common name (FQDN) for the certificate should match the host name for the location that you just are configuring.  To get started right click on the site in IIS and choose Edit Bindings.

Then click the Add… button to add a replacement binding. we'll choose https because the kind, the suitable IP address on the server to bind the web site to, then choose the SSL certificate file and click on OK. you're now serving the web site using HTTPS. move and open your browser and enter the full domain with the https:// protocol specification to look at the location a new HTTPS.

HostForLIFE.eu IIS 7.5 Hosting
HostForLIFE.eu is European Windows Hosting Provider which focuses on Windows Platform only. We deliver on-demand hosting solutions including Shared hosting, Reseller Hosting, Cloud Hosting, Dedicated Servers, and IT as a Service for companies of all sizes. We have customers from around the globe, spread across every continent. We serve the hosting needs of the business and professional, government and nonprofit, entertainment and personal use market segments.

HostForLIFE.eu, a leading web hosting provider, has leveraged its gold partner status with Microsoft to launch its latest Sitefinity 7.3 Hosting support.

European Recommended Windows and ASP.NET Spotlight Hosting Partner in Europe, HostForLIFE.eu, has announced the availability of new hosting plans that are optimized for the latest update of the Sitefinity 7.3 hosting technology.

HostForLIFE.eu supports Sitefinity 7.3 hosting on our latest Windows Server and this service is available to all our new and existing customers. Sitefinity 7.3 offers a natural extension to all customer SharePoint workflows and wrap a compelling presentation around client core business documents. Contextual task-oriented approach to organizing documentation on any topic.

HostForLIFE.eu hosts its servers in top class data centers that is located in Amsterdam, London, Paris and Seattle (US) to guarantee 99.9% network uptime. All data center feature redundancies in network connectivity, power, HVAC, security, and fire suppression. All hosting plans from HostForLIFE.eu include 24×7 support and 30 days money back guarantee. All hosting plans from HostForLIFE.eu include 24×7 support and 30 days money back guarantee. The customer can start hosting our Sitefinity 7.3  site on our environment from as just low €3.00/month only.

Sitefinity 7.3 is a Web Content and Experience Management Platform that enables business to engage, convert and retain customers through multiple channels. Sitefinity 7.3 is the only truly mobile web content management on the market that supports all three mobile strategies out of the box – responsive design, mobile apps and mobile sites.

Sitefinity 7.3’s intuitive user interface delights both developers and business users alike, making it a more efficient environment to get more work done faster. There’s no long training required, so even new non-technical users will be up and running in no time. Because it’s built on a modern code-base, Sitefinity is best equipped to meet the long term needs of today’s expanding businesses, including tackling challenges like mobile, ecommerce, multisite management, content personalization, and so much more.

HostForLIFE.eu is a popular online Windows based hosting service provider catering to those people who face such issues. The company has managed to build a strong client base in a very short period of time. It is known for offering ultra-fast, fully-managed and secured services in the competitive market. Our powerful servers are specially optimized and ensure Sitefinity 7.3 performance.

For more information about this new product, please visit http://hostforlife.eu/European-Sitefinity-73-Hosting

About HostForLIFE.eu :
HostForLIFE.eu is awarded Top No#1 SPOTLIGHT Recommended Hosting Partner by Microsoft (see http://www.asp.net/hosting/hostingprovider/details/953). Our service is ranked the highest top #1 spot in several European countries, such as: Germany, Italy, Netherlands, France, Belgium, United Kingdom, Sweden, Finland, Switzerland and other European countries. Besides this award, we have also won several awards from reputable organizations in the hosting industry and the detail can be found on our official website.HostForLIFE.eu Proudly Launches Sitefinity 7.3 Hosting

After following several posts and tutorials on properly fixing IIS dynamic compression for JSON responses, i used to be still reaching a dead finish. For no matter reason, my responses were still uncompressed. Apparently, using the NetworkService account doesn’t perpetually play nicely with static or dynamic content compression.

The NetworkService account doesn’t have permission to the IIS Temporary Compressed Files folder, preventing it from writing and reading out compressed streams. The best thanks to get around this can be by adding the NetworkService account to the IIS_IUSRS group (which already has permissions to the IIS temporary folder).

1. First step, Open the local Users and groups management console.

2. Next, Select Groups from the sidebar.

3. Now, open the IIS_IUSRS property window.

4. Click Add, then enter Network Service as the user. Make sure to have your nearby workstation as the area, then Check Names to make certain you entered everything effectively. Click OK.

5. Next, Click OK on the IIS_IUSRS property window.

6. Close the Local Users and Groups management console
7. Restart IIS

Dynamic compression should be working now!

If you've setup another IIS site and application pool and using a .NET application, you may run into this problem:
HTTP Error 500.21 – Internal Server Error Handler “ExtensionlessUrlHandler-Integrated-4.0″ has a bad module “ManagedPipelineHandler” in its module list.

And here is the solution to solve this error:
First, Run the "aspnet_regiis.exe" program from Command Line (in the Command Prompt) and type this syntax:
run %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i

Note: if your computer is 64 bit, then use the following:
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i
Restart IIS.

If above solution doesn’t work for you, try the other method below:
Click Start -> All Programs -> Accessories -> Run
In the Open textbox paste in the following line

For silent repair on 32 bit computer with .Net Framework version 4.0.30319 use:
%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart

For silent repair on 64 bit computer with .Net Framework version 4.0.30319 use:
%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart

Click OK to start the repair
After, the repair ran for a few minutes, restart IIS.

Today while taking a shot at vista IIS 7.5 and I was attempting to erase one of module named as CustomErrorModule for Default Web Site and quick I was informed with this decent lapse.

Also this appear to be occurring just with Modules which are recorded as Native. I had the capacity erase Managed module without any problem.nothing was accounted for under framework & application occasion viewer logs. Arrangement was to go at Root level Modules designs and select the required native module and Unlock it.

The  IIS 7.5 Native Modules seem to be locked by default and same would be valid incase of appcmd tool.

C:\Windows\System32\inetsrv>appcmd unlock config /section:httpErrors
Unlocked section "system.webServer/httpErrors" at configuration path "MACHINE/WEBROOT/APPHOST".

Happy Coding!

European leading web hosting provider, HostForLIFE.eu announced support for DotNetNuke 7.3.4 hosting plan due to high demand of DotNetNuke CMS users in Europe.

HostForLIFE.eu proudly launches the support of DotNetNuke 7.3.4 on all our newest Windows Server  environment. HostForLIFE.eu DotNetNuke 7.3.4 Hosting plan starts from just as low as €3.00/month only and this plan has supported ASP.NET 5, ASP.NET MVC 5/6 and SQL Server 2012/2014.

DotNetNuke 7.3.4, as well known in the web industry and familiar among .NET developers, is a Web Content Management System (WCMS) based on Microsoft .NET platform. It is an excellent open source software that you can use to manage your website without having much technical knowledge.

HostForLIFE.eu clients are specialized in providing supports for DotNetNuke for many years. We are glad to provide support for European DotNetNuke 7.3.4 hosting users with advices and troubleshooting for our clients website when necessary.

DNN 7.3.4 is a smaller maintenance release than normal and is focused on addressing the most serious platform issues. DNN 7.3.4 addresses a number of platform issues and should be the last release before DNN 7.4.0. DNN 7.3.4 added ability to save localized lists to resource file, added method to remove all subscriptions from a ContentItem, fixed issue where AUM was not correctly handling 301 redirects, Fixed issue where popup iframe is not initialized correctly and fixed issue where multiple region/country controls in a profile did not work correctly.

DotNetNuke 7.3.4 will be a great content management system that support many advance website features such as blogs, forums, e-commerce system, photo galleries and more. DotNetNuke 7.3.4 is a great platform to build your web presence with. HostForLIFE.eu can help customize any web software that company wishes to utilize.

Further information and the full range of features DotNetNuke 7.3.4 Hosting can be viewed here http://www.hostforlife.eu/European-DotNetNuke-734-Hosting

About Company
HostForLIFE.eu is European Windows Hosting Provider which focuses on Windows Platform only. HostForLIFE.eu deliver on-demand hosting solutions including shared hosting, Reseller Hosting, Cloud Hosting, Dedicated Servers, and IT as a Service for companies of all sizes.

HostForLIFE.eu is awarded Top No#1 SPOTLIGHT Recommended Hosting Partner by Microsoft (see http://www.asp.net/hosting/hostingprovider/details/953). Our service is ranked the highest top #1 spot in several European countries, such as: Germany, Italy, Netherlands, France, Belgium, United Kingdom, Sweden, Finland, Switzerland and other European countries.

At this post, I will explain you how to disable Client Certificate Revocation (CRL) Checking in IIS 8. The Public Key Infrastructure (PKI) is an important because certificates are used in so many scenarios when testing Microsoft products and technologies. And one of the trickiest parts of PKI is availability of the Certificate Revocation List (CRL). That is because some solutions require a successful CRL check and some don’t. The problem is that Microsoft documentation doesn’t always make it clear which is the case for a particular scenario, so you end up having to guess whether it is required or not (or worse, going through the entire configuration process and finding that it doesn’t work).

When performing on a system with no internet access it's vital to confirm that CRL checking is disabled. If not disabled you'll always receive a 403.13 error once coming.

And here is the code to Show All Binding and Their Verify Client Certificate Revocation Setting:
netsh http show sslcert

Code for Delete SNI Binding:
netsh http delete sslcert hostnameport=www.yourwebsite.com:443

This is code for Add SNI Binding:
netsh http add sslcert hostnameport=www.yourwebsite.com:443 certhash=78dd6cc2bf5785a123654d1d789c530fcb5687c2 appid={3cc2a456-a78c-2cc9-bcc9-782bc83bb789} certstorename=My verifyclientcertrevocation=disable

Hope this tutorial works for you!

By default, IIS can not upload large file size to the web server. For IIS 6 and IIS 7, the default maximum file size for upload is 4 MB and 28.6 MB respectively. IIS 7 will throw a 404 error (HTTP Error 404.13 - CONTENT_LENGTH_TOO_LARGE) if user upload file larger than 30MB. In order to allow for larger file size uploads, a few server changes are required.  You have three steps to increase the file upload limit:

1. Modify the maxAllowedContentLength setting in the web.config
You could increase the max file size by modify the maxAllowedContentLength setting in the web.config file: <system.webServer>
  <security>
    <requestFiltering>
      <requestLimits maxAllowedContentLength="2147483648" />
    </requestFiltering>
  </security>
</system.webServer>

With that maxAllowedContentLength, users can upload files that are 2 GB in size. This setting will work right away without restart IIS services.

2. Edit the request filtering feature settings and therefore the request limits using IIS manager

• Open IIS Manager.
• Choose the web site that you simply wish to configure.
• Check that you're in features view per the button at the lowest of the manager.
• Choose Requests Filtering and open it by double-clicking the icon. The Request Filtering pane displays.
• From the Actions pane on the right hand side of the screen click Edit Feature Settings... link. The Edit Request Filtering Settings window displays.
• In the Request Limits section, enter the appropriate maximum allowed content length (Bytes) then click the OK button.
• Next, Restart IIS.

3. Manually edit the ApplicationHost.config file

• Click start. In the start Search box, type notepad. Right-click notepad, and so click Run as administrator.
• On the File menu, click Open. within the File name box, type %windir%\system32\inetsrv\config\applicationhost.config, and so open.
• Within the ApplicationHost.config file, find the  node.
• Take away the maxAllowedContentLength property. Or, add a value that matches the scale of the Content-Length header that the client sends as a part of the request. By default, the worth of the maxAllowedContentLength property is 30000000.
  For instance, modify the subsequent configuration information within the  section.

  <requestLimits maxAllowedContentLength ="<length>" />
  

• Finally, Save the ApplicationHost.config file.

European leading web hosting provider, HostForLIFE.eu announced the support for WordPress 4.0.1 hosting plan due to high demand of WordPress 4.0.1 users in Europe. HostForLIFE.eu is a popular online WordPress hosting service provider catering to those people who face such issues. The company has managed to build a strong client base in a very short period of time. It is known for offering fast, fully-managed and secured services in the competitive market.

HostForLIFE.eu hosts its servers in top class data centers that is located in Amsterdam (NL), London (UK), Paris (France) and Seattle (US) to guarantee 99.9% network uptime. All data center feature redundancies in network connectivity, power, HVAC, security, and fire suppression. All hosting plans from HostForLIFE.eu include 24×7 support and 30 days money back guarantee. All hosting plans from HostForLIFE.eu include 24×7 support and 30 days money back guarantee. The customer can start hosting our Wordpress 4.0.1 site on our environment from as just low €3.00/month only.

WordPress 4.0.1 patches a critical cross-site scripting vulnerability affecting comment boxes on websites running the content management system software. An attacker would need only to inject malicious JavaScript into a comment that would infect a reader viewing it on the webpage or an admin in the management dashboard.

The update also addresses three other cross-site scripting vulnerabilities, a cross-side request forgery flaw, a denial-of-service bug related to password checks, server-side request forgery issues, and what WordPress called “an extremely unlikely hash collision” that could lead to account compromise. WordPress said it also invalidates links in a password reset email if the user remembers our password and logs in and changes our email address.

WordPress 4.0.1 addresses an additional eight security issues, including three other XSS vulnerabilities that can be exploited by a contributor or an author, a cross-site request forgery (CSRF) that can be leveraged to trick a user into changing his/her password, and a denial-of-service (DoS) bug. HostForLIFE.eu is a popular online Windows based hosting service provider catering to those people who face such issues. The company has managed to build a strong client base in a very short period of time. It is known for offering ultra-fast, fully-managed and secured services in the competitive market. Our powerful servers are specially optimized and ensure WordPress 4.0.1 performance.

For more information about this new product, please visit http://hostforlife.eu/European-WordPress-401-Hosting

About us:
HostForLIFE.eu is awarded Top No#1 SPOTLIGHT Recommended Hosting Partner by Microsoft (see http://www.asp.net/hosting/hostingprovider/details/953). Our service is ranked the highest top #1 spot in several European countries, such as: Germany, Italy, Netherlands, France, Belgium, United Kingdom, Sweden, Finland, Switzerland and other European countries. Besides this award, we have also won several awards from reputable organizations in the hosting industry and the detail can be found on our official website.