Efficient management of Windows servers

Deny server restart

Under normal circumstances, after the patch is installed in the Windows 2003 Server system, the system will always prompt to restart the server. But many friends often cannot tolerate Windows 2003 Server servers"

"Slow" startup operation, so I hope that the server will not restart after the security patch is applied. In fact, whether the Windows 2003 Server server will restart or not has a certain relationship with the current system patch features

. For those security patches that force the system to boot, the server generally cannot be rejected; but for those patches that do not force the system to boot, the following methods can be taken:

1. On the Windows 2003 Server server system desktop, click the "Start"/"Run" command in turn, in the system run dialog box that opens, enter the string command "cmd", click the "OK" button, and Tie

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 program is located, and then execute the "aaa /?" string command (where aaa is the name of the system patch that needs to be installed at present), followed by

In the prompt interface that appears, check whether the current patch has the "-z" parameter. If it has this parameter, it means that the current patch can not be forced to restart the system after installation;

3. Then in the DOS command line, enter the string command "aaa -z", click the Enter key, the patch will be automatically installed in the system, and the server system will not be required to restart.

Remove restricted access to the server

In order to improve the work efficiency of employees, the unit recently planned to open the access rights of the Windows 2003 terminal server to every employee, but considering the security, the network administrator only provides access to all employees.

The same account is used to log in to Windows 2003 Terminal Server. However, when employees use this account to log in to the terminal server, they find that the server can only allow one person to log in to the server at the same time, and later

As soon as one employee logs into the server, the previous employee is "forced" to log out of the terminal server. What is going on with this phenomenon? Is there a way to make all employees use the same device at the same time?

Can the account be successfully logged in to the server?

In fact, the above phenomenon is mainly caused by the default state of the Windows 2003 terminal server, which enables the "restrict each user to use only one session" function, and canceling it will solve the problem.

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

2. In the configuration window, double-click the "Restrict each user to only one session" option at "Server Settings", and in the Options Settings dialog box that appears, uncheck its checkbox

,"Sure". And restart the server system, so that employees will be able to log into Windows 2003 Terminal Server system at the same time using the same account in the future.

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326897701&siteId=291194637