In this post, we're going to be very basic and straight forward few clicks on how to create an dconfigure self-signed certificate in IIS 7 or later.

Steps here mentioned are based on IIS 8, but it would be almost same on IIS 7 as well.

Step 1

To get started open IIS and select Server Certificates feature.

It will display list of all installed Server Certificate on web server.

Step 2

To create new self-signed certificate, click on Create Self-Signed Certificate in action pane.

It will open dialog box where you can specify friendly name for server certificate and certificate store for newly created SSL certificate.

Just specify name of the certificate, certificate store and click on OK. So, you are half way done, you have created Self-Signed Certificate with IIS, but still half way to go. After creating certificate, you need to bind it with websites then only we will be able to browse local IIS website with HTTPS.

Step 3

To bind websites with this certificate, select website in IIS and right click on it and select Edit Bindings.

It will open Site Bindings dialog where we can see binding information for selected websites. By default you will find one HTTP binding listed here.

Step 4

Click on Add button to Add new binding for selected website.

Step 5

Here, select binding type HTTPS and select newly created SSL certificate from drop down and click on OK. And congrats, you have added HTTPS binding to website which uses self-signed certificate in local IIS. To verify open and browse https://localhost.

Hope this quick post would be helpful!

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.

In this post, we will learn how you can use IIS URL Rewrite extensions to redirect domain.com to www.domain.com. IIS URL Rewrite extensions enables web administrator to enforce powerful rules to transform complex URLs into simple and consistent Web addresses. As well it also helps to produce user and search engine friendly URLs.

As you all know that by default, you can access website with or without WWW. For e.g. browsing hostforlife.eu and www.hsotforlife.eu will open same website. This means there are two different web addresses are available for one website and hence website’s SEO ranking will be distributed between these two addresses. To overcome these SEO ranking distribution, we can force all web traffic to redirect either domain.com or www.domain.com. Google web masters tool also allow web master to set preferred domain for indexing website URLs. So conclusion is that redirecting all web traffic to only one primary domain or canonical domain can improve SEO ranking. Just follow these steps with IIS.

Step 1

Connect to website through IIS manager and click on URL Rewrite icon.

Step 2

In Actions pane click on Add Rules.

Step 3

In Add Rules dialog box click you can find several predefined rule template. Click on canonical domain name template under search engine optimization section.

Step 4

It will open dialog box to select primary domain for website. Choose appropriate options.

Step 5

Press ok. You have done it. Now all your web traffic will be redirected to primary domain you have selected. And you can see added rewrite rule in list pane. But just using predefined rule template is not enough for web administrator. We should also dig into rule settings done by this rule template. For examine settings of created rule select rule in list pane and double click on it or click on Edit Rules link in Action Pane.

Step 6

It will open edit inbound rule window. Scroll down to bottom of window. There you will find Action sections. In action sections, there is one drop down named Action Type. Default value of Action Type is redirect. Expand Action Type drop down to see different actions available for this rule.

Step 7

And below action type drop down there is another drop down Redirect Type. Default value of this is Permanent (301). Expand drop down to see list of available other redirect type.

Setting redirection type Permanent (301) will cause to send HTTP 301 status code and then after it will redirect to primary domain. So search engine can index appropriate URLs.

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.

When we publish a website on the internet, typically we record more internet domains (.com, .net, etc.) in order to encourage the maximum possibility that users reach our pages. Having a site that responds to different URL, however, it is not indicated by a point of view of SEO, as it involves a fractionation of the total hit among the various possible addresses, and a best practice is to make sure that all these addresses redirigano to a standard domain name. This process, which is called a URL Canonicalization, can be easily implemented in IIS 7 and above.

First, the initial situation will be similar to that in the figure, that is when we have a Site with binding in a number of hosts that will include various domains, even in the versions with and without "www.". If desired, we can add additional ones through the Bindings option.

With such a configuration, IIS responds to calls in each of these domains, but obviously keeping unchanged the address displayed by the browser. To solve this problem, we can use a form called IIS URL Redirect Module, which can automatically download and install via the Web Platform Installer.

