HTTP Commander application install at Windows Servers 2008 R2 SP1, 2012, 2012 R2, 2016, 2019 (IIS 7.5, 8, 8.5, 10).
Note 1!
You can view
Installation screencast (video) (Recommended)!
Note 2!
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 IIS 7+ and .NET Framework 4.7.2+ installed.
In this section:
IIS and .NET Framework Installation
1. IIS Installation
Note! If the IIS is already installed,
then still follow the steps below to make sure that
ASP.NET Features are installed.
-
Open the Server Manager,
click the Add roles and features link,
(or go to Roles section and click Add roles for Windows 2008 R2),
on the Bofore You Begin screen click Next button,
on the Installation Type - Role-based or feature-based installation and press Next,
on the Destination Server screen select current server and click Next.
Check Web Server (IIS) role with add the IIS Management Console
feature and press Next button.
Screenshots
-
Select ASP.NET 4.x on the screen Features in
the section .NET Framework 4.x Features
(or ASP.NET in the section Application Development for Windows Server 2008 R2).
If you plan to use Windows Search Service in HTTP Commander, to search files by content
(option SearchMethodOfFiles)
check also the feature Windows Search Service
(for more information see Windows Search manual).
Press the Next button twice to go to the screen Role Services.
On this screen (Role Services) also check:
-
ASP.NET, .NET Extensibility 4.x,
Application Initialization
in the section Application Development
-
Dynamic Content Compression in the section Performance
-
Basic Authentication and Windows Authentication
in the section Security
Screenshots
-
Click the Next button and follow the instructions
Screenshots
2. .NET Framework 4.7.2 or above
-
To determine which version of the .NET Framework you are using, see the article
How to: Determine Which .NET Framework Versions Are Installed.
If the decimal value of the Release key in the Registry node
HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
less than 461808 (that corresponds to version 4.7.2),
then you need to download and install
.NET Framework 4.7.2
(or above).
Screenshot
-
If .NET Framework 4.7.2 (or above) has been already installed,
you need either reinstall it or execute the following commands as administrator:
%WINDIR%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
and (for 64-bit systems):
%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
Automatic HTTP Commander Installation with installation wizard (EXE)
3.a Automatic HTTP Commander Installation...
-
Download
latest released version of HTTP Commander
from official web site.
-
Launch downloaded EXE file with Administrative privileges:
Right click on downloaded file → "Run as Administrator".
-
Follow on-screen installation instructions and wait for installation to complete.
-
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.
- Configure Force Logout function.
-
Configure anonymous access to public links
if anything of the following is true:
The process of configuring public links for anonymous access is detailed in the section
configure anonymous access to public links.
Installation wizard automatically configures Anonymous access for public links.
You will only configure special account for that handler and set permissions for it on all shared folders.
Manual HTTP Commander Installation (ZIP package)
3.b Manual HTTP Commander Installation...
How to detect application pool HTTP Commander runs under?
- Open IIS Manager
- Select HTTP Commander application on the Connections pane
- Click "Basic Settings..." on the Actions pane
- "Edit Application" window appears
- Read the Application pool field — that the name of the application pool HTTP Commander runs under.
How to unblock distribution archive?
-
Right click distribution archive file
HTTPCommanderAJSx.x.xWindows.zip
and select Properties in context menu.
-
In the properties dialog, open "General" tab,
click "Unblock" button and then Apply button.
Screenshot
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 Application settings,
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 because it has answers how to increase performance
and security of application and some other helpful solutions.