 |
|
|
|
 |
|
||
 |
 |
|
|
 |
 |
|
|
 |
|
||
 |
|
||
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
||
|
|
|
|
 |
 |
|
|
|
|
|
|
|
|||||||||||||||
|
A. Create the IIS web site This is done using the IIS manager program that is located in the option pack, Internet Information program group on NT4, or in the Administrative Tools, Internet Services Manager in Windows 2000. Right Click on the web server and choose new web site. A wizard will start and guide you through the process. First enter a descriptive name. e.g. NetHelpDesk Web Interface. Then choose the IP address that you wish this to appear on - or leave blank for all IP addresses present on the server. Enter the TCP/IP port number you wish to use for the web site. Normally this is port 80. If this is already in use on your server for another web site choose another port number such as 8080. Enter the path of the root of the web site. Browse to the c:\nhweb folder where the wb2.exe file is located. Allow executables to be used on the web site by checking the appropriate tick box. The web site should now be created and may be in a stopped state. Use a right mouse click to start the web site when ready. Before starting however, make the following adjustments by right clicking and choosing properties: Documents: enable default document - change to just wb2.exe. This will display this page first when entering the web site. See the IIS help file for an explanation of these settings. B. Give Execute permissions for IIS By default, the folder c:\nhweb will have execute permission to all users as NT gives these permissions by default. If this is not the case, or you wish to tighten security, use Windows explorer to set the permissions on the folder to be RX (read and execute) for the IIS user. The IIS user is generally of the format IUSR_xxxx where xxx is the server name. This is the user that is used by IIS to execute code and needs RX access to appropriate folders such as c:\nhweb. NHlogs needs write access. C. Test the web interface Using a web browser, type in the address of the web site you have just created. The NetHelpDesk login screen should appear. You can enter any valid NetHelpDesk login name at this point. The type of access is controlled by the settings in the Windows based NetHelpDesk Client's setup screen. Each NetHelpDesk user can be a technician with full control or be the person responsible for one Area/Client. Individual end users do not need to logon to check the status of their own calls. D. Appearance of Web Pages The appearance of the web pages can be controlled via the Windows client. Use options / setup / messages. There are entries for the different states of the web site. Adjust the HTML code carefully as required. You will see that there are phrases such as REPLACEMENU that are non-HTML code. These are replaced at run time by the system and create HTML for the menu etc. Some experimentation may be required to achieve the effect you require. E. Trouble Shooting If things don't work, use the NT event log to diagnose errors. Check the NT security settings of the folders that IIS needs access to. Check that the cnetweb.ini file correctly indicating where the logs folder is. Check the .udl file by using the test connection button in the .udl editor program. Check that you have set the default web page to be wb2.exe. Look in the IIS logs in the winnt\system32\logs folder. Look at the c:\nhlogs folder for error messages. Test access to the area1.gif file rather than to the wb2.exe by entering http://servername:80/area1.gif in the browser's address box. Contact our support desk, which can provide general help on default installations. |
|
|||||||||||||||
|
|
|
|
 |
|
|
|
Our powerful help desk software system and web interface helpdesk help desk software allows your company to run a more efficient helpdesk. It comes complete with a knowledge base, change management, and inventory management. |