The configuration can be done either by using IIS Manager web.config. In the first case, just double click on URL Rewrite, as shown, to open a mask through which to create our rewriting rules.

From www.testredirect.com to testredirect.com

Once you add a new Blank rule, we must first specify which URLs are to be taken into account by the module applying the rule. This type of setup is indicated by regular expression and, in our case, we will use the pattern (. *) To handle all possible URL.

The second step is to indicate, within the group Conditions, the condition for which the rule will have to act. Therefore, we add a new condition to apply to the host component of the URL and check that does not match the canonical (in our example "testredirect.com"), indicating quset'ultimo through a regex ^ testredirect\.com$.

The last step is to specify the action to be taken (section Action), which in particular will be a type Permanent Redirect to the address shown.

The suffix {R: 1} and the Append flag query string make sure that any file names or query string parameters are appended to the new address so generated.

This configuration can also be set from the web.config section system.webServer:

<system.webServer>
    <modules runAllManagedModulesForAllRequests="true" />
      <rewrite>
          <rules>
              <rule name="RedirectRule" stopProcessing="true">
                  <match url="(.*)" />
                  <conditions>
                      <add input="{HTTP_HOST}" pattern="^testredirect\.com"
                            negate="true" />
                  </conditions>
                  <action type="Redirect" url="http://testredirect.com/{R:1}"
                          appendQueryString="false" />
              </rule>
          </rules>
      </rewrite>
</system.webServer>

From testredirect.com to www.testredirect.com

To redirect reverse, simply change the regular expression and the redirect url in the web.config as in the example below:

<system.webServer>
    <modules runAllManagedModulesForAllRequests="true" />
      <rewrite>
          <rules>
              <rule name="RedirectRule" stopProcessing="true">
                  <match url="(.*)" />
                  <conditions>
                      <add input="{HTTP_HOST}" pattern="^www\.testredirect\.com"
                            negate="true" />
                  </conditions>
                  <action type="Redirect" url="http://www.testredirect.com/{R:1}"
                          appendQueryString="false" />
              </rule>
          </rules>
      </rewrite>
</system.webServer>

Since our rule applies to all the different hosts by canon law, the redirect will be performed automatically for all other domain names (eg. Www.testredirect.net) that we recorded between the bindings of IIS Site.

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.

When a website is particularly popular, it is possible that its contents, for example images, videos and so on in your site, are shown on another website beacuse most of people took those files and linked it to their site. Perhaps without any authorization and permission, you didn't realize about it. In the end, the result is the files will appear on sites that do not belong to us. Maybe this condition is annoying, it will enlarge your expense (bandwidth) of your site. But don't worry, you can have some return in terms of visibility or impressions of the ads especially images and videos that you have in your pages.

Fortunately, using URL Rewrite Module for IIS 7 or above is pretty straightforward to create a rule to handle this problem. All you have to do, once installed, you have to include this section in the web.config:

<system.webServer>
  <modules runAllManagedModulesForAllRequests="true" />
  <rewrite>
    <rules>
      <rule name="Avoid remote linking" enabled="true" stopProcessing="true">
        <match url="(.*)" />
        <conditions>
          <add input="{REQUEST_FILENAME}" matchType="IsFile" />
          <add input="{REQUEST_FILENAME}" pattern="\.(png|jpg)" />
          <add input="{REQUEST_FILENAME}" pattern="blocked\.png" negate="true" />
          <add input="{HTTP_REFERER}" pattern="^http://www\.testredirect\.com/.*$" negate="true" />
        </conditions>
        <action type="Rewrite" url="/blocked.png" appendQueryString="false" />
      </rule>
    </rules>
  </rewrite>
</system.webServer>

As you can see, You can apply the node condition to all requests for files whose extensions are png or jpg (of course you can customize this setting at will). The last condition, in particular, allows you to see through the value of the variable HTTP_REFERER server, if the request was originated by a page that belongs to us or not. If not, the action is designated to perform a rewrite the URL to be processed, by sending the contents of a special image that you have provided (in your case, blocked.png) in a place that originally requested.

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.

