Three magic keys to managing Windows servers efficiently

foreign media have reported that the Windows Server in terms of revenue ratio, the market is still a distant leader. In view of this, we have gathered some experience in the management of Windows Server for our readers, hoping to bring you a hint of inspiration in our practical work.

Deny server reboot

Typically, after you install a patch on a Windows 2003 Server system, you will always be prompted to restart the server. However, many friends are often unable to tolerate the "slow" Startup of Windows 2003 Server servers, so the server will no longer reboot after a security patch is completed. In fact, whether the Windows 2003 server will reboot is related to the current system patch feature. Security patches that force the system to boot are generally not allowed to be rejected by the server, but for patches that do not enforce the system startup features, the following can be done:

1. On the Windows 2003 Server System desktop, click Start/Run, and then in the Open System Run dialog box, enter the string command "cmd" and switch the system working mode to MS-DOS after clicking the "OK" button;

2. On the DOS command line, switch the current directory to the same directory as the patch by using the "CD" command, and then execute "AAA/?" String command (where AAA is the currently installed system patch name), in the following prompt interface, check if the current patch with the "-Z" parameter, if the parameter, it indicates that the current patch after installation can not force the system to restart;

3. Then in the DOS command line, and then enter the string command "Aaa-z", after clicking Enter, the patch is automatically installed on the system, and the server system is not required to reboot.

Remove restricted access to the server

To improve employee productivity, the organization recently intended to open Windows 2003 Terminal Server access to every employee, but with security in mind, network managers only provided the same account for all employees to log on to Windows 2003 Terminal servers. However, when the employees log on 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, and the former employee is "forced" to exit the Terminal Server login once the employee logs in to the server. What happened to this phenomenon, there is no way for all employees at the same time, using the same account can be successfully logged into the server?

In fact, this phenomenon is mainly due to the Windows 2003 Terminal Server in the default state, the "limit each user can only use one session" feature, the cancellation of which can solve the problem.

1. Start menu, follow the Settings/Control Panel command in sequence, and then double-click the Administrative Tools icon to enter the Terminal Services Configuration window;

2. In this configuration window, double-click the "Restrict each user to use only one session" option in the server settings, and in the Options Settings dialog box that appears later, uncheck the checkbox, "OK". and restart the server system so that employees can log in to the Windows 2003 Terminal Server System at the same time, using the same account number later.

Remotely View server log files

Network management can use the server log files, to achieve the purpose of protecting the security of the server. However, the server's log files are usually only found on the server, but in case the network administrator out of town, how to ensure remote viewing? The Windows 2003 server provides remote maintenance functionality, but is not open by default and requires manual startup.