Tips for Windows 2003 Server Management Challenges

In the eyes of many network administrators, the management of the server may be a relatively simple thing! However, the facts may not be as easy as we might think, in different server system environments, we may encounter a number of different management challenges, these management challenges seriously affect the efficiency of our Management Server.

1, speed up the server login

When we have the Active Directory installed in the Windows 2003 Server system and all the workstations in a particular domain are set up, and the user accesses the server's account, the workstation user, when attempting to log on to the server, always complains that the current logon speed is much slower than before. So why do we have to be able to increase the speed at which a workstation user logs on to a Windows 2003 server when the server is logged slower than before?

In fact, once the Active Directory is installed in the server system, if the "Domain Name System" in the Active Directory is not configured correctly, it will naturally cause the server to log on longer. When the workstation attempts to log on to the server, the location domain controller component used by the Active Directory is actually the domain controller locator, and the domain controller locator follows the _LDAP._TCP. DnsDomainName "This format accesses the DNS server to get the service resources that the workstation user wants; If the DNS server server fails to work properly during this access connection, or if the local server's DC registration operation is incorrect, The workstation will not be able to locate the DC when it logs on to the server, so the speed of the login server can be severely affected. In fact, in order to solve this problem, we only need to run the Netdiag diagnostics in the LAN workstation as well as the DC, we can quickly find the specific cause of the failure, such as whether the DNS server is not working properly, or the DC registration operation is incorrect, once the cause of failure is found, It is not difficult for us to easily eliminate the slow server login failures.

2, to simplify the password for the server

When the author tries to upgrade the unit Windows 2003 Server System update to a domain controller, I would like to set a relatively simple access password for the unit leader, after all, the leadership of many things, usually remember not to have both uppercase and lowercase letters and numbers of complex passwords; but when you actually set up a simple password, Domain Controller system to prohibit the author in this system to create too simple password, in the face of this fault prompts, how exactly should we face it?

In fact, the inability to set overly simple passwords is caused by the default security settings for Windows 2003 servers, and we can simplify the password for the server by modifying the default security settings policy for the system as follows:

First log in to the domain controller system as a super administrator, and in the System desktop, click the Start button, in the pop-up system "start" menu, followed by the "Settings"/"Control Panel" command, in the Pop-up Control Panel window, double-click the "Administrative Tools" icon, open the Server System Management tool List window;

Second, double-click the "Domain Security Policy" icon in the mouse, in the Default Domain security Settings window that pops up, double-click Windows Settings/Security Settings/password policies and, in the right-hand display window of the corresponding password policy item, find the option "Password must meet complexity requirements". Using the right mouse button to click the option, execute the Properties command from the pop-up shortcut menu, and open the property Settings window as shown in Figure 1.

Figure 1

Check to see if the disabled item in the Settings window is selected. If not, you must select it in time, click the OK button in the dialog box, and then restart the server system so that we can set up a simpler password in the domain controller.