In this post, you will see how to install and run Node.js in IIS with IISNode.

Installing Node.js

Firstly, you need to install Node.js engine on server which can be download from http://www.nodejs.org/#download. Installing Node.js engine will enable us to run node.js application on windows server. But still you have to require configuring IIS so it can route .js requests to the Node.js engine. This can be easily done with the help of IISNode module for IIS 7.x. Once you install IISNode module, you can configure web.config file to route .js or particular file to iisnode module. IISNode module can be downloaded from https://github.com/tjanczuk/iisnode/archives/master once you install iisnode, you will able to find IISNode module in IIS Manager under modules.

Get IIS Ready to Run Node.Js Application

IISNode will also install sample application to get started with Node.js. Sample application is copied within IISNode installation directory. If you installed iisnode with default settings, then sample can be found in C:\Program Files\iisnode\www directory. To run this sample application, create new application within default website for e.g. let say nodejsapp which points to sample application directory mentioned above. Now go to http://localhost/nodejsapp/ and you should able to see different sample link on your browser:

Now let examine HelloWorld sample. Go to http://localhost/nodejsapp/helloworld/hello.js to run server side JavaScript with the help of node.js engine.

It looks there are some issue with application pool write permission. There are two temporary workaround to deal with this permission issue. One is disable logging by adding following key in web.config. Another one is create one application pool with identity as LocalSystem and assign that application pool to the nodejsapp application. If you run into a 503 status code with IIS reporting error code 0x5 (ERROR_ACCESS_DENIED), make sure the identity of the application pool running the site that hosts your node.js application has read & execute rights to node.exe on disk. If you are using the default IIS configuration (DefaultAppPool running under ApplicationPoolIdentity), you can set appropriate ACLs on the node.exe by running:

icacls %systemdrive%\node\node.exe /grant IIS_IUSRS:rx

Now you should able to run Node.js sample shipped with IISNode.

IIS 8.0 with Free ASP.NET Hosting
Try our IIS 8.0 with Free ASP.NET Hosting today and your account will be setup soon! You can also take advantage of our Windows & ASP.NET Hosting support with Unlimited Domain, Unlimited Bandwidth, Unlimited Disk Space, etc.

This tutorial will guide you through protecting your server from malicious PHP scripts and also allows you to run multiple sites with different configurations which is imperative in a multiple domain environment for security reasons. To complete this tutorial, you must have working installation of IIS with PHP installed and at least 2 websites.

1. Setting up a php.ini file

Step 1

PHP arrives by default with 2 PHP.ini files. These are overly complex for a new user and ultimately not everything within it is needed. Here, you will use a stripped down version of a php.ini file which I have developed over several years for the “average” setup. Here is a default php.ini file:

; Time Zone
date.timezone = GMT

; Fast CGI fixes for IIS
fastcgi.impersonate=1
cgi.fix_pathinfo=0
cgi.force_redirect=0

; Base directories for htdocs, uploads and sessions
open_basedir = c:\sites\your_website\
;doc_root = c:\sites\your_website\
upload_tmp_dir = c:\sites\your_website\
; Double backslash the session save path. Remember to create the session folder.
; Option only applies when WinCache is not being used
session.save_path = c:\\sites\\sessions\\

; Extension Dir
extension_dir = "./ext/"

; These need disabling for php5.4 as they're deprecated
; You should never need to enable these if your scripts are secure
safe_mode = Off
register_long_arrays = Off
allow_call_time_pass_reference = Off
register_globals = Off

; Logging
log_errors = On
error_log = syslog

; Error Reporting
error_reporting  =  E_ALL & ~E_NOTICE
display_errors = On
display_startup_errors = Off

; Disable functions that could cause a security risk, comma separated
disable_functions = system,shell_exec,exec,escapeshellarg,escapeshellcmd,passthru,proc_ close,proc_ get_ status,proc_ open,proc_terminate

; Memory limits
max_execution_time = 60     ; Maximum execution time of each script, in seconds
max_input_time = 60    ; Maximum amount of time each script may spend parsing request data
;max_input_nesting_level = 64 ; Maximum input variable nesting level
memory_limit = 64M      ; Maximum amount of memory a script may consume (128MB)
post_max_size = 8M

