Creating the Website IIS 4.0

Note: This article applies to RPM 4.5 which is not the latest version available.  The content in this article may not be relevant to you.  For information relevant to RPM Elite 5.0 or later, please review this article.

RPM Remote Print Manager® Elite (RPM Elite) version 4.5 and prior includes a remote administration utility called the Remote Print Administrator (RPA). To administer RPM remotely with RPA, open a browser from any computer and type the server name followed by rpm. For instance, if your computer is named server, type server/rpm.

RPA requires Microsoft Internet Information Server (IIS), which should be installed prior to installing RPM Elite. Both IIS version 5 and version 4, also called Personal Web Server, are supported. If either is installed, the RPA component can be selected during the installation process. Personal Web Server can be found on the Windows NT 4.0 Option Pack.

During installation, the setup program attempts to add the RPM website to IIS or Personal Web Server directly beneath the Default Web Site. If Default Web Site has been renamed or deleted, the RPM website will not be added automatically, and must be created manually.

  1. From the Start menu, point to the Programs menu, then Windows NT 4.0 Option Pack, then Microsoft Personal Web Server, and choose Internet Service Manager.
  2. The Microsoft Management Console will be opened to the Internet Information Server snap-in. Expand the computer name tree, then Web Sites.

  3. Right click the website where you wish to add access to RPM, point to the New menu, and choose Virtual Directory. The Virtual Directory Creation Wizard is started.
  4. The first step of the wizard asks for a short name or alias. Enter rpm and click Next. Note that the name must be rpm or the RPA will not function properly.

  5. The second step prompts you for the location where the files are installed. Click Browse and locate the RPA folder, which by default is C:\Program Files\Brooks Internet Software\RPMElite\RPA.

  6. The final step of the wizard asks you to customize permissions required for the virtual directory. RPA requires the execute permission as it is an ISAPI extension.

  7. The new rpm virtual directory properties must now be edited, as the default properties are insufficient for RPA. In the Internet Information Services window, right click rpm and choose Properties from the menu.
  8. In the Documents tab, verify Enable default document is selected. Click Add and type index.html, which will add it as a default document. Press OK to accept and dismiss the dialog.

  9. Highlight the index.html document you entered in the previous step and click the Up button until the document is at the top of the list.
  10. Now, click the Directory Security tab. Under Anonymous access and authentication control, click the Edit button.
  11. Deselect Allow Anonymous Access, and verify that Windows NT Challenge/Response is selected. Windows authentication is required because RPA reads and modifies configuration as the authenticated user. Press OK to accept the changes and dismiss the dialog.

  12. Finally, press Apply in the rpm Properties dialog to apply the changes to directory security, then OK to dismiss the dialog.

RPM is now accessible on your network using a browser. To test, open a browser and type the following: server/rpm. Be sure to substitute your server's actual name in place of server.