Efficient management of Windows Server's three-axe

Foreign media has 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 a little inspiration in the practical work. Rejecting a Server Reboot In general, after installing a patch on a Windows 2003 Server system, the system always prompts 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 security patches that are forced to start the system, it is generally impossible for the server to refuse. However, for patches that do not require the system startup feature, you can do the following: 1. On the Windows 2003 Server server system desktop, click Click the “Start” "Start”/“Run” command. In the subsequent system run dialog box, enter the string command “cmd”, 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 “aaa /? ” string command (where aaa is the name of the system patch that needs to be installed currently), in the prompt interface that appears after it, check whether the current patch has the parameter "-z", if it has this parameter, it indicates The current patch may not be required to restart after the installation is complete; 3. Then in the dos command line, enter the string command “aaa -z”, after clicking the Enter key, the patch will be automatically installed. Go to the system and do not require the server system to reboot. Unrestricted Access to Servers In order to improve employee productivity, the organization recently intended 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. What is going on in this phenomenon? Is there any way for all employees to log in to the server with the same account at the same time? In fact, the above phenomenon is mainly due to 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 Services Configuration window; 2. In the In the configuration window, double-click on the "Server Settings" option to limit each user to use only one session. In the option settings dialog box that appears, uncheck the check box. ,“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 NMS can fully utilize the server's log files to protect the server. However, the server's log files can usually only be viewed locally on the server, but in case the network administrator goes out, how to ensure remote viewing? The Windows 2003 server provides remote maintenance, but it is not enabled by default and needs to be started manually.