Efficient management server to extract 3 tips

Efficient management server has always been inseparable from effective server management skills. The author summarizes the work experience and extracts 3 tips to share with readers.

Remote View Server Log File

The network management system can fully utilize the server's log files to protect the server. However, the server's log files can only be viewed locally on the server, but in case the network administrator goes out, how to ensure remote viewing? Windows 2003 server provides remote maintenance, but it is not enabled by default, you need to manually start .

1. Check if the Windows 2003 server has installed the II6.0 component and its related components. If it is not installed, you must first install these components into the server.

2 In the "Start" menu, click the "Settings", "Control Panel" command, "Add or Remove Programs" icon, then click the "Add /Remove Windows Components" button in the subsequent interface, and the components that pop up In the installation wizard window, select the "Application Server" option, click the "Details" button in the corresponding window; then select the "Internet Information Services (IIS)" option, and then continue to click in the corresponding window "Details" button;

3. In the wizard settings window that appears, select the "World Wide Web Service" project and continue to click the "Details" button in the corresponding window, in a wizard interface , then select the "remote management (html)" project; click the "OK" button, and put the installation CD of the Windows 2003 server system into the CD-ROM drive, then the system will automatically finish The remaining installation setup tasks.

In the future, network administrators can find a computer that can access the Internet no matter where they go, and enter the address of "http://aaa.aaa.aaa.aaa:8098" through the IE browser interface ( Aaa.aaa.aaa.aaa indicates the valid IP address of the Windows 2003 server. In the server account verification interface that is opened later, the system administrator account is correctly entered, and the server can be logged in to the management and maintenance page of the server remotely. The web administrators on this page can easily view the log files in the server.

Denying server restart

In general, after installing the patch on Windows 2003 Server system, the system will always prompt to restart the server. However, many of the friends often cannot tolerate the "slow" startup of the Windows 2003 Server server, so the server does not restart after the security patch is completed. In fact, whether the Windows 2003 Server server will restart will have a certain relationship with the current system patch features. For those security patches that are forced to start the system, it is generally impossible for the server to refuse; but for those patches that do not require the system startup feature, you can take the following measures:

1. On the Windows 2003 Server server In the system desktop, click the "Start" /"Run" command, in the subsequent system operation dialog box, enter the string command "cmd", click the "OK" button, switch the system working mode to MS- DOS state;

2. In the DOS command line, use the "cd" command to switch the current directory to the directory where the patch is located, and then execute the "aaa /?" string command (where aaa is currently needed) Install the system patch name. In the prompt interface that appears, check whether the current patch has the "-z" parameter. If the parameter is included, it indicates that the current patch is not mandatory after the installation. Restart;

3. Then in the DOS command line, enter the string command "aaa -z", click the Enter key, the patch will automatically Loaded into the system, and the server is not required to restart the system.

Unblocking access to the server

In order to improve employee productivity, the organization recently planned to open access to Windows 2003 terminal servers to every employee, but considering security, the network The administrator only provides the same account for all employees to log in to the Windows 2003 terminal server. However, when employees log in to the terminal server with this account, they find that the server can only allow one person to log in to the server at the same time. After the employee logs in to the server, the former employee will be forced to log out of the terminal server. . What is going on with this phenomenon? Is there any way for all employees to log in to the server smoothly using the same account at the same time?

In fact, this phenomenon is mainly due to Windows. In the default state of 2003, the terminal server is enabled with the function of "Limit each user can only use one session", and canceling it can solve the problem.

1. "Start" menu, execute the "Settings" /"Control Panel" command in turn, then double-click the "Administrative Tools" icon to enter the Terminal Services Configuration window;

2. In the configuration window, double-click the "Restrict each user can only use one session" option in the "Server Settings", and in the option setting dialog box that appears, uncheck the check box. ,"determine". And restart the server system, so that employees can use the same account in the future, you can log into the Windows 2003 terminal server system at the same time.