When IIS 7.0 is enabled, you must install Windows powershell snap-in for IIS 7.0
Manage the related platform and settings of IIS 7 in powershell. After the installation is completed, an IIS powershell management instance will be created in the program set.
Console, you can start using these easy-to-use cmdlet immediately after activation. However, this function is already built in the production system of IIS 7.5. It seems to be a good thing, but it cannot
The quick release of snap-in was removed. When I was not familiar with Windows powershell, I still could not find the method for opening the website. I did some work to find out.
On Windows Vista/Windows Server 2008
After powershell snap-in for IIS 7.0, the following release is displayed on the desktop, which is very convenient:
After Windows 7/Windows Server 2008 R2, you cannot install Windows
Powershell snap-in for IIS 7.0 (because it has been created), if you want to install Windows
Powershell snap-in for IIS 7.0 still tells you that you cannot install it ~
The truth is that IIS 7.5 does not regard this item as snap-in, but instead replaces it with the webadministration mode for unknown reasons. Therefore
To use these convenient cmdlet after the Windows powershell login window, you need to manually enter webadministration
This is the only thing you need to do. You may not be able to find this notebook for a long time. It took me a lot of time to study it when I used it for the first time, but what I really want is a convenient and convenient release!
If you want to manually enter the webadministration module, do you know where the most important part is? The answer is:You must know that the model group name is webadministration! Check iis.net files online.
Powershell snap-in
Webadministration mode, so it starts a period of time until the relevant information is found. @_@''
So I will introduce an important command to list the available modules in your computer:
Get-Module -ListAvailable
Administrative organization: the location of the webadministration module is as follows:
%SystemRoot%\system32\WindowsPowerShell\v1.0\Modules\WebAdministration
Therefore, after you start Windows powershell, you must manually import the webadministration module. The command is as follows:
Import-Module WebAdministration
If you want to know which cmdlets or alias are available in the webadministration module, you can also run the following command to check whether:
get-command -pssnapin WebAdministration
When the Web administration module is added,IIS :\Enter a blank name.IIS:You can enter and modify the IIS related information:
Finally, I want to add another method to establish a successful deployment:
1. added a new release.
2. Import the following commands and metric data.
C: \ windows \ system32 \ windowspowershell \ V1.0 \ powershell.exe-noexit
-Command import-module webadministration; Set-location
IIS: \; clear-host
3. Set the release nameIIS powershell
Management
Success!
The next step is to understand how to perform platform management through powershell. Please refer to using scripts to automation management in your article.
Http://blog.miniasp.com/post/2011/06/27/How-to-use-IIS-75-Windows-PowerShell-Snap-in.aspx