Shulou(Shulou.com)06/02 Report--

Microsoft is best known for its Windows operating system, such as desktop systems such as Windows 7 and Windows 10. After the great success of the desktop system, Microsoft finally entered the server operating system by releasing Windows NT.

This makes Windows NT or Windows Server systems with strong Windows desktop system features: graphical interface, easy to use. Microsoft inherits the characteristics and advantages of the Windows desktop system to the Windows Server system, of course, to release its own advantages once again, because to enter a new field, it is better to make use of existing resources and ideas, rather than completely starting from scratch, so that Windows Server products can be launched quickly.

Microsoft can also advocate the use of Windows Server, which is as easy to use as Windows 7 and can earn more than 10,000 a month if he can type.

Of course, this will also give us practitioners the illusion that we can judge Windows Server by using the experience of Windows 7 or Windows 10, and even come to the conclusion that Windows Server is unstable and a toy.

After all, it is a product of two different scenarios. For Windows desktop systems, ease of use and compatibility is the primary goal, while for Windows Server systems, stability, availability, reliability and expansibility are the preferred goals. Starting from Windows Server 2008, Microsoft has been working on this improvement in the last decade, and this continuous improvement has also led to some confusion in terms of management tools.

For example, there are basically three ways administrators want to know which patches Windows Server has updated:

1. Graphical management tools

This method inherits from the Windows desktop system, click the mouse, easy and easy.

2. Command line tool: wmic qfe list

Command-line tools have some characteristics:

A. you can achieve some more advanced functions, such as saving the patch result as a TXT or HTM file: wmic qfe list / output:d:\ hotfixes.htm qfe list

B. you can write automated scripts, such as bat or cmd

3 、 Powershell: get-hotfix

Powershell looks like a command-line tool, but it is completely different in terms of ease of use, extensibility, and security.

So the next problem that leads to confusion is that without having to list so many, I can complete this task with the first graphical tool, why mess around, and the command line and Powershell are so terrible that I don't know how to start. To solve the problem of tool selection, you still have to look at the scene:

1, one-time task, single server task, graphics chemical industry has the function, click the mouse, it is possible

2. What if I want to get patch updates for all servers and generate HTML or CSV reports? Is it difficult for a server to check with a graphical chemical tool and then write it in a csv file?

3. What if I still want to collect and count all server update reports every month and email the results to the designated administrator regularly? This graphical tool can only show that there is nothing I can do, and my concubine cannot do it.

Not to mention this, more importantly, as a qualified and good Windows Server administrator, you will be powerless to rely solely on graphical management tools:

1. Requirements of high-paying posts

You can take a look at the above job requirements, automation and Powershell are required skills

2. Automation

The administrator's job is to plan, deploy, operate and respond quickly to ensure the availability and reliability of the system, and in this process, there will be requirements from the business, such as

In fact, all you need is a very simple Powershell code.

Import-Module ActiveDirectory$Sid = Read-Host "Input Sid" $ADUsers = Get-ADUser-Filter * foreach ($ADUser in $ADUsers) {If ($ADUser.sid-eq $SID) {write-host $ADUser.Name}}

Another example is to continuously monitor the server's CPU memory, disks and so on. I believe that readers can enumerate a lot of such examples in practical work. And only when we effectively master the automation technology of Powershell, can we calmly face the challenge of high-paying jobs, this step is not that we can easily turn the page with our eyes closed and then opened.

3. The development of Windows Server itself

As we just described for you, Microsoft started from Windows Server 2008, put more emphasis on the stability and reliability of the system on the Windows Server system platform, and gradually increased the deployment mode such as Server Core,Nano Server. After installation, there is no graphical interface at all, and even in the updated version after Windows Server 2016 RTM, the graphical deployment version is no longer available.

At this point, Microsoft is constantly adapting to the changes of the times and technology. As a member of the Windows Server operation and maintenance staff, there is certainly no reason not to embrace change and the future.

Finally, let's talk about the value of this column. Windows administrators go from graphics to Powershell, the easy before the difficult. Powershell challenged our habits from the beginning, so that we couldn't start when we opened the Powershell environment, which was a difficult process, and many people returned to their comfort zone in the challenge, thus hampering their careers and work tasks.

We also hope that through this column, we will focus on common examples in our work, including the most common management tasks, such as network configuration, role installation, server status monitoring, file management, domain service account management, WSUS server cleaning, virtual machine batch creation, and so on.

Through the study of the column, you will not only be able to write Powershell scripts for similar tasks, but more importantly, in this process, we will be able to understand the basic specifications of Powershell, what is the module of Powershell, the command query and usage of Powershell, Powershell remote management features, Powershell variables, judgments, loops, functions and so on. Then the next thing is to practice examples repeatedly and apply them repeatedly in practice, the sense of discomfort and fear will also be eliminated, and the beauty of Powershell will also help us to make our Windows operation and maintenance more professional and professional.

As for the author, he has more than 10 years of Microsoft technical work experience, six consecutive years of Microsoft MVP, Microsoft technical expert, 51CTO gold medal lecturer, recorded more than 1000 hours of courses, long-term use of Powershell improvement and optimization work, Powershell code volume of more than 100, 000 lines.

If you are interested, please come to the 51CTO subscription column "Powershell Automation Operation and maintenance Guide".

The early bird discount is only 39 yuan, with 17 places left.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.