Windows Server Management Tips Summary

I believe everyone is no stranger to the term Windows Server. Today, Xiaobian has compiled some experience and skills in Windows server management. I hope to help you in your future work.

Remotely viewing server logs File

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 .

Denying Server Restart

In general, after installing the patch on Windows 2003 Server, 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 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”, click the <;OK" 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 “aaa /?&rdquo The 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 parameter "-z", if it has this parameter, it indicates the current After the patch is installed, you can not force the system to restart;

3. Then in the DOS command line, enter the string command “aa a -z”, after clicking the Enter key, the patch will be automatically installed into the system and the server system will not be required to reboot.

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 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 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, the above phenomenon is mainly due to Windows. In the default state of 2003, the terminal server enabled the "Restrict each user can only use one session" function, and canceled it to solve the problem.

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 "Only one user can 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.

Xiaobian summarizes some tips for effectively managing servers. Although you may have mastered a lot of skills in this area, there are still many techniques in server management waiting for everyone's summary. You also have some novel tips or tricks, please let us know in the comments below.