10 common errors made by new windows Administrators

10 mistakes new windows administrators make
New windows administrators often make 10 mistakes: Author: Debra Littlejohn shinder
Translated by Debra Littlejohn shinder: endurer, category 1st: 10 things, network administration
Classification: 10 things, network management tags: Job, security, Administrator, network, environment, auditing, Deb shinder, Microsoft Windows, recruitment & selection, networking
Job, security, Administrator, network, environment, audit, Deb shinder, Microsoft Windows, recruitment and selection, networking English Source: http://blogs.techrepublic.com.com/10things? P = 467 & tag = NL. e071

Whether you're new to network administration or to the Windows environment, a few common oversights and mistakes can trip you up. deb shinder explains how to avoid some of the problems new windows admins often encounter.
Whether you are a newbie in network management or windows, some common mistakes and mistakes may keep you updated. Deb shinder explains how to avoid some common problems for new windows administrators.

Endurer Note: 1. trip up: (make) make a mistake and trip...

Maybe you're a brand new network admin. you 've taken some courses, you 've ve passed some certification exams, perhaps you even have a Windows domain set up at home. but you'll soon find that being responsible for a company network brings challenges you hadn't anticipated.

Maybe you are a brand new network administrator. You have taken some courses and you have passed some certification exams. Maybe you even have a Windows domain at home. However, you will soon find that the responsible company network brings you any unexpected challenges.

Endurer Note: 1. Take a course: take a course

Or maybe you're an experienced reset ate it person, but up until now, you 've worked in a Unix environment. now-either due to a job change or a new deployment in your current workplace-you find yourself in the less familiar world of windows.

Or, maybe you are an experienced Enterprise IT person, but now you have been working in UNIX environments. Now-either due to work changes or new deployment of your current job-you will find yourself in an unfamiliar Windows world.

This article is aimed at helping you avoid some of the most common mistakes made by new windows administrators.

This article aims to help you avoid the most common mistakes made by new windows administrators.

 

#1: trying to change everything all at once

Trying to change everything at once

 

When you come into a new job, or start working with a new technology, you may have all sorts of bright ideas. if you're new to the workplace, you immediately hone in on those things that your predecessors were (or seem to have been) doing wrong. you're full of all the best practices and tips and tricks that you learned in school. if you're an experienced administrator coming from a different environment, you may be set in your ways and want to do things the way you did them before, rather than taking advantage of features of the new OS.

When you come to a new job or start to work with new technologies, you may have various good ideas. If you are a newbie in the workplace, immediately put your hands on what your predecessor (or looks like already) has done wrong. Your mind is filled with all the best practices, skills, and tips you have learned at school. If you are an experienced administrator from different environments, You may set your approach and want to follow the previous approaches to handle these tasks, rather than taking advantage of the features of the new operating system.

Either way, you're likely to cause yourself a great deal of grief. the best bet for someone new to Windows networking (or to any other job, for that matter) is give yourself time to adapt, observe and learn, and proceed slowly. you'll make your own job easier in the long run and make more friends (or at least fewer enemies) that way.

In short, you may cause a lot of trouble to yourself. For a newbie who has a Windows Network (or any other job for this problem), the best bet is to give yourself time to adapt, observe and learn, and perform slowly. In this way, in time, you will make your work easier and make more friends (or at least reduce enemies ).

Endurer Note: 1. Either way: Ad. In short (either way, both sides)

#2: overestimating the technical expertise of end users

Overestimated technical knowledge of end users

Please new administrators failed CT users to have a better understanding of the technology than they do. don't assume that end users realize the importance of security, or that they will be able to accurately describe the errors They're getting, or that they know what you mean when you tell them to perform a simple (to you) task such as going to Device Manager and checking the status of the sound card.

