So, let’s put aside for a moment that what the Chocolatey guys are having you do is, technically, a horrible security practice. Your’e downloading code, from the Internet, from people you don’t even know, and executing it under admin credentials. That script isn’t digitally signed, so you’ve no idea if it’s what they intended you to download, or if they’ve been hacked and their script altered. Terrible, terrible practice.
But let’s put that aside.
As a note for future posts, if you’re getting errors, it’d be super-helpful if you included them in your message. They often contain a lot of valuable information, so without them, everyone here is really just guessing, which isn’t as helpful to you.
But let’s focus on this: What is it you are trying to do?
You want IIS to execute PS1 files server-side, as a web page? Not a great idea - I can explain why, if that’s what you’re after.
You want IIS to host PS1 files, and you want your computers to download & execute those scripts? From IIS? I probably don’t understand why. There’s probably a hundred better ways to get computers to run PowerShell scripts without dragging IIS into it.
Or maybe I’m not understanding what you want to accomplish?
[blockquote]I suspect it has something to do with my IIS setup as, if I go to ‘https://chocolatey.org/install.ps1’ IE shows it as a text file (in the browser). if I go to my URL, I am prompted to download the fire.[/blockquote]
The above is probably because of additional HTTP headers that their server is sending. Your server is using the default behavior. PS1 files aren’t supposed to be executable file types under Windows. There’s a set of very good security reasons why Microsoft set that as the default. If we’re going to have a discussion about turning that off, and allowing execution of arbitrary code downloaded from a web server, I just want to make sure you’re aware of the potential Bad Things. If there’s a better way to accomplish what you’re trying to do, I’d like to help you identify that, if I can.