Efficient management of Windows Server

Foreign media once reported that Windows servers are still the leader in the market in terms of revenue ratio. In view of this, we have collected some experience and skills on Windows Server Management for the majority of readers and hope to bring you some inspiration in practical work.

Reject server restart

Generally, after installing the patch in the Windows 2003 Server System, the system always prompts you to restart the Server. However, many may not be able to tolerate the "slow" Startup operation on Windows 2003 Server, so they hope that the Server will not be restarted after completing the security patch. In fact, whether the Windows 2003 Server will be restarted has a certain relationship with the current system patch features. For security patches that require system startup, the server cannot be rejected. However, for those patches that do not require system startup features, the following methods can be taken:

1. on the Windows 2003 Server System desktop, click "start"/"run" commands. In the subsequent system run dialog box, enter the string command "cmd ", after clicking the OK button, switch system working mode to MS-DOS state;

2. In the doscommand line, run the "cd" command to switch the current directory to the directory where the patch is located, and then run "aaa /?" In the string command, aaa is the name of the system patch to be installed. In the prompt page that appears, check whether the current patch has the "-z" parameter, if this parameter is set, it indicates that the system cannot be forced to restart after the current patch is installed;

3. then, in the doscommand 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.

Cancel restricted access to the server

In order to improve the efficiency of employees, the Organization recently planned to open the access permission for Windows 2003 terminal server to every employee, but considering the security, network administrators only provide the same account for all employees to log on to the Windows 2003 terminal server. However, when employees use this account to log on to the terminal server, they find that the server can only allow one person to log on to the server at the same time. After the employee logs on to the server, the previous employee is forced to log out of the terminal server. How is this happening? Is there a way for all employees to log on to the server smoothly using the same account within the same time?

In fact, the above phenomenon is mainly because the Windows 2003 terminal server enables the "restrict each user to use only one session" function by default, and the problem can be solved by canceling it.

1. In the "Start" menu, execute the "Settings"/"Control Panel" commands in sequence, and double-click the "Management Tools" icon to enter the terminal service configuration window;

2. in the Configuration window, double-click the "restrict each user to use only one session" option at "Server Settings". In the option Setting dialog box that appears later, deselect the check box and click OK ". Restart the server system so that employees can log on to the Windows 2003 terminal server system with the same account in the future.

Remotely view server log files

Network administrators can use server log files to protect server security. However, the server's log files can only be viewed locally on the server. However, how can we ensure remote access when network administrators leave the door? Windows 2003 Server provides remote maintenance, but it is not activated by default and needs to be started manually.