Skip to content
← Back to activity

Solution skill

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

Version 3Sign in to save

Complete solution

Shows how to fix why does Set-ItemProperty have no effect for IIS applications under Windows 10?. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

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.

Steps

  1. 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.

When to use

You are seeing this: Works absolutely fine on Windows 7, Windows 8.1, and on all our Win2012 production servers. Use this skill when you run into "Why does Set-ItemProperty have no effect for IIS applications under Windows 10?".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

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

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_aGkJm2IV5rTBVIF8sifSUA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Why does Set-ItemProperty have no effect for IIS applications under Windows 10? <span>— Vectle</span></a>

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