IIS 8.0 on Windows Server 2012 and Windows 8.0

Configure the server to host Sitefinity CMS projects

  1. Download the Windows Server 2012 PowerShell script and save it on your server.
  2. In the context menu of the downloaded file, click Run with PowerShell.
  3. Restart the server.

NOTE: When running the PowerShell script, your system may become slower. Keep in mind that the script modifies Windows features that can affect other parts of the system.

You can also perform the configuration manually.
For more information, see Manually configure the server to host Sitefinity CMS projects.

Install Sitefinity CMS on the server and create the project

  1. Download Sitefinity CMS Project Manager on the server.
    For more information, see Install Sitefinity CMS.
  2. Create the project, using procedure Create a project.
    In Step 3, select FileSystem.
  3. Configure the project using procedure Configure and start a project.
  4. Close Sitefinity CMS Project Manager.
    Sitefinity CMS automatically create a folder with the name of the project.
  5. Copy the entire project’s folder and place it inside C:\inetpub\wwwroot folder.
    If you do not see folder inetpub, IIS is not installed on your server and you must install it.

NOTE: It is not required to execute the project manager on the server. You can download and run the project manager on a local workstation and then transfer the project files to the web server using FTP or file share.

Run the project on the IIS

  1. Open Internet Information Services (IIS) Manager.
  2. In the left pane, expand your server’s node and in the context menu of Sites node, select Add Web Site…
    Add Web Site window appears.
  3. In Site name, enter a name for the website.
  4. If you have a dedicated application pool for this website, click Select… button and select it from the Application pool dropdown box. Otherwise, for each website, you are adding, IIS creates a corresponding Application pool.
  5. In Physical path, click button and browse to select inetpub\wwwroot\<your project name> folder, where you have chosen to locate your project files.
  6. In Binding section, if you have a dedicated IP address for the website, select it. If you have multiple websites sharing the same IP address, enter the host name of your website.
  7. Click OK.
    The Add Web Site window closes.
  8. In the left pane, click Application Pools node.
  9. Select the application pool of your website and in the right pane, click Basic Settings…
  10. In .NET Framework version dropdown box, select .NET Framework v4.0.30319.
    If there is no such entry, you must install .NET 4.8.
  11. In Managed pipeline mode dropdown, select Integrated.
  12. Click OK.
  13. Since Sitefinity CMS configurations are stored in the App_Data folder, the Application pool must have write permissions to this location. To grant such permissions, perform the following:
    1. Open folder inetpub\wwwroot\<your project name>.
    2. Open the context menu of App_Data folder and click Properties.
    3. On tab Security, click Edit… » Add…
    4. In From this location, select your server.
    5. Enter the object name using the following naming convention:
      IIS APPPOOL\<Application pool name>.
    6. Click OK.
    7. Grant permission to modify the App_Data folder, by selecting Allow checkbox of Modify permission.
    8. Click OK » OK.

RESULT: Open the IIS, select the uploaded site, and in the left pane, click Browse. The website runs in the browser, hosted on the IIS.

Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Web Security for Sitefinity Administrators

The free standalone Web Security lesson teaches administrators how to protect your websites and Sitefinity instance from external threats. Learn to configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.

Foundations of Sitefinity ASP.NET Core Development

The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.

Was this article helpful?