-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
09-23-2009, 3:23 AM
See my reply on another thread, it is applicable here too. Main difference for you will be hosting PowerShell from inside of PHP. I am not familiar how PHO could execute managed code, but you probably could only start it as separate process, in this case you have to write your script that will take credentials as parameters and execute start-job ...
-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
09-23-2009, 3:10 AM
Yes, jobs are v2.0 feature. This version is actually already released in Windows 7 and will be released downlevel very soon. You could use it for development, it is very stable. Hosting PowerShell is generally the same in both v1.0 and v2.0. You could start with that.
--Sergei
-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
09-22-2009, 5:23 PM
I believe you could work around the problem with worker process identity by using PowerShell jobs. Here is how I would approach it (I am planning to write blog post on this topic some time).
1. In your Web application add code that hosts PowerShell. This is fairly trivial. This instance of PowerShell will run at whatever identity worker process ...
-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
09-02-2009, 1:41 AM
Worker process doesn't have an access to the whole configuration system. It is by design. PowerShell snapin will report access problem, that may or may not be reported in the log. As far as I know, we didn't test the snapin when hosted in the worker process.
--Sergei
-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
09-02-2009, 1:20 AM
I don't see these reported issues as a bug, snapin was designed this way and this is an expected behavior. The fact that you all are getting into that with PowerShell is just a specific case, you will see the same behavior with most of other APIs to configuration system, when you run them from worker process. To fix this we either should ...
-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
08-05-2009, 12:36 AM
Corey, I opened bug with your findings for this issue. As soon as we will be able to reproduce this problem, I will have more information.
Thanks,
Sergei
-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
08-04-2009, 12:43 AM
Hi Matt!
Unfortunately, it is a bug in our code for this command. Sorry about that and thanks for reporting it. We will fix it in our next refresh of IIS snapin.
You could use low level command to set binding value for https protocol:
set-webconfigurationproperty ...
-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
08-04-2009, 12:09 AM
Corey, if IIS is not installed, Powershell snapin cannot be installed, or will not work -- because configuration system is not available. So there is something unusual with your setup.
I cannot reproduce your issue on any of my machines, I will ask our tester tomorrow to look to this . Meanwhile you could try a workaround -- new-website command ...
-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
08-03-2009, 7:56 PM
I was asking you to run your commands line by line, as I did. Sometimes in the script variables are assigned not the way you expect them to be.
My understanding is that you use release version of IIS snapin, right?
Thanks,
Sergei
-
Posted to
IIS 7.0 - PowerShell
by
sergeia
on
08-03-2009, 7:43 PM
Cory, which version of PowerShell are you running? I just tried this on Windows Server 2008 R2 (which has PowerShell v2.0 but the same exactly IIS snapin):
PS I:\websites> $websiteDir = dir i:\websites
PS I:\websites> $websiteDir
Directory: ...