How to Secure Windows Server 2003

First of all i want to say nothing is to be secure 100% because every lock have the key.
Security is an increasingly important topic for network administrators. It's an ongoing battle to make sure you've installed all of the latest updates along with keeping up to date with all of the developing threats. Properly securing server begins with planning. When you're deploying Windows Server 2003, now i am going to give you some tips you can use them to protect your window server 2003.

There's an old proverb stating that a chain is only as strong as its weakest link. This is saying is especially true when we are talking about a network's chain of security mechanisms. we know a lot of people who spend countless hours making sure that every packet flowing across the network is authenticated and encrypted, all of the files on the server's hard disk have the proper permissions assigned to them in manor way . Such measures are important, but the fact is that the vast majority of hacks are perpetrated by using legitimate user accounts

In most networks, the user accounts themselves are by far the weakest part of the network's entire security infrastructure. Then a hacker only needs to know two pieces of information (a user name and a password) to be able to access anything on entire network. Sure, encrypting all of the packets as they flow across the wire will help to prevent a hacker from sniffing passwords, but there are plenty of other ways that hackers can acquire passwords.
oldest password acquisition methods still works to That day. That's a brute force crack. Like I said, hacker must have a Id and a password in order to gain full access to network resources. Of course, Microsoft was kind enough to provide the hackers with the ID name for you; Administrator. That means that hackers only need to figure out the Administrator's password in order to gain access to your network.
Microsoft has long recommended that we changed name of Administrator account so that hackers won't know what it is. The problem is that even if you change the account name, the account's SID remains the same. Since Microsoft uses a specific SID for the Administrator account, it's fairly easy to figure out what the account has been renamed to, just by examining the SIDs. In fact, there are even GUI utilities that can automatically tell you what name the Administrator's account is using.