Windows 2003 Web Interface _windows2003

The Web Management interface (Web Management Interface) Windows Server 2003is a feature that is highly desirable for network users, and is designed primarily to provide remote Web management interface services to some privileged network users when they are unable to perform native maintenance. The following is a brief introduction to four common Web interface Management services.

　　Web interface for print server

The print server is one of the Windows Server 2003 servers that is an important component of resource sharing. In Windows Server 2003, if the print server has an IIS server installed, network users with permissions can manage print servers through browsers such as IE, and users in the domain can install printers, manage their own printed documents, and so on. This convenient management mode is the "Printer Server Web interface management mode." Its implementation process is as follows:

First, install IIS 6.0 and the associated 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 select Application Server in the Windows Components wizard window that pops up.

After you double-click application Server, select Internet Information Services (IIS) in the pop-up window. Because you want to set up the printer server to use Web interface management, you will also need to click the "Details" button. Click the "Internet print" option in the pop-up window to enable Web printing and management of the printer (Figure 1).

Figure 1

After the component is installed, you can enter the http://print server name/printers/into the printer server's Web interface Management page on any computer in the local area network. On this page, you can see all the printers and status on this server.

Web interface for Terminal Server

A Terminal server is a service that allows a remote network user with permission to manage a server by logging on to the desktop interface. In general, we all use the Remote Desktop Connection feature to connect the client to the Terminal server.

In Windows Server 2003, users can complete connection, logon, and administrative operations with a terminal server by using IE browser (version 4.0) on the client side, as long as the Terminal server is paired with an IIS server. This feature is the Remote Desktop Web Connection feature that will be described below. Its primary purpose is to enable administrators to connect to a 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, during installation, double-click Internet Information Services (IIS) to check the open window to select World Wide Web services. Then double-click Web Services to start installing the selected components after you select Remote Desktop Web Connection in the pop-up window.

After the component is installed, you can access the Terminal server by entering the http://server IP address or name/tsweb/(such as http://192.100.100.16/tsweb/) in the IE address bar of the remote computer. When you enter the IP address of the server in the Remote Desktop Web Connection page and set the resolution size, you can log on to the Terminal server's login interface by clicking the "Connect" button. You can log on to the server's desktop environment by entering the correct username and password.

Tip: If there is an inability to connect to a Terminal Server, please confirm that the Remote Desktop feature of the Terminal Server is active, that is, right click on "My Computer", select "Properties" in the pop-up menu, set the interface on the "Remote" tab in the Properties window, and check "allow users to connect to this computer remotely".

　　Web interface for streaming media server

In Windows Server 2003, it's easy to set up a Windows Media streaming server that supports both webcasts and video on demand, but if you think about it, we can also manage streaming media servers through the Web interface.

Check Windows Media Services in the Windows Components Wizard window and go to the Detailed Settings window for this option to check the "Windows Media Services Manager for Web" item (Figure 2). From the Windows Media Services installation warning Prompt box that pops up, you can see that the currently selected component requires IIS 6.0 support. Click OK at this point (the IIS 6.0 component will be automatically selected).

Figure 2

After the above components are installed, you can enter the http://streaming media server IP address 8080/(such as http://192.100.100.16:8080/in the remote computer's IE browser address bar). Default.asp) uses a web interface to manage streaming media servers. When you enter the URL and press ENTER, you can see the Web Interface Administration page for Windows Media services.

For security reasons (to prevent other users from managing Windows Media Services), you can log out of this administration by entering the URL http://192.100.100.16:8080/WMSLogOff.asp when exiting the Web Interface Administration page.

　　Remote Maintenance Web Interface

Remote maintenance is a very important feature that can help network administrators through the Web interface to complete the server's multiple specific service project management maintenance operations, that is, remote access to the IIS 6.0 Web interface Management page.

In the Windows Components wizard window, select Application Server, Internet Information Services (IIS), World Wide Web services, check remote management (HTML) in the World Wide Web service, and then click OK to install the components.

After you do this, you can enter an address such as "https://server name or IP address 8098" on the local area network (only "http://server IP address: 8098") to access IIS in Windows Server 2003 on a remote computer 6.0 Web Interface Management page.

On this page, you can view or configure the server's run log file, Web site IP address, DNS suffix, domain. You can also create, edit, and delete lists of users and groups on the server, even remotely restarting the server and shutting down the server.

Do you feel that the Web interface management features of Windows Server 2003 are powerful by explaining the example of Web interface management? But the author should emphasize that the Web interface management is due to the user's management is appropriate to different levels of security problems, So please use the Web interface management function carefully.