...
More details for getting set up with WebDAV in Windows network places are available here.
General directions for Windows and Macintosh are available here.
If you prefer, there are also several excellent third-party applications available for WebDAV connections, particularly for Macintosh, including Cyberduck, Transmit, Coda, Goliath, and more. For Windows support at the moment is primarily limited to the Network Places folders provided within the operating systemthe alternative to Network Folders is BitKinex.
Permits and Access Control
...
By default, your LAMP account will come with a permit of the form cit.lamp.*.. or an Active Directory "permit" group in the form on cit-lamp-. The initial membership of this permit will be the primary contact, the secondary contact, and all additional authorized users listed on the signup form. Additionally, the primary and secondary contacts for the instance will also have the update privilege to update membership to the permit via the permit interface ActiveRoles Server interface at https://admgmt.activedirectory.cornell.edu/permits/default.aspx (Internet Explorer required). Instructions for using the interface can be found at http://paw1www.cit.cornell.edu/cgi-bin/permit.cgi/services/active_directory/howto/videos/manage_legacy_permits/index.cfm
DAV Access Control
Access to the key generation page of DAVPortal is restricted to valid-user. Access to the DAV share itself by default is restricted to the permit created with your LAMP instance. This is to allow the use of the require netid directive in combination with DAVPortal. Though anyone with a NetID can receive a DAVPortal key for your instance, by default, only those in the permit will be able to actually access the share. The rest of the configuration is up to you - please feel free to adjust it to your needs through the use of .wdaccess files (see "Opening and Restricting Access", below).
...
A note about Content Management/Blogging Systems (WordPress, etc.)
Before installing Wordpress in the LAMP hosting environment, please chect out the Cornell University Blog service at http://blogs.cornell.edu/
Several content management systems have internal configuration that specifies what the software thinks the URL/hostname of the site is. If you have setup the CMS using the pre-production URL but intend to have a custom URL point to it later, you will need to change the configuration later.
...