Windows administrator has a good quality, which is very helpful to solve the problem in the future. It has been stable in solving some system patches and vulnerabilities.
1. The awakening of high authority
Vista’s bad public image makes us clearly aware of the advantages and disadvantages of “low authority” and “high authority”. To paraphrase Churchill, some people have never suffered so much. In our work, we have clearly recognized this, and our user community has also clearly recognized the consequences of ignoring this issue.
2. Workstation is more important than server
Server technology is attractive and rewarding, but the management service level on the workstation is really important. When CFO’s outlook client hangs up, we are responsible for the whole supply chain, from the F9 key of his / her notebook, all switches and routers, to his / her exchange mailbox, we have to check it. No matter what the potential problem is, windows administrators will bravely accept the reality and treat it as an “outlook problem”.
3. Google search, not coding
Compared with the administrators of other systems, we will not add potential security vulnerabilities to our system in order to write specific scripts, even if this will affect repetitive, manual tasks, we will not hesitate. Instead, we will assume that some people have the same problems in some places. We will jump to the most recent browser session and search for a fully tested solution that others have already used.
4. No editor operation
We don’t need the infamous editor. Scripts are good. We admire those who are proficient in VI and Emacs, but we will not “worship” them. If we have to write scripts, we have PowerShell, and most of us are so busy upgrading the other eight qualities that we don’t have time to learn them at all.
Recommended topic: script column – PowerShell
5. We prefer tested solutions
We try not to be cannon fodder. We rely on the world’s largest software companies to check our deployed products, and time proven solutions often outperform the latest and greatest solutions. When a user has something cool to try, we will transfer them to a separate subnet or a new virtual machine on the DMZ.
6. “Autopsy” is the business of consultants
We can be like the next generation of geeks, or we can be like the next generation of geeks to create a miracle that is more “elegant” than “Stuxnet”. But in the end, we have a “party” and an organized category. When we find a problem, we are just as curious about the cause of the problem as anyone else – even if it turns out that we just made a mistake. But usually, we’re too busy with the next release, the next crisis, or the next upgrade to think about them. We know that a serious, fair and excellent autopsy report should be completed by an impartial third party, rather than an exhausted administrator.
7. We know what we don’t know
Although we’ve also dabbled in red hat and Ubuntu, and worked hard to make the Linux machine in our “server farm” work normally, we know that it’s only a short-term dabble, short-term contact with things we don’t know. We’d rather have others maintain applications written entirely in “bash” or “CSH,” especially those without “man page.”.
8. No matter who raised the question, we assume that it is our own
Like others, we can be proud of our expertise in servers and networking products, but in the world of experts, we are just a few small players. If we are CCNA, what we know is not just how to tell Microsoft system center configuration manager how to put the new virtual machine into her system, or how to manage the desktop license through her network. Similarly, we are looking forward to meeting the professional problems raised by temporary users with the same level of expertise as ours, which we think is a good thing. When we need help, we can also consult these users.
9. Network security is also our job
Whether we are the holders of CISSP certificates or not, we should let our enterprises know as much as possible about the security measures in place. This covers almost everything from desktop disk encryption to applications. We will not use “windows is usually the target of attacks” as an excuse to avoid responsibility.
Experience sharing: find out when to follow notes and when to discard cards (restart)
But sometimes we have to restart windows. Of course, we hope we don’t have to. We are worried that the latest patch will affect the stability or bring new vulnerabilities. We often remind ourselves that no one can invade a closed server.
These are the nine qualities that a Windows administrator should have. If you want to learn more wonderful tutorials, please continue to pay attention to the developer website!