Three Tips for efficient Server Management

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 /?" String command (aaa is the name of the system patch to be installed). On the prompt page that appears, check whether the current patch contains 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.

1. Check whether the II6.0 component and its related components have been installed on the Windows 2003 Server. If the components have not been installed, install them on the server first;

2. in the "Start" menu, click "Settings", "Control Panel" commands, and "add or delete programs" icon, then, click the "Add/delete Windows Components" button on the page and select the "Application Server" option in the pop-up component Installation Wizard window, click the "details" button in the corresponding window, select the "Internet Information Service (IIS)" option, and click the "details" button in the corresponding window;

3. in the displayed wizard settings window, select the "World Wide Web Service" project and click the "details" button in the corresponding window. In the displayed wizard interface, select the "Remote Management (html)" project, click the "OK" button, and put the installation CD of the Windows 2003 Server system into the optical drive, then the system automatically completes the remaining installation and setting tasks.

After, network administrators no matter where you go, as long as you can find a computer that can access the Internet, and enter the IE browser interface "http://aaa.aaa.aaa.aaa: 8098" address (which aaa. aaa. aaa. aaa indicates the valid IP address of the Windows 2003 Server). On the server account verification page that will be opened later, enter the system administrator account correctly to remotely log on to the server management and maintenance page, on this page, the network administrator can conveniently view the log files on the server.

Related Articles]

• Top 10 server management errors that CTO must keep in mind

• Virtual Server management experience and skills