Many new administrators expect users to have a deep understanding of the technologies they use, which is too high. Do not assume that end users understand the importance of security, they can accurately describe the errors they encounter, or when you tell them to execute a simple task (for you, for example, enter the Device Manager and check the sound card status. They can understand what you mean.

When people in the business world use computers every day but know very little about them beyond how to operate a few specific applications. if you get frustrated with them, or make them feel stupid, most of them will try to avoid calling you when there's a problem. instead they all ignore it (if they can) or worse, try to fix it themselves. that means the problem may be far worse when you finally do become aware of it.

Many people in the business world use computers every day, but little is known about knowledge beyond how to operate a few specific applications, but if you are disappointed with them or make them stupid, most of them will try to avoid calling you when there is a problem. Instead, they will ignore it (if they can) or, worse, try to fix it themselves. This means that when you finally notice this, the problem may be more serious.

#3: underestimating the technical expertise of end users

Underestimating end users' technical knowledge

Although the above applies to evaluate of your users, most companies will have at least a few who are advanced computer hobbyists and know a lot about technology. they're the ones who will come up with valid tive workarounds to circumvent the restrictions you put in place if those restrictions inconvenience them. most of these users aren't malicious; they just resent having someone else in control of their computer use-especially if you treat them as if they don't know anything.

Although the above applies to many of your users, there are at least some advanced computer fans and many technologies in most companies. When your restrictions make them feel inconvenient, they will bypass them. Most of these users are not malicious, but are dissatisfied with others' control over their use of computers-especially if you think they do not know anything about them.

Endurer Note: 1. Come up with: Come up; come up
2. Put in place: Set and arrange
3. Treat as: Treat

The best tactic with these users is to show them that you respect their skills, seek out their input, and let them know the reasons for the rules and restrictions. point out that even a topnotch racecar driver who has demonstrated the ability to safely handle a vehicle at high speed must abide by the speed limits on the public roads, and it's not because you doubt his/her technology skills that you must insist on everyone following the rules.

The best strategy for these users is to show them that you respect their skills, seek their opinions, and let them know the reasons for making rules and restrictions. Even top drivers who have demonstrated the ability to operate high-speed vehicles safely must comply with speed limits on the road. This is not because you suspect his/her technical skills, but because everyone must follow the rules.

#4: not turning on Auditing

Audit function not enabled

Windows server operating systems have built-in security auditing, but it's not enabled by default. it's also not one of the best supported ented features, so some administrators fail to take advantage of it. and that's a shame, because with the auditing features, you can keep track of logon attempts, access to files and other objects, and Directory Service Access.

Windows Server OS has built-in security audit function, but it is disabled by default. It is not one of the most worthy features of the book, so some administrators have not been able to use it. This is a pity because the audit feature allows you to track logon attempts, access to files and other objects, and access to directory services.

Active Directory domain services (ad ds) auditinghas been enhanced in Windows Server 2008 and can be done more granularly now. without either the built-in auditing or third-party auditing software running, it can be almost impossible to pinpoint and analyze what happened in a security breach.

In Windows Server 2008, the audit of the Active Directory domain service (ADDs) has been enhanced and can be done in more detail now. Without a built-in audit or third-party audit software, it is impossible to precisely identify and analyze what security vulnerabilities have occurred.

#5: Not keeping systems updated

System updates not maintained

This one ought to be a no-brainer: keeping your servers and client machines patched with the latest security updates can go a long way toward preventing downtime, data loss, and other consequences of malware and attacks. yet administrators fall behind, and their networks are running systems that aren't properly patched.

This should be a good idea: keeping your servers and clients patched with the latest security updates can greatly help prevent downtime, data loss, and the consequences of other malware and attacks. However, many administrators are lagging behind, and their networks are running systems that are not properly patched.

This happens for several reasons. understaffed and overworked it except ments just may not get around to applying patches as soon as they're released. after all, it's not always a matter of "just doing it"-everyone knows that some updates can break things, bringing your whole network to a stop. thus it's prudent to check out new patches in a testbed environment that simulates the applications and deployments of your production network. however, that takes time-time you may not have.

There are several reasons for this. IT departments with insufficient manpower and excessive work cannot apply patches immediately after they are released. After all, this is not always a "just do it" problem-everyone knows that some updates may cause damage and stop your entire network. Therefore, it is prudent to check the new patch in the application simulating your product network and the test environment of the configuration. However, this takes time-you may not have time.

Automating the processes as much as possible can help you keep those updates flowing. have your test network ready each month, for instance, before Microsoft releases its regular patches. usewindows Server Update Services (WSUS) or other tools to simplify and automate the process once you 've decided that a patch is safe to apply. and don't forget that application-not just the operating system-need to be kept updated, too.

Automating the process as much as possible can help you keep these updates uninterrupted. For example, before Microsoft releases its regular Patch, you can prepare your testing network on a monthly basis. Once you confirm that a patch is secure, use the Windows Server Update Service (WSUS) or other tools to simplify and automate the process. Do not forget that applications-not just operating systems-must be constantly updated.

#6: Getting sloppy about security

Rashly deal with security work

Administrative administrators enforce best security practices for their users but get sloppy when it comes to their own workstations. for example, IT pros who wowould never allow users to run XP every day logged on with administrative accounts think nothing about running as administrators themselves while doing routine work that doesn't require that level of privileges. some administrators seem to think they're immune to malware and attacks because they "know better. "But this over confidence can lead to disaster, as it does in the case of police officers who have a high occurrence of firearms accidents because they're around guns all the time and become complacent about the dangers.

Many administrators perform the best security measures for their users, but they are very hasty when they come to their workstation. For example, IT experts who never allow users to run Windows XP with an administrator account every day did not think that they do their daily work without such permissions as administrator. Some managers seem to think they are not affected by malware and attacks because they "Know More ." However, this excess self-confidence can lead to disasters. In the same case, police officers with a high incidence of gun fire accidents are often complacent about the dangers because they are always dealing with guns.

Endurer note:
1. Getting sloppy: hasty
2. Routine work: Daily Work
3. Be immune to: not affected. It is immune...
4. play around with gun: play with guns

#7: Not documenting changes and fixes

Unrecorded changes and repairs

Documentation is one of the most important things that you, as a network admin, can do to make your own job easier and to make it easier for someone else to step in and take care of the network in your absence. yet it's also one of the most neglected of all administrative tasks.

One of the most important things for you as a network administrator is to log on to the book. It makes your work easier and makes it easier for others to participate in and take care of the network when you are absent. However, this is the easiest option to ignore in all administrator tasks.

You may think you'll remember what patch you applied or what configuration change you made that fixed an exasperating problem, but a year later, you probably won't. if you document your actions, you don't have to waste precious time reinventing the wheel (or the fix) all over again.

You may think that you will remember the modifications made to the configuration when your application patches or when you fix deteriorating problems, but you may not be able to do so in a year. If you write down your operations, you don't have to waste precious time repeat all of them.

Some admins don't want to document what they do because they think that if they keep it all in their heads, they'll be indispensible. in truth, no one is ever irreplaceable-and by making it difficult for anyone else to learn your job, you make it less likely that you'll ever get promoted out of the job.

Some administrators don't want to record what they do, because they think they are indispensable if they save it in their heads. In fact, no one is irreplaceable-and by making it difficult for others to understand your job, you make your hopes of promoting from the job smaller.

Besides, what if you got hit by a truck crossing the street? Do you really want the company to come to a standstill because nobody knows the passwords to the administrative accounts or has a clue about how you have things set up and what daily duties you have to perform keep the network running smoothly?

What should I do if you are hit by a car while you are crossing the street? You really want the company to get stuck, because no one knows the password of an account with administrative permissions, or there is no clue about how you set up, and you have to execute the daily work to keep the network running smoothly?

#8: Failing to test backups

No test backup

One of the things that home users end up regresponthe most is forgetting to back up their important data-and thus losing it all when a hard drive fails. most IT pros understand the importance of backing up and do it on a regular schedule. what some busy adminsDon'tRemember to do regularly is test those backups to make sure that the data really is there and that it can be restored.

One of the regrets of family users is that they forget to back up their important data-and thus lose it when the hard drive is broken. Most IT professionals understand the importance of backup and regularly back up data. Some busy administrators do not remember to regularly check the backups to ensure that the data is indeed there and can be recovered.

Remember that making the backup is only the first step. You need to ensure that those backups will work if and when you need them.

Remember that creating a backup is only the first step. Make sure that the backups work as needed.

Endurer Note: 1. End Up: end, end

#9: overpromising and underdelivering

Let's talk less about things and do more practical work.

When your boss is pressuring you for answers to questions like "When can you have all the desktop systems upgraded to the new version of the software ?" Or "How much will it cost to get the new database server up and running ?", Your natural tendency may be to give a response that makes you look good. but if you make promises you can't keep and come in late or over budget, you do yourself more damage than good.

When the boss oppress you to give "When can you upgrade all the desktop systems to the new version ?" Or "How much does it cost to upgrade and run the database server ?" When you answer such a question, you will naturally tend to give a response that may make you look good. However, if you make a promise that you cannot maintain, delay, or exceed your budget, you will make yourself fierce.

Endurer Note: 1. He has done more harm than good. He is more profitable.

A good rule of thumb in any business is to underpromise and overdeliver instead of doing the opposite. if you think it will take two weeks to deploy a new system, give yourself some wiggle room and promise it in three weeks. if you're pretty sure you'll be able to buy the hardware you need for $10,000, ask for $12,000 just in case. your boss will be impressed when you get the project done days ahead of time or spend less money than expected.

The good rule of thumb in any enterprise is to talk less about things and do more practical work instead of doing the opposite. If you think it takes two weeks to deploy a new system, give yourself some room for maneuver and ensure that it is completed within three weeks. If you're pretty sure you need $10000, you can purchase the hardware. You need $10000 to avoid unexpected costs. The boss is impressed when you finish the project or spend less money than expected.

Endurer Note: 1. Rule of thumb: Empirical Law (estimation by experience)
2. Wiggle Room: room for maneuver or adjustment
3. Just in case: in case

#10: being afraid to ask for help

Fear for help

Ego is a funny thing, and has it administrators have a lot of investors in theirs. when it comes to technology, you may be reluctant to admit that you don't know it all, and thus afraid-or embarrassed-to ask for help. I 've know mcses and MVPs who couldn't bear to seek help from colleagues because they felt they were supposed to be the "experts" and that their reputations wocould be hurt if they admitted otherwise. but plunging ahead with a project when you don't know what you re doing can get you in hot water, cost the company money, and even cost you your job.

Self-esteem is an interesting thing. Many IT administrators invest heavily in themselves. When you encounter technical problems, you may be reluctant to admit that you do not fully understand, so you are afraid-or embarrassed-to seek help. I know that some MCSE (Microsoft Certified System Engineers) or MVPs (most valuable experts) cannot bow to asking for help from colleagues because they think they are considered "experts". If they admit they do not understand, honors will be compromised. However, if you are in a project, you do not know what you are doing will put you into trouble, at the cost of the company's funds, or even your work.

If you're in over your head, be willing to admit it and seek help from someone more knowledgeable about the subject. you can save days, weeks, or even months of grief by doing so.

If you do not know what is going on, you are willing to acknowledge and ask those who are more competent in this aspect. In this way, you may suffer from a few days, weeks, or even months.

Endurer Note: 1. over one's head: beyond one's understanding