PowerShell extension--powershell from the third of the zero-start series

In the previous article we introduced the basic PowerShell commands, which the attentive reader may have discovered: Why is PowerShell's command so little??? Seems to be unable to manage the application ah???

Emmm~~ in fact, PowerShell has a strong scalability, and many Microsoft and third-party vendors have integrated PowerShell commands

such as Microsoft's own Active Directory, Exchange, LYNC\SFB, SharePoint, SCCM, SCOM, SQL Server

or third-Party vendor VMware Vcenter, Citrix's XenDesktop, etc.

But it is important to note that although there are many PowerShell commands for managing a specific product, there is only one Windows PowerShell. There is no Exchange PowerShell, there is no Active Directory PowerShell, there is only one PowerShell

All of these PowerShell commands that manage a specific product are Windows PowerShell-based extensions

Now let's take a brief introduction to the PowerShell extension:

• Snap-in (PSSnapin)

• Modules (module)

A snap -in typically contains one or more DLL files, along with the XML and Help files for configuration settings. But the concept of snap-in is being gradually removed, and the future will be less

modules are more independent and do not require complex registration to be used.

Now let's try adding extensions in PowerShell:

Start by get-pssnapin-registered view to determine which extensions the current computer has

Add the snap-in you want to use with the Add-pssnapin command

Now you're ready to use the extended command.

Next try to add the module , again we first try to see the module

Emmm~~ has a lot

Importing modules using commands

You can now manage your ad through PowerShell.

Well, the basic method is introduced to this, we can try to add according to their own needs, to see if it can not be used properly

PowerShell extension--powershell from the third of the zero-start series