; Sendmail / mail()
SMTP = localhost
smtp_port = 25
;sendmail_from = [email protected]

; File Uploads
file_uploads = On
upload_max_filesize = 100M

; fopen wrappers
allow_url_fopen = On
allow_url_include = On
default_socket_timeout = 10

; Extensions
;extension=php_bz2.dll
extension=php_curl.dll
;extension=php_dba.dll
;extension=php_dbase.dll
;extension=php_exif.dll
;extension=php_fdf.dll
extension=php_gd2.dll
;extension=php_gettext.dll
;extension=php_gmp.dll
;extension=php_ifx.dll
extension=php_imap.dll
;extension=php_interbase.dll
;extension=php_ldap.dll
;extension=php_mbstring.dll
;extension=php_mcrypt.dll
;extension=php_mhash.dll
;extension=php_mime_magic.dll
;extension=php_ming.dll
;extension=php_msql.dll
;extension=php_mssql.dll
extension=php_mysql.dll
;extension=php_mysqli.dll
;extension=php_oci8.dll
extension=php_openssl.dll
;extension=php_pdo.dll
;extension=php_pdo_firebird.dll
;extension=php_pdo_mssql.dll
;extension=php_pdo_mysql.dll
;extension=php_pdo_oci.dll
;extension=php_pdo_oci8.dll
;extension=php_pdo_odbc.dll
;extension=php_pdo_pgsql.dll
;extension=php_pdo_sqlite.dll
;extension=php_pgsql.dll
;extension=php_pspell.dll
;extension=php_shmop.dll
;extension=php_snmp.dll
extension=php_soap.dll
;extension=php_sockets.dll
;extension=php_sqlite.dll
;extension=php_sybase_ct.dll
;extension=php_tidy.dll
;extension=php_xmlrpc.dll
;extension=php_xsl.dll
;extension=php_zip.dll
;extension=php_wincache.dll

; WinCache

; More info http://us2.php.net/manual/en/wincache.configuration.php

; To use these make sure the WinCache DLL is enabled

; Enable WinCache?
; If you disable WinCache be sure to set the session.save_handler to "files"
wincache.fcenabled = 0

; Defines a comma-separated list of IIS web site identifiers where file cache should be enabled or disabled.
wincache.fcenabledfilter =

; Defines the maximum memory size (in megabytes, default 24) that is allocated for the file cache.
; If the total size of all the cached files exceeds the value specified in this setting,
; then most stale files will be removed from the file cache.
wincache.fcachesize = 24

; Enables or disables the file change notification detection functionality.
wincache.fcndetect = 1

; Defines the maximum allowed size (in kilobytes, default 256) for a single file to be cached.
; If a file size exceeds the specified value, the file will not be cached.
; This setting applies to the file cache only.
wincache.maxfilesize = 256

; Enables or disables the opcode cache functionality
wincache.ocenabled = 1

; Defines a comma-separated list of IIS web site identifiers where opcode cache should be enabled or disabled.
wincache.ocenabledfilter =

; Defines the maximum memory size (in megabytes, default 96) that is allocated for the opcode cache.
; If the cached opcode size exceeds the specified value, then most stale opcode will be removed from the cache.
; Note that the opcode cache size must be at least 3 times bigger than file cache size.
; If that is not the case the opcode cache size will be automatically increased.
wincache.ocachesize = 96

; Defines how many files (default 4096) are expected to be cached by the extension, so that appropriate memory size is allocated at the startup time.
wincache.filecount = 4096

; Defines how often (in seconds, default 30) the extension checks for file changes in order to refresh the cache.
; Setting it to 0 will disable the refreshing of the cache.
wincache.chkinterval = 600

; Defines the maximum time to live (in seconds, default 1200) for a cached entry without being used.
; Setting it to 0 will disable the cache scavenger, so the cached entries will never be removed
; from the cache during the lifetime of the IIS worker process.
wincache.ttlmax = 1200

; Defines if caching is enabled when PHP is running in command line (CLI) mode.
wincache.enablecli = 0

