HTTP Commander application install at Windows 2008 (IIS 7 and 7.5).
Note!
We offer free installation assistance for both trial and commercial licenses. You can get help via email, instant messenger or via remote access to your server. You need few minutes to get online help.
The HTTP Commander is installed like any other ASP.NET application.
To run the application, you need at least to have IIS and .NET framework 4.0 or 3.5 installed.
IIS and .NET Framework Installation
1. Installation IIS and .NET Framework 4.0 or 2.0...
- For web service installation, open the Server manager, go to Roles
section, click Add roles, and check Web server (IIS) role.
Screenshot
- Select "ASP.NET"
, "Basic Authentication" and "Windows Authentication" that are necessary for HTTP Commander.
Click Next and follow the instructions.
Note! You should install .NET framework after IIS installed. If you had .NET framework installed before IIS then reinstall .NET framework!
Screenshot
2. Installation .NET Framework 4.0 or 3.5...
You can choose how to run application: under .NET Framework 4.0(recommended) or 2.0+3.5:
- If you prefer to use .NET Framework 4.0 (recommended) then download it and install.
- if you prefer .NET Framework 2.0 + 3.5 then:
- You haveinstalled IIS with ASP.NET 2.0. The HTTP Commander also requires .NET Framework 3.5 extensions. Check if you have them:
- Click the Start button in the lower left corner of the display.
- Navigate to Administrative Tools and select Server Manager.
- In the Server Manager interface, click Features to display all the installed Features in the right side. Check if .NET Framework 3.5 is listed there.
If .NET Framework 3.5 feature is not listed, go to the next step to see how to install it.
- How to install .NET Framework 3.5:
- In the Server Manager interface, select Add Features to display a list of possible features.
- In the Select Features interface, expand .NET Framework 3.5.1 Features.
- Once you expand .NET Framework 3.5.1 features, you will see two check boxes. Check .NET Framework 3.5 and click Next.
- In the Confirm Installation Selections interface, review the selections and click Install.
- Allow the installation process to complete and click Close.
Screenshot
HTTP Commander Installation
3. HTTP Commander Installation...
- Place HTTP Commander code on web server:
- Open IIS server's root folder in Windows Explorer (by default it is c:\Inetpub\wwwroot\)
- Extract the HTTP Commander zip archive to a new HTCOMNET folder inside the root folder. You can use any name for the folder or place it not in the root. In this manual we use such placement and name as default.
Screenshot
- Unblock files which come from another PC (latest Windows 2008 security issue):
- Open at Windows explorer HTTP Commander Bin\ folder (c:\Inetpub\wwwroot\HTCOMNET\Bin).
- Right-click the any *.dll file and select "Properties" in the context menu.
In the new window, open "General" tab and click "Unblock" button.
Make the same action with all other *.dll files at Bin\ folder!
Screenshot
- Restart application (Close all w3w.exe procceses) if you already tryed to run application
- Create "Application" in IIS:
- Open IIS console: Control panel->Administrative tools->
Internet Information Services->Expand "Sites" and then "Default web site"
- Right-click the "HTCOMNET" folder and select "Convert to Application" in the context menu.
In the new dialog box, click "ok".
Screenshot
- Set Basic authentication
- In the IIS console, select HTCOMNET node and click "Authentication" in the right tab.
You should have "Basic Authentication" and "ASP.NET Impersonation" enabled. All the other options should be disabled.
Select "Basic Authentication" option and click "Edit..." link in the right Actions tab. In the new dialog set default domain name!
Why you need to use Basic authentication?
Note! If you cannot find "Basic" settings, the feature have not been installed. You need to check "IIS Installation" step then.
Screenshot
- Check "Full trust" level:
-
In the IIS console in the right panel, open ".NET trust levels" and select "Full" in the list.
Note! HTTP Commander also supports "Medium trust" but in this case you can provide access only to the folders inside the application root (HTCOMNET folder).
Screenshot
- Check required NTFS permissions.
Running and configure
- Now you can run HTTP Commander diagnostics page. Open the application URL in your browser, e.g. "http://localhost/HTCOMNET/Diagnostics.aspx". Look if you have something non resolved issues.
-
If everything fine you can run HTTP Commander main page "http://localhost/HTCOMNET/Default.aspx" and login as domain admin user. See folder edit in AdminPanel to setup access to the folders for necessary users and groups. After that try to login as simple user. If you can't login or view data or manage files then check NTFS permissions.
- We strongly recommend to read NTFS permissions section of the Documentation to be sure that permissions are set correctly for the application .
- For application configuration you need to set parameters at web.config file, also there you can read how to configure advanced features like folders mapping (WebDav), Office edit or online documents editors at IIS.
- Read FAQ section becouse it has answers how to increase perfomance and security of application and some other helpfull solutions.