Tips for efficient server management

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

Refuse to restart the server. Generally, after installing the patch in the Windows 2003 Server system, the system will always prompt you to restart the server. However, many friends often cannot tolerate the "slow" startup operation of the Windows 2003 Server server, so they hope that the server will not restart after the security patch is applied. In fact, whether the Windows 2003 Server server will restart has a certain relationship with the current system patch characteristics. For those security patches that force system startup, the server generally cannot reject it; but for those patches that do not force system startup features, you can take the following methods:

1. In the Windows 2003 Server server system desktop, click the "Start"/"Run" command in sequence. In the system run dialog box that opens subsequently, enter the string command "cmd", click the "OK" button, and then 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 the name of the system patch that currently needs to be installed), followed by In the prompt interface that appears, check whether the current patch has the "-z" parameter. If it does, it means that the current patch does not force the system to restart after installation;

3. Then in the DOS command line, enter the string command "aaa -z" and click the Enter key. The patch will be automatically installed in the system and will not require the server system to restart.

Remove restricted access to the server. In order to improve employee work efficiency, the company recently planned to open access to the Windows 2003 terminal server to every employee. However, considering security, the network administrator only provided the same account for all employees. to log into Windows 2003 Terminal Server. However, when employees used this account to log in to the terminal server, they found that the server could only allow one person to log in to the server at the same time, and as soon as subsequent employees logged in to the server, the previous employee would be "forced" to log out of the terminal server. . What exactly is going on when this phenomenon occurs? Is there any way to allow all employees to log in to the server smoothly using the same account at the same time?

In fact, the above phenomenon is mainly caused by the Windows 2003 terminal server enabling the "limit each user to only one session" function by default. Disabling it can solve the problem.

1. Go to the "Start" menu, execute the "Settings"/"Control Panel" command in sequence, and 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 to one session" option in the "Server Settings" area, and in the option settings dialog box that appears, uncheck its check box. ,"Sure". And restart the server system so that employees using the same account in the future can log in to the Windows 2003 terminal server system at the same time.

Remotely View Server Log Files Network management can fully utilize the server's log files to protect server security. However, the server's log files can usually only be viewed locally on the server. But in the event that the network administrator travels far away, how to ensure remote viewing? Windows 2003 server provides a remote maintenance function, but it is not enabled by default and needs to be started manually. .

1. Check whether the II6.0 component and its related components have been installed on the Windows 2003 server. If not, these components must be installed on the server first;

2. In the "Start" menu, click "Settings", "Control Panel" command, "Add or Remove Programs" icon, then click the "Add/Remove Windows Components" button in the subsequent interface, and click on the pop-up In the Component Installation Wizard window, select the "Application Server" checkbox, and then click the "Details" button in the corresponding window; then select the "Internet Information Services (IIS)" checkbox, and then continue clicking in the corresponding window. "Details" button;

3. In the wizard setting window that appears, select the "World Wide Web Service" item, and continue to click the "Details" button in the corresponding window. In a wizard interface that pops up, select the "Remote Management (html)" item. ;Click the "OK" button and put the installation CD of the Windows 2003 server system into the CD-ROM drive, and then the system will automatically complete the remaining installation and setting tasks.

In the future, no matter where the network managers go, as long as they can find a computer with Internet access, they can enter the address "http://aaa.aaa.aaa.aaa:8098" (where aaa.aaa.aaa .aaa represents the effective IP address of the Windows 2003 server). In the server account verification interface that opens later, if you enter the administrator account correctly, you can remotely log in to the server's management and maintenance page. In this page, the network administrator You can easily view the log files in the server.