Some Important steps to configure the Windows Server 2008 R2

Install Internet Information Services (IIS) on Windows Server 2008 and Windows Server 2008 R2 Computers

Use the following procedure that applies to Windows Server 2008 and Windows Server 2008 R2:

1. On the Windows Server computer, navigate to Start / All Programs / Administrative Tools / Server Manager to start Server Manager. In Server Manager, select theFeatures node, and then click Add Features to start the Add Features Wizard.
2. On the Select Features page of the Add Features Wizard:
   
   
   • For Windows Server 2008, select the BITS Server Extensions check box. For Windows Server 2008 R2, select the Background Intelligent Transfer Services (BITS)check box. When prompted, click Add Required Role Services to add the dependent components, including the Web Server (IIS) role.
   • Select the Remote Differential Compression check box, and then click Next.
3. On the Web Server (IIS) page of the Add Features Wizard, click Next.
4. On the Select Role Services page of the Add Features Wizard:
   
   
   • Windows Server 2008 R2 only: For Common HTTP Features, select the WebDAV Publishing check box.
   • For Application Development, select the ASP.NET check box and, when prompted, click Add Required Role Services to add the dependent components.
     
     
   • For Security, select the Windows Authentication check box.
   • In the Management Tools node, for IIS 6 Management Compatibility, ensure that both the IIS 6 Metabase Compatibility and IIS 6 WMI Compatibility check boxes are selected, and then click Next.
5. On the Confirmation page, click Install, and then complete the rest of the wizard.
6. Click Close to exit the Add Features Wizard, and then close Server Manager.

Install WebDAV for IIS 7.0

You must install WebDAV manually on Windows Server 2008 computers with IIS 7.0. The following procedure applies to Windows Server 2008 with IIS 7.0 installed:

1. Depending on your server operating system architecture, download either the x86 or x64 version.
2. Depending on the version you downloaded, run either the webdav_x86_rtw.msi or the webdav_x64_rtw.msi file to install WebDAV IIS 7.0 extensions.

Enable WebDAV and create an Authoring Rule

Use the following procedure to enable WebDAV and create an Authoring Rule for Windows Server 2008 and Windows Server 2008 R2:

1. Navigate to Start / All Programs / Administrative Tools / Internet Information Services (IIS) Manager to start Internet Information Services 7 Application Server Manager.
2. In the Connections pane, expand the Sites node, and then click Default Web Site if you are using the default Web site for the site system or SMSWEB if you are using a custom Web site for the site system.
3. In the Features View, double-click WebDAV Authoring Rules.
4. With the WebDAV Authoring Rules page displayed, in the Actions pane, click Enable WebDAV.
5. In the Actions pane, click Add Authoring Rule.
6. In the Add Authoring Rule dialog box, for Allow access to, select All content.
7. For Allow access to this content to, select All users.
8. For Permissions, select Read, and then click OK.

Use the following procedure to change the property behavior of WebDAV on Windows Server 2008 and Windows Server 2008 R2:

1. In the WebDAV Authoring Rules page, in the Actions pane, click WebDAV Settings.
2. In the WebDAV Settings page, for Property Behavior, set Allow anonymous property queries to True.
3. Set Allow Custom Properties to False.
4. Set Allow property queries with infinite depth to True.
5. For a distribution point that is enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS, for WebDAV Behavior, setAllow hidden files to be listed to True.
6. In the Action pane, click Apply.
7. Close Internet Information Services (IIS) Manager.

Configure requestFiltering for IIS on distribution points

The following information applies when you use distribution points that are enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS.

By default, IIS blocks several file extensions and folder locations. If package source files contain extensions that are blocked in IIS, you must configure the requestFiltering section in the applicationHost.config file on a distribution points that is enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS.

For example, you might have source files for a software deployment that include a folder named bin, or that contain a file with the .mdb file extension. By default, IIS request filtering blocks access to these elements. When you use the default IIS configuration on a distribution point, clients that use BITS fail to download this software deployment from the distribution point. In this scenario, the clients indicate that they are waiting for content. To enable the clients to download this content by using BITS, on each applicable distribution point, edit the requestFiltering section of the applicationHost.config file to allow access to the files and folders in the software deployment.

Use the following procedure to modify requestFiltering for Windows Server 2008 and Windows Server 2008 R2.

1. Open the applicationHost.config file located in the %Windir%\System32\Inetsrv\Config\ directory on distribution points that are enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS.
2. Search for the <requestFiltering> section.
3. Determine the file name extensions and folder names that you will have in the packages on that distribution point. For each extension and folder name that you require, perform the following steps:
   
   
   • If it is listed as a fileExtension element, set the value for allowed to true.
     
     For example, if your package contains a file with an .mdb extension, change the line true to allowed<add fileExtension=".mdb" allowed="false" /> to <add fileExtension=".mdb" allowed="true" />.
     
     Allow only the file name extensions required for your packages.
   • If it is listed as a <hiddenSegments> element, delete the entry that matches the file name extension or folder name from the file.
     
     For example, if your package contains a folder with the label of bin, remove the line <add segment=”bin” /> from the file.
4. Save and close the applicationHost.config file.