; Defines a list of files that should not be cached by the extension.
; The files list is specified by using file names only, separated by the pipe symbol - "|".
; E.g. wincache.ignorelist = "index.php|misc.php|admin.php"
wincache.ignorelist =

; Defines a string that will be used when naming the extension specific objects that are stored in shared memory.
; This is used to avoid conflicts that may be caused if other applications within an IIS worker process tries
; to access shared memory. The length of the namesalt string cannot exceed 8 characters.
wincache.namesalt =

; Enables or disables the user cache functionality.
wincache.ucenabled = 1

; Defines the maximum memory size in megabytes (default 8) that is allocated for the user cache.
wincache.ucachesize = 8

; Defines the maximum memory size in megabytes that is allocated for the session cache.
wincache.scachesize = 8

; Specifies an absolute or a relateve path to the reroute.ini file that contains the list of PHP functions whose
; implementation should be replaced with the WinCache function equivalents.
wincache.rerouteini =

;; ####
;; Don't edit these unless you know what you're doing!
;; ####

; Sessions
; "files" - save to files
; "wincache" - use WinCache
session.save_handler = files
session.use_cookies = 1
session.name = PHPSESSID
session.cache_limiter = nocache
session.cache_expire = 180

; Default MIME-TYPE
default_mimetype = "text/html"

; Allow

Step 2

There are several items that you will need to amend before it is ready for use on your server:

• Copy and paste the text in the box above into a new text file.
• Inside your PHP folder, create a folder called ‘ini’.
• Save the text file inside the ini folder you just created.
•  Rename the file to the name of your website. For example ‘yourdomain.com.ini’.
• Open the file in your favourite text editor.

From here, now you need to change some settings in the php.ini to suit your setup:

1. Change this to your time zone.

date.timezone = GMT

Here is a link to a list of valid time zones: Time Zones. You will need to do this to make sure the time and date is correctly reported to PHP scripts.

2. Change the below paths to the location of your website root folder.

; Base directories for htdocs, uploads and sessions
open_basedir = c:\sites\your_website\
;doc_root = d:\public_html\iisunderground\
upload_tmp_dir = c:\sites\your_website\
; Double backslash the session save path
; Option only applies when WinCache is not being used
session.save_path = c:\\sites\\sessions\\

The session.save_path must have double backslashes, so don’t forget. Also be sure to create the sessions folder. You should not store the sessions folder inside your web accessible folder for security reasons. These directories are used to prevent scripts from accessing locations outside of their web accessible folders. The defined folder is the “lowest” they can go. They can go forward  directories but not backwards beyond this set folder.

3. Change SMTP to the host you wish to use for e-mail.

; Sendmail / mail()
SMTP = localhost
smtp_port = 25
;sendmail_from = [email protected]

Normally this will stay at the default ‘localhost’ if you are using a mail server on your system. Change SMTP port to the port the mail server SMTP service uses. The default is 25 and normally won’t need to be changed. Un-comment sendmail_from (removing the semi-colon) if you intend to use a global address to send mail from. Lots of sites will use [email protected].

4.Change the extennsions.

; Extensions

There are lots of extensions to choose. If you ever find that your scripts tell you an extension or function is not available, you can often un-comment the extension (remove the semi-colon) here, save the file and restart IIS to get it working. The defaults enabled already will get you going for most applications.

WinCache is an extension for IIS that enables caching of PHP scripts. This allows them to run up to 5-10x faster than normal.

To enable WinCache, follow the installation tutorial and then set this extension to ‘1’ (enabled) rather than ‘0’ (disabled):

; Enable WinCache?

; If you disable WinCache be sure to set the session.save_handler to "files"
wincache.fcenabled = 0

The default settings will get you moving. If you ever come back to developing a site, you may need to disable WinCache to avoid the script being cached while you work on it. WinCache is designed for production systems only when using long cache time periods.

2. Configuring IIS to accept the new php.ini

The php.ini is now ready to be configured into IIS.

