Created On:  15 March 2012

Problem:

How to install License Server 4.0 with IIS 7.0 or IIS 7.5 on Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2?

Resolution:

Each operating system comes with its own version of Internet Information Services (IIS). Windows Vista and Windows Server 2008 come with IIS 7.0 while Windows 7 and Windows Server 2008 R2 come with IIS 7.5, which has improved and more features.
 
IIS 7.x is in fact a complete redesign and rewrite of IIS, so the following instructions on how to install License Server 4.0 are completely different from the ones made for IIS 6.0 running on Windows Server 2003.
 

1)      Install MF License Server 4.0:

Install License Server in a different directory other than the default "Program Files" or “Program Files (x86)” directory, as there is an access restriction which causes problems in the software. Consider installing License Server in C:\\LS4
Note: If the file - LSP3240000110.exe – used to install the License Server is dated 2006-07-26 or more recent, there is no need to install the License Server FixPack from the SupportLine web site.
 

2)      Make sure IIS 7.x is installed with the following role services, which are grouped under Application Development:

·         CGI

·         ISAPI Extensions

Note: If these role services are not installed, then the "ISAPI and CGI Restrictions" icon will not be found in Features View of the web server Home screen in IIS Manager.
 

3)      Check Application Pools setting:

a.       Open IIS Manager

b.      Click on the server name (the screen displayed on the right pane is the web server Home screen)

c.       Expand the server name in the left hand pane by clicking on " "

d.      Click on Application Pools in the left hand pane

e.      Make sure the DefaultAppPool in the center pane has “Managed Pipeline Mode” set to Classic. To change this setting, double-click on DefaultAppPool, select Classic from the "Managed pipeline mode" drop-down list, and click on OK

f.        On a 64-bit environment, right-click on DefaultAppPool, click on Advanced Settings, and set "Enable 32-Bit Applications" to True

g.       After making any changes in DefaultAppPool, the default application pool must be restarted by right-clicking on DefaultAppPool and clicking on Recycle

h.      Make sure the DefaultAppPool's status indicates Started

 

4)      Add LS4 as a new application in Default Web Site:

a.       Expand Sites in the left hand pane, which is below Application Pools

b.      Right-click on Default Web Site

c.       Click on Add Application

d.      Enter LS4 as Alias

e.      Click on Physical Path's browse "..." button to select C:\\LS4\\BIN

f.        Click OK

 

5)      Grant full control to the IUSR (local) account on LS4 application:

a.       Expand Default Web Site in the left hand pane

b.      Right-click on LS4

c.       Click on Edit Permissions

d.      Click on the Security tab

e.      Click on Edit

f.        Click on Add

g.       Make sure the machine name is specified in the “From this location” field – If not, click on Locations, select the machine name, and click on OK

h.      Type IUSR from the "Enter the object names to select" field

i.         Click on Check Names (IUSR will be underlined as it has been checked)

j.        Click on OK

k.       Click on IUSR to edit its permissions

l.         Check Allow for "Full control"

m.    Click on OK

Note: By default, Anonymous authentication is enabled in IIS 7. The IUSR account, which was introduced in IIS 7.0 and replaces the IIS 6.0 IUSR_computername account, is used to allow anonymous access.
 

6)      Make sure dynamic compression is not enabled on LS4 application:

a.       Expand Default Web Site in the left hand pane

b.      Click on LS4

c.       Double-click on Compression in the right hand pane

d.      Make sure “Enable dynamic content compression” option is unchecked. This option is grayed out if the associated role service was not installed. If this is however not grayed out and left unchecked, it will not allow the client to obtain a license from License Server. It will cause a prompt from the client to download a “.tm1.tmp” file (see MF KB 33079)

 

7)      Create ISAPI and CGI Restrictions

a.       Go to web server home screen by clicking on the server name in the left hand pane

b.      Double-click on "ISAPI and CGI Restrictions"

c.       Select "Restriction" from the "Group by" drop-down list

d.      Add a new restriction for each one of the following files from the License Server installation "Bin" directory: LS4.DLL, LSADMIN.DLL, LSCLIENT.DLL, LSADMIN.EXE and LSCLIENT.EXE

To add a restriction:

                                 i.            Right-click in the center pane white space and select Add

                               ii.            Click on the browse "..." button to select DLL or EXE file

                              iii.            Check "Allow extension path to execute”

                             iv.            Click on OK

 

8)      Enable the Handler Mappings for ISAPI and CGI from the web server home screen:

a.       Go to web server home screen by clicking on the server name in the left hand pane

b.      Double-click on Handler Mappings (note CGI-exe and ISAPI-dll are both Disabled)

c.       Right-click on ISAPI-dll

d.      Click on Edit Feature Permissions

