The only way to correctly install modules is by way of module install packages, This is because modules need to be registered correctly in the database etc. for you to use them.

The preferred way of running in a webfarm is using a fileshare, so all servers run the application from the same location. All uploaded files will then always be available to all servers immediately. If you need more information about how to set up a web farm, you can download the webfarm configuration guide through here: http://www.dnnsoftware.com/about/reso...

Mind you: only DNN Evoq Content has full support for web farms.

---

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn:

install skins/modules via zip files is the appropriate way to do this, as the zip file will also contain a .dnn manifest file. This allows DNN to perform any necessary registration and installation actions, and allows for clean uninstalls (it also supports shared components, registering dependencies, creating custom permissions etc. - the manifest is very powerful).That said, you don't have to upload a file to install it, you can place it within the install folder structure and have it install as part of your custom install (e.g. place your zip files in install/modules or install/skins and they will install as part of the installation - this is how people make custom builds). Alternatively you can drop the files in and use install.aspx?mode=InstallResources to force install of any zip file within the install folders (see http://www.dnnsoftware.com/wiki/page/... ). As for load balanced servers, DNN does not do anything for that - you're in charge of how your load balanced environment is setup - the most common approaches are a single UNC folder which all webheads point to, or using file/folder synchronisation (e.g. DFS or Robocopy) to keep the webhead's content matching.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US