• Open the IIS Manager from Start > Control Panel / Administrative Tools / IIS Manager.
•  On the left hand side, select your website from the sites list.
• From the icons, select Handler Mappings just as you would for installing PHP.
• Find your php handler mapping in the list and double click it.
• Under the executable box, you will have your PHP executable location. We need to edit it to include your php.ini file:

Example: c:\php\php-cgi.exe|-c c:\php\ini\your_website.com.ini
The '-c' modifier tells PHP to load a custom php.ini file.

• Using the above example, modify it to your PHP location and your php.ini location.
• Once you are done, click OK.

3. Test your configuration

Your modified php.ini is now installed. All that is left to do is test your website to make sure it is working as intended. To do this, create a php file and include the following code:

<?php phpinfo(); ?>

Save it to your web accessible folder and then navigate to it in your browser. If you get something that looks like this, then you have been successful.

For each site you have now or create in the future, follow this process to make sure it has it’s own php.ini file. This ensures it will be secure and if you are hosting others, it makes sure they can’t access other peoples files by locking them down into their own folders.

IIS 8.0 with Free ASP.NET Hosting
Try our IIS 8.0 with Free ASP.NET Hosting today and your account will be setup soon! You can also take advantage of our Windows & ASP.NET Hosting support with Unlimited Domain, Unlimited Bandwidth, Unlimited Disk Space, etc.

In this post, I'm going to show you how to install and use IIS URL Rewrite. The IIS URL Rewrite module may be a better solution than HTTP Redirect in IIS. You can effectively “redirect” from http://domain.com to http://www.domain.com. Of course the URL rewrite has many more uses and features, but I will use it for redirection purposes in this tutorial.

IIS URL Rewrite Installation

To get the below URL Rewrite code to work in IIS, you must first install the URL Rewrite module. The URL Rewrite module is not installed by default. To install the IIS URL Rewrite module: Go Here and click install… Or just click Here. Once installed you may need to reboot.

IIS URL Rewrite after Installation

You can double click and make your URL rewrite rule using the interface, or edit the web.config. See below:

IIS URL Rewrite code in the web.config

IIS URL Rewrite http:// to http://www :

<!--web.config url rewrite-->
  <system.webServer>
      <rewrite>
          <rules>
              <rule name="RedirectToWWW" stopProcessing="true">
                  <match url=".*" ignoreCase="true" />
                  <conditions>
                      <add input="{HTTP_HOST}" pattern="^domain.com$" />
                  </conditions>
                  <action type="Redirect" url="http://www.domain.com/{R:0}" redirectType="Permanent" />
              </rule>
          </rules>
      </rewrite>
  </system.webServer>

Previous to IIS7 this was handled in:

<system.web>
</system.web>

The above code can be viewed in the URL rewrite module interface. It’s illustrated below. You may add or modify in either the web.config, or this interface. The main thing is to get it installed, and most likely reboot.

URL Rewrite Rules Interface in IIS

IIS redirect using URL Rewrite

Notice under the “Action” section in the above image there is a selection for “Action type”. Among other choices you can choose “Redirect.” Once selected there are then places for you to select “Redirect URL,” and “Redirect type,” such as “Permanent (301).”

IS 8.0 with Free ASP.NET Hosting
Try our IIS 8.0 with Free ASP.NET Hosting today and your account will be setup soon! You can also take advantage of our Windows & ASP.NET Hosting support with Unlimited Domain, Unlimited Bandwidth, Unlimited Disk Space, etc.

The File Transfer Protocol (FTP) is a standard network protocol used to transfer computer files from one host to another host over a TCP-based network, such as the Internet. FTP is built on a client-server architecture and uses separate control and data connections between the client and the server. Internet Information Services (IIS, formerly Internet Information Server) is an extensible web server created by Microsoft for use with Windows NT family. IIS supports HTTP, HTTPS, FTP, FTPS, SMTP and NNTP. In this tutorial, I will show you how to install FTP Server in IIS 8 (Windows Server 2012).

Please follow these steps below:

Step 1

Open the Server Manager and click on Manage and select Add Roles and Features. Skip the Before you begin page by clicking on Next button. Then Select Role-based or feature based installation.