e.      Check "Execute"

f.        Click on OK (note CGI-exe and ISAPI-dll are now both Enabled)

 

9)      Check that the ISAPI and CGI mappings are enabled for the Default Web site:

a.       Click on Default Web site

b.      Double-click on Handler Mappings

c.       See if CGI-exe and ISAPI-dll are both Enabled

 

10)   Check that the ISAPI and CGI mappings are enabled for the LS4 application:

a.       Click on the LS4 application underneath Default Web Site

b.      Double-click on the Handler Mappings icon

c.       See if CGI-exe and ISAPI-dll are both Enabled

 

11)   Restart IIS server:

a.       Go to web server home screen by clicking on the server name in the left hand pane

b.      Click on Restart, which is under Manage Server in the right hand pane

 

12)   Give "Full Control" permission to the IUSR (local) account on License Server registry key:

a.       Open Registry Editor

b.      Go to "HKEY_LOCAL_MACHINE\\SOFTWARE\\Micro Focus\\License Server\\4.0" on a 32-bit environment or to "HKEY_LOCAL_MACHINE\\SOFTWARE\\wow6432mode\\Micro Focus\\License Server\\4.0" on a 64-bit environment

c.       Right-click on the 4.0 key

d.      Click on Permissions

e.      Click on Add

f.        Make sure the machine name is specified in the “From this location” field – If not, click on Locations, select the machine name, and click on OK

g.       Type IUSR from the "Enter the object names to select" field

h.      Click on Check Names (IUSR will be underlined as it has been checked)

i.         Click on OK

j.        Click on IUSR to edit its permissions

k.       Check Allow for "Full control"

l.         Click on OK

 

13)   Configure License Server:

a.       Go to Start > All Programs > Micro Focus License Server 4.0 > Configuration

b.      Uncheck "Use License Server Web Server"

c.       Enter server name or IP address in the Server Name field

d.      Enter the LS4 application name preceded by a slash character (i.e. /LS4) in the Virtual Directory field

e.      Enter 80 (or whatever IIS is using as port) in the Port Number field

f.        Click on OK.

Note: This will open the License Server administration page in your default web browser. To open License Server next time, you can either go to "Start > All Programs > Micro Focus License Server 4.0 > License Server" or simply open a web browser and enter http://machine-name/ls4/lsadmin.dll where machine-name is the name or IP address specified in step (c) and ls4 is the LS4 application name specified in step (d)

 

14)   Review License Server’s Basic Configuration:

a.       Open the License Server Administration page

b.      Click on the License Server Configuration button, which is second from the right

c.       Make sure C:\\LS4 (or any folders where IUSR has full permission on) is specified for both Log Files Location and Backup Files Location

d.      Click on Apply to save changes

15)   Install licenses in License Server:

a.       Open the License Server Administration page

b.      Click on the License Server Configuration button, which is second from the right

c.       Click on Additional Licenses

d.      Check the product name(s)

e.      Click on OK

f.        Submit Request Key at the MF Licensing site (http://supportline.microfocus.com/licensing/LicensingHome.asp)

g.       Enter the Response Key from Micro Focus

h.      Click on OK

 

16)   Check the registry permissions are correct:

a.       Open the License Server Administration page

b.      Click on the License Server Configuration button, which is second from the right

c.       Click on Group Manager

d.      Click on New to create a new group

e.      Enter TEST_GROUP in the Group field

f.        Check Allow Network Licensing

g.       Enter 1 in the Days field

h.      Check one of the products under Options Allowed

i.         Enter 1 for Max Permanent Licenses and Max Licenses

j.        Click on Apply

k.       Close the web browser

l.         Go back to the Group Manager page (follow steps “a” through “c”)

m.    See if TEST_GROUP is still listed

If the group is still listed, it means the registry permissions are properly set. The test group can now be deleted by clicking on its name from the group list, click on Delete, and click on Yes to proceed with deletion.
 
If however the group does not get created, you will need to review Step 11. If Step 11 was followed properly and a group cannot still be created, then the issue could be related to the web browser's security setting that prevents submit buttons from executing any programs from a web page. This could be the case with MS Internet Explorer (IE) where its internet security tags the License Server page as "Internet", and it displays "Internet" in the IE’s status bar next to the globe icon. IE's security setting is very strict with "Internet" pages or sites. You may then want to have the web server's URL (i.e. http://server-name) to be recognized as “Local intranet”. This can be achieved as follows:

a.       Double-click on “Internet” from IE’s status bar to open IE’s Internet Security screen

b.      Click on Local Intranet

c.       Click on Sites

d.      Click on Add as the server’s URL is populated into “Add this website to the zone”

e.      Click on Close

f.        Click on Apply

g.       Click on OK

h.      Close IE