Windows Server efficiently manages three magic weapons

Foreign media have 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 in Windows server management for the readers, and hope to bring you in practice.

Foreign media has reported that the proportion of Windows server revenue is still on the market. The leader of the distance. In view of this, we have collected some experience and skills in Windows server management for the readers, and hope to bring you a little inspiration in the practical work.

Denying server restart

In general, after installing the patch on Windows 2003 Server system, the system will always prompt you to restart the server. However, many friends often cannot tolerate the Windows 2003 Server server's "slow" operation, 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 who require mandatory system startup security patches, usually can not make the server refused; but for those patches are not mandatory for the system start-up characteristic, it may take the following measures:

1. On the Windows 2003 Server server system desktop, click the “Start” "Start”/“Run” command, in the subsequent system run dialog box, enter the string command “cmd”, click “ After confirming the 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 the name of the system patch that needs to be installed currently), in the prompt interface that appears later, check whether the current patch has the "-z" parameter, if with this parameter, then it indicates that the current patch after installation may not be mandatory system restart;

3. Next, at the DOS command line, lose String command & ldquo; aaa -z & rdquo ;, click the Enter key, the patch will automatically install the system, and does not require the server to restart the system.

Unblocking Access to Servers

In order to improve employee productivity, the organization recently planned to open access to Windows 2003 Terminal Server to every employee, but For security reasons, network administrators only provide the same account for all employees to log in to Windows 2003 Terminal Server. However, when employees log in to the terminal server with the 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 quit the terminal server. Login. This phenomenon in the end is how it happened, that there is no way to get all employees at the same time using the same account can successfully log on a server it?

In fact, The above phenomenon is mainly caused by the fact that the Windows 2003 terminal server is enabled by default, and the function of "restricting each user can only use one session" can be solved by canceling it.

1. “ Start & rdquo; menu, in turn, execute the "Settings" <;&" control panel” command, and then double-click the "Administrative Tools" icon to enter the terminal service configuration Window;

2. In the configuration window, double-click on the "Server Settings" button to limit the "Every user can only use one session" option, and the option settings that appear after it. In the dialog box, uncheck its checkbox, “OK”. 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.

Remotely viewing server log files

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 .