Three techniques for efficient server management

Deny 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 start 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 system running dialog box that opens, enter the string command cmd, and click the OK button to 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 needs to be installed currently), which appears after it. In the prompt interface, check whether the current patch has the -z parameter. If the parameter is included, it indicates that the current patch cannot be forced to restart after the installation is completed;

3. Then in DOS In the command line, enter the string command aaa -z. After clicking the Enter key, the patch will be automatically installed into the system and the server will not be required. Re-start.

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 the employee logs in to the terminal server with the account, it is found that the server can only allow one person to log in to the server at the same time, and the subsequent employee will be forced to log out of the terminal server as soon as the employee logs in to the 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 to limit the use of only one session function for each user. Cancellation can solve the problem.

1. Start the menu, execute the settings/control panel commands in turn, and then double-click the management tool icon to enter the terminal service configuration window;

2. In the configuration window, Double-click the limit of the server settings with the mouse. Each user can only use one session option. In the option setting dialog box that appears later, uncheck the check box and confirm. 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.

Remote View Server Log File

The NMS 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 yet, you must first install these components into the server;

2 In the Start menu, click Settings, Control Panel Commands, Add or Remove Programs icon, then click the Add/Remove Windows Components button in the subsequent interface, and in the pop-up Component Installation Wizard window, copy the application server. Select the option, click the Details button in the corresponding window; then select the Internet Information Services (IIS) option and continue to click the Details button in the corresponding window;

3. The wizard that appears In the settings window, select the World Wide Web service project, and continue to click the details button in the corresponding window, in the wizard interface, select the remote management (html) project; click the OK button and put the Windows 2003 server system The installation CD is placed in the CD-ROM drive and the system will automatically complete 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 http://aaa.aaa.aaa.aaa:8098 address through the IE browser interface (where 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 user can be logged in remotely to the server's management and maintenance page. The network administrator can easily view the log files in the server.