Select the server you wanted to install the FTP Server and click on Next.

Step 2

We must first install the Web Server (IIS) to enable the FTP Server feature and allow to add the pre-requisite to proceed to FTP Server installation.

Click on "Next" Button twice.

Step 3

When you are asked to select the role services to install for Web Server (IIS): Scroll down and make sure you have checked the FTP Server role, FTP Service and FTP Extensibility checkbox. Confirm the installation selections and click on Install. Then Click on close when the installation is done.

Step 4

It is now time to configure the newly installed FTP Server: Open your Server Manager and click on Tools then select Internet Information Services (IIS) Manager. You can click on Yes and disable the IE ESC to enable this feature or just click on No.

Step 5

In your Internet Information Services (IIS) Manager: Right click on you Sites and select Add FTP Site. Name your FTP Server and Select the content directory. In this screenshot, I made a folder name FTP-Files and click on OK.

Review the name and path then click on Next.

Check the Start FTP site automatically and the No SSL option and click on Next.

Step 6

This option depends on where you gonna use this FTP Server. In this example, I selected the basic authentication and specify the user who could access the FTP Server with Read and Write permission. Once you have decided on authentication and authorization information, Click on Finish.

Step 7

We are now done with the Installation and Setup of our FTP Server. Now its time to test it using your Internet Explorer. Open your Internet Explorer and type in: ftp://ipaddressofyourftpserver. Then Login and test if the authentication is working.

Hey, Its working!

Step 8

Now try to test using File Zilla or your favorite FTP application. Connect to your FTP Server and upload a test file (Remember to check if you have transferred the file successfully).

Step 9

Once everything is working. You might want to tweak some settings according to your FTP needs. Setup SSL, edit authentication and customize your FTP server. Just open the Internet Information Services (IIS) Manager to play around with the settings.

Hope this was able to help you setup your FTP Server in your Windows 20012 Server.

IIS 8.0 with Free ASP.NET Hosting
Try our IIS 8.0 with Free ASP.NET Hosting today and your account will be setup soon! You can also take advantage of our Windows & ASP.NET Hosting support with Unlimited Domain, Unlimited Bandwidth, Unlimited Disk Space, etc.

Today, I will explain to you how to set up redirector for SharePoint Sites in IIS 8. First, you need to install IIS 8 on your computer. You can check how to install IIS in this link. I used SharePoint Server 2013, IIS 8, and Windows Server 2012 to apply this tutorial.

Step 1

Most importantthing that you have to is to install HTTP Redirection component when installing IIS 8 to set-up redirector. You can click on Next to finish Installation. Let all the necessary components installed on.
If it requires a restart then do it.

Step 2

Click on Run and type Inetmgr to open the IIS manager console, you can see HTTP Redirect.

Step 3

Double click on this. You can see the HTTP Redirect console. In my example I am redirecting it to google.com and click Apply on the right hand side of the console.

Step 4

Now open you IE and type: http://localhost and hit enter and you will be redirected to google.com.

This is just an example, you can choose any URl based on your needs.

IIS 8.0 with Free ASP.NET Hosting
Try our IIS 8.0 with Free ASP.NET Hosting today and your account will be setup soon! You can also take advantage of our Windows & ASP.NET Hosting support with Unlimited Domain, Unlimited Bandwidth, Unlimited Disk Space, etc.

Today, i'm gonna explain to you the simple steps to load a file in the browser through the file server.

Just follow these steps:

Step 1

Using any web editor you like, create a file called index.html that resembles the page below using your name. Save it on the desktop.

Step 2

Using the mouse, double-click on the file that you have save in your desktop. Then page index.html is loaded into the browser via the file server.

Step 3

And the files that are rendered through the file server will have file:// in the Navigation window. Just remember, PHP files may not be rendered through the file server.

IIS 8.0 with Free ASP.NET Hosting
Try our IIS 8.0 with Free ASP.NET Hosting today and your account will be setup soon! You can also take advantage of our Windows & ASP.NET Hosting support with Unlimited Domain, Unlimited Bandwidth, Unlimited Disk Space, etc.