-
Posted to
IIS 7.0 - PowerShell
by
JeongHwan
on
09-25-2009, 1:58 PM
You cannot use the object value as a site id value as you thought. :-)
Here is one of the way to use the ID as a number value.
$test = (Get-ChildItem IIS:\Sites|select-object -last 1).id
FYI, here is the way to check the data type.
PS IIS:\sites> (Get-ChildItem IIS:\Sites|select-object -last 1|format-list id | select ...
-
Posted to
IIS 7.0 - PowerShell
by
JeongHwan
on
09-25-2009, 1:48 PM
FYI,
I'd like to imform that Add-PSSnapin cmdlet should not be used if your machine is installed with Win7 OS. Only Import-module cmdlet should be used in that case. :-)
-
Posted to
IIS 7.0 - PowerShell
by
JeongHwan
on
09-24-2009, 7:58 PM
Snapin name is changed to Webadministration on IIS Powershell RTW build.
So, "Add-PsSnapin WebAdministration" is the right way instead of "Add-PsSnapin IISProviderSnapin".
-
Posted to
IIS 7.0 - PowerShell
by
JeongHwan
on
09-24-2009, 7:46 PM
BTW, I was wrong Microsoft.AppHostQueryProcessor is not related to IIS Powershell. Actually it is one of IIS component files in Win7.
Please check the COM file is registered in your Win7 machine by searching the string "Microsoft.AppHostQueryProcessor" or class id "688eeee5-6a7e-422f-b2e1-6af00dc944a6" ...
-
Posted to
IIS 7.0 - PowerShell
by
JeongHwan
on
09-24-2009, 7:30 PM
I tried my program on Win7 and it worked well.
BTW, I think you should check why the get-website is not recognized as the name of a cmdlet because the Get-WebSite is a valid cmdlet name on Win7 build.
Maybe you can follow this on DOS prompt if you are not familiar about how to start IIS Powershell ...
-
Posted to
IIS 7.0 - PowerShell
by
JeongHwan
on
09-24-2009, 6:04 PM
Hi,
I can't reproduce the problem.
And I don't see the product id of "Microsoft.AppHostQueryProcessor" is used by IIS Powershell on RTW (Go Live) build.
Are you using old version? Or, please try your program in a clean machine with the IIS Powershell RTW (Go Live) build.
I executed the below program and I did not see ...
-
Posted to
IIS 7.0 - PowerShell
by
JeongHwan
on
09-17-2009, 5:39 PM
I am not clear about your scenario but I guess, you are trying to remove a certain binding but if the target site has only that binding you want to get exception instead of removing the binding. Am I right? If so, I think you can use this script code for that purpose.
if ($null -ne (Get-WebBinding -name "Default Web ...
-
Posted to
IIS 7.0 - PowerShell
by
JeongHwan
on
09-02-2009, 5:03 PM
Hi,
Thanks a lot for your feedbacks. I am going to report the design change request to support powershell script from config editor.
Jeong Hwan Kim
-
Posted to
IIS Search Engine Optimization Toolkit
by
JeongHwan
on
08-11-2009, 4:50 PM
Thanks for the error report. I am going to investigate this issue and log a new bug if we don't have any bug on this issue yet.
-
Posted to
IIS 7.0 - PowerShell
by
JeongHwan
on
08-05-2009, 7:11 PM
We were able to reproduce your issue. It is a product issue and we will fix it some day in future. The issue we found is that if there is no web sites, the new-website cmdlet does not work with showing the error message. Please let me know if this is not your case and we will investigate more.
FYI, another work-around regarding the ...