Windows 2003 Web Interface

The Web Management Interface is a feature worthy of being used by network users in Windows Server 2003. The main purpose of this function is to make it impossible for some authorized network users. Provide remote web management interface services for local maintenance. The author gives a brief introduction to the four common web interface management services.

Print Server Web Interface

The print server is one of the Windows Server 2003 servers and is an important part of resource sharing. In Windows Server 2003, if the print server has an IIS server installed, network users with permissions can manage the print server through browsers such as IE. Users in the domain can also install printers and manage their own printed documents through the browser. Wait. This convenient management mode is "printer server web interface management method". The process of its implementation is as follows:

First install IIS 6.0 and related remote management components. Click “Start →Control Panel →Add/Remove Programs", click the "Add/Remove Windows Components" button in the "Add or Remove Programs" window, and then in the pop-up  Windows Components Wizard&rdquo In the window, select “Application Server”.

After double-clicking "Application Server", select "Internet Information Service (IIS)" in the pop-up window. Because you want to set up the printer server to use the web interface management, you need to click the <;Details" button. In the pop-up window, check the “Internet Printing” option to implement web printing and manage the printer (Figure 1).

After the component is installed, you can enter the print server name /printers/(such as 192.100.100.16/printers/) on any computer on the LAN to enter the printer server's web. Interface management page. On this page you can see all the printers and statuses on this server.

Web Interface for Terminal Servers

Terminal Server is a service that allows remote network users with permissions to log in to the server through the desktop interface. In general, we use the “Remote Desktop Connection” feature to connect the client to the terminal server.

In Windows Server 2003, users can use the IE browser (version 4.0 or higher) to connect, log in, and manage the terminal server by using the IE server with the terminal server. This feature is the "Remote Desktop Web Connection" feature that will be described below. Its main purpose is to allow administrators to connect to the terminal server through a web interface (browser) without having to install the "Remote Desktop Connection" program on each computer.

First install IIS 6.0, and double-click "Internet Information Service (IIS)" during the installation process, and select "World Wide Web Service" in the window that opens. Then double-click "World Wide Web Service" and select "Remote Desktop Web Connection" in the pop-up window to start installing the selected components.

After installing the component, you can access the terminal server by entering the server IP address or the name /tsweb/(eg http://192.100.100.16/tsweb/) in the IE address bar of the remote computer. After entering the IP address of the server and setting the resolution in the “Remote Desktop Web Connection” page, click the “Connect” button to log in to the login interface of the terminal server. Enter the correct username and password to log in to the server's desktop environment.

Tip: If you are unable to connect to the terminal server, please confirm whether the remote desktop function of the terminal server is activated, ie right click on “My Computer", select “Properties> ;, in the Properties window, the "Remote" tab settings interface, check "Allow users to remotely connect to this computer".

Web interface for streaming media server

In Windows Server 2003, it is easy to set up a Windows Media streaming server that supports both webcasting and video-on-demand, but you I have thought about it, we can also manage the streaming server through the web interface.

In the "Windows Components Wizard" window, select "Windows Media Services" and go to the detailed settings window of this option, and check the "Windows Media Services Manager for Web" item. (figure 2). From the pop-up "Windows Media Services Installation Warning" prompt box, you can see that the currently selected component requires IIS 6.0 support. At this point, click the “OK" button (IIS 6.0 components will be automatically selected).

After the above components are installed, you can enter http://streaming server IP address 8080/(for example, http://192.100) in the address bar of the remote computer's IE browser. .100.16:8080/default.asp) Manage the streaming server using the web interface. After entering the URL and pressing the Enter key, you can see the Web Interface Management page of Windows Media Services.

For security reasons (to prevent other users from managing Windows Media Services), you can log out of this management by entering the URL http://192.100.100.16:8080/WMSlogoff.asp when exiting the web interface management page.

Remote Maintenance Web Interface

The remote maintenance function is a very important function, which can help network administrators to complete the management and maintenance operations of multiple specific service items of the server through the Web interface. That is, remote access to the IIS 6.0 Web Interface Management page.

In the "Windows Components Wizard" window, select "Application Server", "Internet Information Service (IIS)", "World Wide Web Service", and in the "World Wide Web Service". In the ” check "Remote Management (HTML)", and finally click the "OK" button to install the component.

After completing the above operation, you can enter the address in the LAN, https://server name or IP address8098” (On the remote computer, you can only enter “ server IP address: 8098&rdquo ;) to access the Web Server Management page of Windows Server 2003 IIS 6.0.

On this page, you can view or configure the server's running log file, website IP address, DNS suffix, and domain. In addition, you can create, edit, and delete lists of users and groups on the server, and even remotely restart the server and shut down the server.

Through the explanation of the Web interface management example, do you feel that the Web Server management function of Windows Server 2003 is very powerful? But the author should emphasize that the Web interface management will be different due to the user's management. Level security risks, so please be careful to use the web interface management function.