Clever out incur WINS server management

Efficient Management Server has been inseparable from effective server management skills, although you have mastered many of these skills, but the server has a lot of skills waiting for your summary, waiting for your excavation; This is not, some of the following server management tips are the author in the recent work summed up, I believe there are a lot of you have rarely encountered!

Deny server reboot

Typically, you will be prompted to reboot the server after the patch is installed in the Windows 2003 Server System. But many impatient friends, who often cannot tolerate the "slow" Startup of Windows 2003 Server servers, have come to the idea that the server will no longer restart after a security patch has been completed. So is there an appropriate way to make Windows 2003 Server servers not reboot after installing patches? In fact, the Windows 2003 Server servers will reboot, with the current system patch characteristics have a certain relationship; For those security patches that force the system to boot, we generally cannot allow the server to refuse to reboot, but for patches that do not enforce the system boot feature, we can do the following to prevent the server system from restarting:

First, in the Windows 2003 Server System desktop, click Start/Run, and then in the system Run dialog that opens later, enter the string command "cmd" and switch the system working mode to MS-DOS after clicking the OK button;

Second, 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;

Then in the DOS command line, and then enter the string command "Aaa-z", the patch is automatically installed on the system and the server system is not required to reboot once the return key is clicked.

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, the above phenomenon, this is mainly due to the fact that Windows 2003 Terminal Server, by default, has the "restrict each user to only one session" feature enabled; To eliminate this, you just need to follow these steps to cancel the "restrict each user to only one session" feature:

First, click the Start menu in the Windows 2003 Terminal Server System desktop, follow the Settings/Control Panel command in sequence, and then double-click the Administrative Tools icon to enter the Terminal Services Configuration window;

Then in the Configuration window, double-click the "Restrict each user to use only one session" option at the server settings, and in the Options settings dialog that appears later, uncheck the "Restrict each user to use only one session" checkbox, and then click OK. and restart the server system so that employees will be able to log into the Windows 2003 Terminal Server System at the same time using the same account number.

Remotely View server log files

If you are a careful person, can use the server log files, to achieve the purpose of protecting the security of the server, after all, any illegal attacks on the server will be in the server log files left clues, as long as you are careful enough to know whether the server is currently under attack, once found that there are attack traces, As long as the appropriate response measures in a timely manner to ensure the security of the server. But then again, the server log files can only be found in the server local, but in case of network management personnel out of town, how to ensure that the server log files can be remotely viewed by network managers at any time?

To do this, you just take advantage of the remote maintenance of Windows 2003 server, and through the IE browsing interface, you can remotely view the log files of the server, of course, the default state, the Windows 2003 Server Remote Maintenance function is not open, we need to manually start. The following are the steps to remotely view the server log file:

First check to see if the Windows 2003 server has installed the II6.0 components and their associated components, if not installed, you must first install these components to the server;

Next on the server System desktop, on the Start menu, clicking Settings, click Control Panel, and then, in the window that appears, double-click the Add or Remove Programs icon, click the Add/Remove Windows Components button in the subsequent interface, and in the Component Installation Wizard window that pops up, Select the "Application Server" option and click the "Details" button in the corresponding window.

You will then see a setup interface as shown in Figure 1, select the Internet Information Services (IIS) complex option, and then continue clicking the Details button in the corresponding window;

Figure 1

In the Wizard Settings window that appears, select the World Wide Web Service project. and continue to click the "Details" button in the corresponding window, in the wizard interface shown in Figure 2, and then select the remote Management (HTML) item, when you are finished, click the OK button and turn windows 2003 the installation CD of the server system is put into the optical drive, and then the system will automatically complete the remaining setup tasks;

Figure 2

Later, no matter where the network manager goes, as long as can find a computer that can be connected to the Internet, and through IE browser interface enter "http://aaa.aaa.aaa.aaa:8098" address (where AAA.AAA.AAA.AAA represents windows 2003 Server's valid IP address, in the later Open Server account verification interface, the correct input system administrator account, you can log on to the server's management Maintenance page, in which the network manager can easily view the server log files.

Insinuate to decrypt the server

If you accidentally forget the Windows 2000 Server's Super Admin password, you will not be able to log in to the server system to maintain and manage it. In this case, most people will choose to reinstall the server system, but so that any important information on the server will not be recoverable. Is there any way to decrypt the server that has forgotten the login password without affecting the server information? The answer is yes, you can just follow the following methods:

First from the Internet search and download the Ntfsdos Professional program, and in accordance with the usual way to install it to other normal log on to the Windows 2000 Server;

Once the program is installed, you can see the Ntfsdos Professional Boot Disk Wizard icon appears in the system's Start menu, click the icon to open a wizard interface, and follow the prompts to generate two windows 2000 DOS boot disk for server system;

With the Windows 98 boot CD, you can start the Windows 2000 system that cannot log on directly into a pure DOS system, insert the DOS boot disk of the Windows 2000 Server system into the floppy drive, and then type "Ntfspro.exe" at the DOS command prompt String command, the command quickly lists all NTFS partition discs in the server system after the return key is clicked;

Then with the help of CD command, the current directory to switch to Winnt\system32\config, and then use the "del" command to delete the Sam file, and finally the server system restart, when the server system login interface, as long as the direct "OK" button to re-enter the Windows 2000 Server System.

Automatic Publishing Server startup information

In order to allow the unit staff to access the information in the LAN server in time, there is no way to let the server start, it can automatically notify the startup information to employees, so that all employees can access the first time LAN server? To do this is actually very simple, just generate a startup information notification script, Then let the server run the script automatically during startup. The following is the specific implementation step of the method:

Run any text editing tool first, and enter the following command code in the edit window:

@echo off

NET send * Please staff access to the server

The above command code file is then saved as a batch file with an extension of "bat", for example, where the author saves the file as "Start.bat", where the "net send * Please staff Access server" command, which means "Please staff access to the server" The information is automatically distributed to all workstations of the LAN;

Click the start/Run command below, follow the "Poledit" command in the pop-up system run box, click the "file", then the "Open Registry" option in the window, and then double-click the local computer icon;

In the interface that pops up as shown in Figure 3, expand the System directory, select the Run item, click the Show button, click the Add button in the display content interface, and then lose the absolute path to the Start.bat file, and then click OK.

Figure 3

Next, in the System policy editing interface, click the file/Save command again, so that the message notification script can be saved to the system registry, and then the server will be automatically released to all workstations during the startup process.