Dealing with Windows 2003 server management problems

cited: In the eyes of many network administrators, managing the server may be a relatively simple thing! However, the fact may not be as easy as we imagined, in different server system environments We may encounter many unique management challenges that seriously affect the efficiency of our management servers.

In the eyes of many network administrators, managing the server may be a relatively simple matter! However, the facts may not be as easy as we think, in different server system environments, we may encounter There are quite a few management challenges that have a serious impact on the efficiency of our management servers. To this end, this article will now summarize some of the server problems that are prone to frequent occurrences, and propose countermeasures for each management problem. I hope that these contents can be useful to everyone!

1. Speed ​​up server login

When we installed Active Directory on the Windows 2003 server system, set up all the workstations in a specific domain, and created the account of the user accessing the server, the workstation user always complained about the current when trying to log in to the server. The login speed is much slower than before. So why after the above settings, we will feel that the server login speed is slower than before, how can we improve the speed of workstation users logging into Windows 2003 server?

In fact, once installed in the server system In the Active Directory, if the "Domain Name System" in the Active Directory is not configured correctly, it will naturally lead to an extended server login time. When the workstation attempts to log in to the server, the location domain controller component used by Active Directory is actually the "domain controller locator", and the domain controller locator accesses the connection DNS server in the format "_ldap._tcp.DnsDomainName". In order to get the service resources required by the workstation user; if the DNS server server is not working properly during this access connection, or if the DC registration operation of the local server is incorrect, then the workstation cannot find the DC when logging in to the server, The speed at which you log in to the server can be severely affected. In fact, in order to solve this kind of failure, we only need to run the Netdiag diagnostic program in the LAN workstation and DC respectively. Through this program, we can quickly find the specific cause of the failure, for example, whether the DNS server is not working properly, or The DC registration operation is not correct. Once the cause of the failure is identified, it is not difficult to easily troubleshoot the slow login of the server.

2, simplify the password for the server

When I try to upgrade the unit's Windows 2003 server system update to a domain controller, I would like to set a simple access password for the unit leader, after all, There are many things to do, and you can't remember complicated passwords with both uppercase letters and lowercase letters and numbers. However, when setting up simple passwords, the domain controller system prohibits the author from creating too simple passwords in the system. This kind of fault prompt, how do we face it?

In fact, the inability to set an overly simple password is due to the default security settings of the Windows 2003 server. We only need to modify the system as follows: The default security settings policy can simplify the password for the server:

First log in to the domain controller system as a super administrator, and click the "Start" button in the system desktop, the system pops up in the beginning In the menu, execute the "Settings" /"Control Panel" command, in the pop-up control panel window, double-click with the mouse Management Tools icon, open the management system list window of the server system;

Secondly, double-click the "Domain Security Policy" icon in the mouse, and in the default domain security settings window that pops up, double-click with the mouse. Windows Settings /Security Settings /Password Policy, in the right side of the corresponding password policy item, find the option "Password must meet the complexity requirements" and right click on the option to pop up Execute the "Properties" command in the shortcut menu to open the property setting window as shown in Figure 1.

Figure 1

Check if the "Disabled" item in the settings window is selected. Status, if you haven't already, you must re-select it in time, click the "OK" button in the dialog box, and then restart the server system. In the future, we can set the domain controller to be relatively simple. The password is gone.

5, let the server process shut down

The easiest way to shut down the server system process is to enter the task manager The process tab page, and select the target process that needs to be closed, and then click the "end process" button. However, the "end process" command is not a panacea, because the "stubborn" service process is being used, or It can't be closed by ending the process. Most of these processes have self-protection or are being called by a specific program. So how can we turn it off in the face of the "stubborn" service process in the server? ??

In the Windows 2003 server system, we can actually use the system's built-in "Ntsd" command to achieve the purpose of forcibly shutting down the server stubborn process. When closing the stubborn process, you can execute "start" /"Run" command, enter the "cmd" string command in the pop-up system run box, click the "OK" button, the system will be automatically switched to the MS-DOS runtime environment;

Then at the command prompt Under the string, enter the string command "ntsd -cq -p process ID" (where the process ID can be viewed through the System Task Manager window) Yes), after clicking the Enter key, you can "force" the specific identified service process; of course, this method does not close all service processes, such as CSRSS.EXE process, SMSS.EXE process, System Processes cannot be closed.

Of course, we can also use some professional killing tools to close the stubborn process. At present, there are many professional tools in this area, such as Kill process, Icesword, process killer, etc. Through these professional tools, we can easily close most processes. For example, when the Process Killer tool is installed on a server system, the tool can automatically streamline the processes in the server and automatically stop all processes other than the server's required processes. For any service process that is running, we can select it in the process list interface of the program, and then execute the "abort process" command.

In addition, some virus processes have their own replication function. It often calls more than one process during the attack. If one of them is forcibly closed, it will be automatically generated by other related child processes. To close such a stubborn process, you can do so through the End Process Tree feature in the Task Manager window. For example, we can select a process called by the virus in the service process tab page, then right-click the name of the process, and then execute the "end process tree" option command in the right-click menu of Figure 3, so that the virus can be called. The series of processes are all closed.

Figure 3