by Graffen
12. March 2009 10:04
At work I’ve spent the past couple of days getting our production environment ready for a new product. The servers are a series of old HP blades with an Alteon load balancer facing the world. I wanted to be able to publish the application to one place and have all the servers serve it from there. So I got the IT department to supply me with a network share and I started setting up the IIS servers.
I quickly stumbled upon a problem: ASP.NET requires certain security settings to be allowed to execute code located on a network share. After googling around a bit, I found the solution to be quite simple. On each server, simply run the following in a command prompt:
c:\windows\microsoft.net\Framework\v2.0.50727\CasPol.exe -m -ag 1 -url "file:////\\servername\share\*" FullTrust -exclusive on
Remember to replace servername and share with your own settings.
UPDATE: Okay so this wasn’t the greatest idea. Like Mr. Viehweg noted in his comment, I hit file-locking issues almost right away. Looking into Distributed File System now.
ea5851f9-73ff-4738-9d9e-d7c83c977cd9|1|5.0
Tags: