Installing WebDAV on IIS 7.0

Installing WebDAV on IIS 7.0

Prerequisites

The following items are required to complete the procedures in this article:

• IIS 7.0 must be installed on your server, and the following must be configured:
  • The Default Web Site that is created by the IIS 7.0 installation must still exist.
  • The Internet Information Services Manager must be installed.
  • At least one authentication method must be installed.

Note: If you choose to use Basic Authentication with the WebDAV redirector, you must connect to your server using HTTPS.

• The WebDAV Redirector must be installed:
  • You must use Server Manager to install the Desktop Experience feature before you can use the WebDAV redirector.

Downloading the Right Version for Your Server

There are two separate downloadable packages for the new WebDAV extension module; you need to download the appropriate package for your version of Windows Server 2008:

• 32-bit Installation Package:
  • WebDAV 7.5 for IIS 7.0 (x86)
• 64-bit Installation Package:
  • WebDAV 7.5 for IIS 7.0 (x64)

Launching the Installation Package

You must run the installation package as an administrator. This can be accomplished by one of the following methods:

• Logging in to your server using the actual account named "Administrator", then browsing to the download pages listed above or double-clicking the download package if you have saved it to your server.
• Logging on using an account with administrator privileges and opening a command-prompt by right-clicking the Command Prompt menu item that is located in the Accessories menu for Windows programs and selecting "Run as administrator", then typing the appropriate command listed below for your version of Windows to run the installation:
  • 32-bit Windows Versions:
    • msiexec /i webdav_x86_75.msi
  • 64-bit Windows Versions:
    • msiexec /i webdav_x64_75.msi

Walking Through the Installation Process

1. When the installation package opens, you see the following screen. If you agree to the license terms, check the "I accept" box, then click Install.
   
2. The progress indicator will reflect the status of the installation as it proceeds.
   
3. After the installation has completed, click Finish.
   
4. The WebDAV extension module is now installed.

Installing WebDAV on IIS 7.5

IIS 7.5 for Windows Server 2008 R2

1. On the taskbar, click Start, point to Administrative Tools, and then click Server Manager.
2. In the Server Manager hierarchy pane, expand Roles, and then click Web Server (IIS).
3. In the Web Server (IIS) pane, scroll to the Role Services section, and then click Add Role Services.
4. On the Select Role Services page of the Add Role Services Wizard, expand Common HTTP Features, select WebDAV Publishing, and then click Next.
5. On the Confirm Installation Selections page, click Install.
6. On the Results page, click Close.

IIS 7.5 for Windows 7

1. On the taskbar, click Start, and then click Control Panel.
2. In Control Panel, click Programs and Features, and then click Turn Windows Features on or off.
3. Expand Internet Information Services, then World Wide Web Services, then Common HTTP Features.
4. Select WebDAV Publishing, and then click OK.

Enabling WebDAV Publishing by Using IIS Manager

The new WebDAV extension module makes it easy to add WebDAV publishing to existing sites by providing you with a wizard that walks you through all of the required steps.

Step 1: Enabling WebDAV and Adding an Authoring Rule

In this first step, we add WebDAV publishing to the Default Web site, and add the required settings to allow the local administrator account to edit the content.

1. In IIS Manager, in the Connections pane, expand the Sites node in the tree, then click the Default Web Site.
2. As shown in the image below, double-click the WebDAV Authoring Rules feature.
   
3. When the WebDAV Authoring Rules page is displayed, click the Enable WebDAV task in the Actions page.
   
4. Once WebDAV has been enabled, click the Add Authoring Rule task in the Actions pane.
   
5. When the Add Authoring Rule dialog appears:
   1. Click All content to specify that the rule applies to all content types.
   2. Choose "Specified users" and type "administrator" for the user name.
   3. Select Read, Source, and Write for the permissions.
   4. When you have completed these items, click OK.
      

Summary
Task completed. You have enabled WebDAV authoring on an existing Web site.
To recap the items that you completed in this step, we added WebDAV publishing to the "Default Web Site" by:

• Enabling WebDAV for the Web site.
• Adding an Authoring Rule for the local administrator account for Read, Source, and Write access.

Note: As mentioned earlier, your default request filtering settings may block several file types from WebDAV authoring. If you do not modify your request filtering settings, you may see various errors when you try to publish files that are blocked. For example, if you attempt to upload or download a web.config file you will see errors in your WebDAV client. For more information about configuring your request filtering settings, see the How to Configure WebDAV with Request Filtering walkthrough.

Step 2: Logging in to Your WebDAV Site

In Step 1 above, you enabled WebDAV publishing for your Default Web Site and added an Authoring Rule for the local administrator account for Read, Source, and Write access to your Web site's content. In this step, you log in using your administrator account.
Ensuring that you have Authorization and Authentication configured

1. In IIS Manager, in the Connections pane, expand the Sites node in the tree, then click the Default Web Site.
2. Double-click the Authentication feature.
   
3. When the Authentication feature opens, make sure that Windows Authentication is enabled. (Note: You can use Basic Authentication with WebDAV, but the WebDAV redirector will only use Basic authentication with SSL connections.)
   
4. In IIS Manager, click the Default Web Site under the Sites node in the tree.
5. Double-click the Authorization feature.
   
6. When the Authorization feature opens, make sure that an Allow rule is defined that includes the administrator account. (For example, the default rule for IIS allowing access to All Users will include the administrator account.)
   

Logging in to your WebDAV site using your administrator account

1. On your WebDAV server, open a command prompt session.
2. Type the following command to connect to your WebDAV server:
   
   net use * http://localhost/

TEN Windows 7 commands...... Every administrator should know....!

1: System File Checker

Malicious software will often attempt to replace core system files with modified versions in an effort to take control of the system. The System File Checker can be used to verify the integrity of the Windows system files. If any of the files are found to be missing or corrupt, they will be replaced. You can run the System File Checker by using this command:

sfc /scannow

2: File Signature Verification

One way to verify the integrity of a system is to make sure that all the system files are digitally signed. You can accomplish this with the File Signature Verification tool. This tool is launched from the command line but uses a GUI interface. It will tell you which system files are signed and which aren’t. As a rule, all the system files should be digitally signed, although some hardware vendors don’t sign driver files. The command used to launch the File Signature Verification tool is:

sigverif

3: Driverquery

Incorrect device drivers can lead to any number of system problems. If you want to see which drivers are installed on a Windows 7 system, you can do so by running the driverquery tool. This simple command-line tool provides information about each driver that is being used. The command is:

driverquery

If you need a bit more information, you can append the -v switch. Another option is to append the -si switch, which causes the tool to display signature information for the drivers. Here’s how they look:

driverquery -v

driverquery -si

4: Nslookup

The nslookup tool can help you to verify that DNS name resolution is working correctly. When you run nslookup against a host name, the tool will show you how the name was resolved, as well as which DNS server was used during the lookup. This tool can be extremely helpful when troubleshooting problems related to legacy DNS records that still exist but that are no longer correct.
To use this tool, just enter the nslookup command, followed by the name of the host you want to resolve. For example:

nslookup dc1.Appliedis.com

5: Ping

Ping is probably the simplest of all diagnostic commands. It’s used to verify basic TCP/IP connectivity to a network host. To use it, simply enter the command, followed by the name or IP address of the host you want to test. For example:

ping 192.168.1.1

Keep in mind that this command will work only if Internet Control Message Protocol (ICMP) traffic is allowed to pass between the two machines. If at any point a firewall is blocking ICMP traffic, the ping will fail.

6: Pathping

Ping does a good job of telling you whether two machines can communicate with one another over TCP/IP, but if a ping does fail, you won’t receive any information regarding the nature of the failure. This is where the pathping utility comes in.
Pathping is designed for environments in which one or more routers exist between hosts. It sends a series of packets to each router that’s in the path to the destination host in an effort to determine whether the router is performing slowly or dropping packets. At its simplest, the syntax for pathping is identical to that of the ping command (although there are some optional switches you can use). The command looks like this:

pathping 192.168.1.1

7: Ipconfig

The ipconfig command is used to view or modify a computer’s IP addresses. For example, if you wanted to view a Windows 7 system’s full IP configuration, you could use the following command:

ipconfig /all

Assuming that the system has acquired its IP address from a DHCP server, you can use the ipconfig command to release and then renew the IP address. Doing so involves using the following commands:

ipconfig /release

ipconfig /renew

Another handy thing you can do with ipconfig is flush the DNS resolver cache. This can be helpful when a system is resolving DNS addresses incorrectly. You can flush the DNS cache by using this command:

ipconfig /flushdns

8: Repair-bde

If a drive that is encrypted with BitLocker has problems, you can sometimes recover the data using a utility called repair-bde. To use this command, you will need a destination drive to which the recovered data can be written, as well as your BitLocker recovery key or recovery password. The basic syntax for this command is:

repair-bde <source> <destination> -rk | rp <source>

You must specify the source drive, the destination drive, and either the rk (recovery key) or the rp (recovery password) switch, along with the path to the recovery key or the recovery password. Here are two examples of how to use this utility:

repair-bde c: d: -rk e:\recovery.bek

repair-bde c: d: -rp 111111-111111-111111-111111-111111-111111

9: Tasklist

The tasklist command is designed to provide information about the tasks that are running on a Windows 7 system. At its most basic, you can enter the following command:

tasklist

The tasklist command has numerous optional switches, but there are a couple I want to mention. One is the -m switch, which causes tasklist to display all the DLL modules associated with a task. The other is the -svc switch, which lists the services that support each task. Here’s how they look:

tasklist -m

tasklist -svc

10: Taskkill

The taskkill command terminates a task, either by name (which is referred to as the image name) or by process ID. The syntax for this command is simple. You must follow the taskkill command with -pid (process ID) or -im (image name) and the name or process ID of the task that you want to terminate. Here are two examples of how this command works:

taskkill -pid 4104

taskkill -im iexplore.exe

Disable Search In Windows 7

Windows 7 Search
Some users might not be happy with the Search feature in Windows 7 and would rather use a third party utility like Everything instead. If so, you may want to get rid of the search feature to free up some real estate in Explorer and the Start Menu.

Disable Windows Search
If you want to disable Windows Search, click on Start and select Control Panel.
 
In Control Panel switch to Large Icons View and click on Programs and Features. or use Appwiz.cpl command from run.

Next in the left panel click on the Turn Windows features on or off hyperlink.

Scroll down the list and uncheck the box next to Windows Search.

Click yes to the message asking if you’re sure you want to continue.

Now click Ok in the Windows Features window.

A progress message comes up while the changes take place.

Then a restart is required to complete the changes.

When you get back from the reboot you’ll no longer see the Search box in the Start Menu.

The search box in Windows Explorer will also no longer show.

If you want to turn it back on again, go back into the Turn Windows Features on or off section and re-enable Windows Search. Personally I would think most people would be happy with the search feature in Windows 7, but if you’re not, this is how to disable it. Hopefully this comes in handy for somebody.

SharePoint Server 2010 Installation

“You have configured this virtual machine as a 64-bit guest operating system…”

By default, Lenovo T61 laptop’s ship with virtualization technology and set VT is disabled.
In order to enable VT on laptop, please shut down your laptop and go to BIOS setup > CPU > Virtualization technology > Enable and Press F10 to Save and Exit.
Install Windows server 2008 with SP 2.

Download prerequisites software (if you need to share your PC folder to access from VMWARE) enable Share folder option:

Go to VM > Setting > Options > Shared Folder > Enable and Select your Pre-request software download folder.

Run > SharePoint Server 2010 Application file, system will extract files and show the above screen, under Install > click Install Software prerequisites…


System will run for few minutes and display the following error message:

Install your prerequisites software that you downloaded one by one.


Once you get the above screen “Installation Complete”, click "Install SharePoint Server” link:

SharePoint 2010 Installation screen prompts for Product Key get beta key from here. 

Read your License terms and click I accept and start Installation:

Select Standalone option, if you are installing with SQL Express 2008 server. If you are installing SQL Server 2008 and SharePoint 2010 farm servers, then select Server Farm option. Since I am using VMWARE installation, I select Standalone option.

System will start the Installation progress…

System would take several minutes to complete installation and prompt for Configuration Wizard.

Run your Configuration wizard and click next >

Step 2 on Configuration wizard click “Yes” to start IIS and SharePoint Admin, Timer service.

Configuration wizard continue 2 of 10 tasks and if everything is ok, the system will display the following screen.
(
Congratulations… you successfully Installed SharePoint 2010.
System will launch SharePoint 2010 Central Administration screen…

How To Configure Remote Desktop To Hyper-V Guest Virtual Machines

Configuring Remote Desktop (RDP) from a host Hyper-V machine to a guest virtual machine can be tricky, so this post is dedicated to the issues and resolution steps I went through to allow RDP.  Cutting to the point, below are the things to look for followed by some explanation about my scenario if you care to read.  This is not an exhaustive list of what is required, just the items that were causing problems for my particular scenario.

Requirements

1. Allow Remote Desktop Connections in guest OS.
2. The network adapter type must allow communication with host machine (e.g. use an “Internal” or “External” virtual adapter.)
3. If running Server 2008 R2 on guest, network discovery mode must be turned on.
4. If running Server 2008 R2 on guest, the services supporting network discovery mode must be running: - DNS Client
   - Function Discovery Resource Publication
   - SSDP Discovery
   - UPnP Device Host
   

My Environment

    A quick word about my environment.  I am running Windows Server 2008 R2 with Hyper V on my laptop and numerous guest VMs running Windows Server 2003 R2 or Windows Server 2008 R2.  I run a domain controller VM and then 1 or 2 SharePoint servers depending on my work needs.  I’ve found this setup to work well except when it comes to the display window for my VMs.

Allow RDP Connection

    This item I had previously taken care of, but it bears repeating because by default Windows Server 2008 R2 does not allow RDP connections.  Change the setting from “Don’t allow…” to whichever “Allow connections…” setting suits your needs.  I chose the less secure option as this is just my dev laptop.

Network Adapter Type

    When I originally configured my VMs I configured each to use 2 network adapters: one using the physical ethernet adapter for internet use and a virtual private adapter for communication between the VMs.  The connection for the ethernet adapter is an "”External” adapter and (as my co-worker Kelly Jones pointed out in comments below) does allow connections between host and guest.  After he pointed this out though I realized that my ethernet adapter is not always reliably enabled (power cord not in disables NIC.)  As such I need a secondary adapter that will always be on to connect the host and guest.  The virtual private adapter I had allowed communication ONLY between the VMs and not to my host.  There is a third option “Internal” which allows communication between VMs as well as to the host.  After finding out this distinction I promptly created an Internal network adapter and assigned that to my VMs.

Turn On Network Discovery

    Seems like a pretty common sense thing, but in order to allow remote desktop connections the target computer must able to be found by the source computer . One of the settings that controls if a computer can be found on the network is aptly named Network Discovery.  By default Windows Server 2008 R2 turns Network Discovery off for security purposes.  To enable it open up the Network and Sharing Center.  Click “Change Advanced Sharing Settings” on the left.  On the following screen select “Turn on network discovery” for the currently used profile and click Save Settings.  You may notice though that your selection to turn on network discovery doesn’t save.  If this is the case then you most likely don’t have the supporting services running (as was my case.)

Network Discovery Supporting Services

    There are a total of 4 services (listed again below) that need to be running before you can turn on network discovery . The below images highlight these services.  In my guest VM I found that I had DNS Client already running while the other 3 were disabled.  I set them all to enabled and started the ones that were stopped.  After this change I returned to the Sharing settings screen and found that Network Discovery was turned on.  I’m not sure whether this was picking up my attempt to turn it on previously or if starting those services turned it on.  Either way the end result was a success.
- DNS Client
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host

Before and After Results

    The first image is the smaller square shaped viewing window used by the Hyper-V native connection.  The second is the full-screen RDP connection in all its widescreen glory.