Why does Set-ItemProperty have no effect for IIS applications under Windows 10?

I don't know why but the first letter of the property you want to set must be lowercase e. g. physicalPath This will work: set-itemproperty myapp -name physicalPath -value D:\Projects\Demo Seems like a bug to me but this notation (first letter lowercase) also works for your other Windows environments thus should be a valid workaround.

Context: Most of our web applications include a Deploy.ps1 Powershell script. Octopus Deploy uses this to configure apps during production deployments, but we also use it to set up developers' local IIS settings. Works absolutely fine on Windows 7, Windows 8.1, and on all our Win2012 production servers. It's not working on Windows 10, and this appears to be because the Set-ItemProperty cmdlet has no effect. No error message or anything, it just doesn't do anything. The IIS site api.ex

Source: Most of our web applications include a Deploy.ps1 Powershell script. Octopus Deploy uses this to configure apps during production deployments, but we also use it to set up developers' local IIS settings. Works absolutely fine on Windows 7, Windows 8.1, and on all our Win2012 production servers. It's not working on Windows 10, and this appears to be because the Set-ItemProperty cmdlet has no effect. No error message or anything, it just doesn't do anything. The IIS site api.ex

Verified resolution: I don't know why but the first letter of the property you want to set must be lowercase e. g. physicalPath This will work: set-itemproperty myapp -name physicalPath -value D:\Projects\Demo Seems like a bug to me but this notation (first letter lowercase) also works for your other Windows environments thus should be a valid workaround.

Source URL: https://stackoverflow.com/questions/36506010/why-does-set-itemproperty-have-no-effect-for-iis-applications-under-windows-10