Category Archives: Windows Server 2008

Windows 7 / Windows Server 2008 R2 – Boot to VHD

Windows 7 and Windows Server 2008 R2 support booting from a VHD directly.  No host OS involved.  Very nice!  It kind of blows my mind a bit to think of the possibilities. 

How Does It Work?

It works like a dual boot machine, where you pick your OS option at startup.  Instead of having physical disk partitions, you can multi-boot onto a VHD instead of a disk partition.  You can boot directly to a VHD running SharePoint 2010 beta for example.   You can have as many of these as you need (and have disk space for).

For people limited to 4GB or RAM on a laptop, this can help SharePoint 2010 run much smoother because it has all the physical memory, no memory sharing with the host.  Your physical disk is available from the booted OS (VHD becomes C:, and physical disks looks like a D:, E:, etc.).  All physical hardware is available, just as if you installed the OS directly to a disk partition.

You can even get it to work with Vista as your main OS on your machine if you’re not ready to rebuild your machine with Windows 7 or Windows Server 2008 R2.  

What’s the Catch?

There are a few catches that I’m aware of: 

  • It only works if the VHD is stored on an internal disk 
  • The OS on the VHD must be Windows 7 or 2008 Server R2
  • Hibernation and bit-locker don’t work when booted from VHD’s.  Suspend does work on my Dell D830 after I installed the NVIDEA drivers for my video card. 
  • It works best with a fixed-size VHD, dynamic VHD disks will run slower
  • There is a slight performance hit, around 3%, when compared to a boot from a physical disk.  It’s negligilbe, I haven’t noticed a difference at all.
  • The vhd is not portable to other boxes due to hardware differences between machines.  You can sysprep and image and move it that way.

Great! Now How Do I Set It Up?

I won’t recreate a detailed walkthrough here, but the basic gist of it is this:

  1. Insert Windows 7 or Windows Server 2008 R2 media
  2. Boot from the CD like you’re installing the OS normally
  3. At the first screen, hit Shift-F10 to open a command window
  4. Use the DiskPart utility to create and mount the vhd.  Type DiskPart at the command prompt cnd enter the following commands:
    1. create vdisk file=C:\VHD-Windows7.vhd maximum=40960
    2. select vdisk file=C:\VHD-Windows7.vhd
    3. attach vdisk
    4. exit
  5. Close the command prompt and continue setup
  6. Select the Custom (Advanced) Install option
  7. Select the VHD disk you created for the install
  8. That’s it!  The Windows installer takes care of the rest.
  9. If you want more control, you can use BCDEdit or EasyBCD to edit the boot menu


If you need a more detailed walkthrough, the best one I’ve seen is here:

If you’re interested in booting a Windows 7 VHD from a system running Vista (I’m not!), you might find these helpful:



SharePoint 2010 Beta – ConfigurationErrorsException

If you’ve installed the SharePoint 2010 public beta, you’ve likely run into the WCF bug. This following errors occur when provisioning Service Applications or when accessing pages that make service calls.

System.Configuration.ConfigurationErrorsException: Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\<Service Area>\client.config line <Line Number>).

The service application proxy “User Profile Service Application” could not be provisioned because of the following error: Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\client.config line 56).

You may see this error in the ULS logs after installing SharePoint 2010, or displayed on the page as an error message when provisioning service applications or accessing SharePoint pages that make WCF service calls.

How To Fix It

This is a known WCF issue when installing SharePoint 2010 on Windows 7, Windows Server 2008, or Windows Server 2008 R2.  It’s, lovingly called the WCF Sharepoint Shared Services Roll-up issue. To fix it, install a WCF OS patch:

KB971831: WCF fix for Windows Server 2008 and Vista only

KB976462: WCF fix for Windows 2008 R2 and Windows 7 
Note:  This link is not activated yet, but you can download the WCF fix at

If you have already installed Microsoft SharePoint Server 2010 on a server running Microsoft Windows Server 2008 R2 or Microsoft Windows 7, Microsoft SharePoint Server 2010 does not need to be reinstalled. You can install the WCF fix afterward. However, Service Applications that have been provisioned without the update installed may need to be removed and re-provisioned once the update has been successfully applied.


SharePoint Team Blog: Installation Notice for the SharePoint Server Public Beta on Microsoft Windows Server 2008 R2 and Microsoft Windows 7

Jie Lie’s GeekWorld: SharePoint 2010 Pre-Requisites Download Links

SharePoint 2007 100% CPU Spike – Blue Screen 0x0000001d


SharePoint 2007 Web Front End (WFE) servers crashing repeatedly.  Environment is SharePoint 2007 (MOSS Enterprise) 64-bit running on Windows Server 2008 Standard.  Server was crashing repeatedly with CPU spiking to 100%, blue screen, and server rebooting itself.  System log showing BugCheck event (1000) entry with code 0x0000001d:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0xfffff9802ea0ef50, 0x0000000000000002, 0x0000000000000000, 0xfffffa6004e06ed9). A dump was saved in: C:\Windows\MEMORY.DMP.


After a lot of troubleshooting, it turns out it was Trend Micro Common Firewall Driver (Trend Micro OfficeScan Client 8.0).  When we disabled the firewall, problem resolved. it! digg it! reddit! technorati! yahoo!

Windows Server 2008 – Can’t Ping the Server

After installing Windows Server 2008, I found I can’t ping the server, even within a “Private Network”.  I like to ping stuff in my spare time, so this was distressing to me.  I suspected to find a firewall issue, but was surprised to find enabling the Network Discovery option in the firewall configuration settings didn’t fix it.

Configure Windows Firewall Settings – File and Printer Sharing

By default, Windows Firewall for WIndows Server 2008 is configured to disallow File and Printer Sharing on the network.  By default Windows Server 2008 firewall is configured with Windows Firewall running, and with File and Printer Sharing disabled.  This blocks ICMP Echo Request packets used by the PING command. You can allow the server to respond to ping requests by doing the following:

  1. Turn off Windows Firewall on the Windows 2008 Server (not recommended)- OR –
  2. Enable the File and Printer Sharing option in Windows Firewall Configuration Settings
    1. Start > Control Panel > Network and Intranet
    2. Under the Windows Firewall section heading, Click the Allow a program through Windows Firewall link
    3. In the programs and ports list, check the File and Printer Sharing option it! digg it! reddit! technorati! yahoo!

Virtual PC 2007 – Installing Vista / Windows Server 2008 Sound Drivers on VPC’s

When building Windows Vista and Windows Server 2008 VPC’s, I found it is sometimes difficult to get the correct device driver for the sound card installed.  After a few fruitless Google searches, I found lots of people with this problem and few solutions.  I finally found a blog post that gave me the help I needed.  Thanks to Greg Low Bit Bucket for his blog post, Greg Low’s Bit Bucket – Playing videos and sound in Windows Server 2008 using a Virtual PC (VPC).

First, as Greg said, if you’re using Virtual Server, you’re out of luck.  Virtual PC 2007 emulates a sound card, but Virtual Server doesn’t.  I’m not sure about Hyper-V.  If anyone has any findings on Hyper-V sound card emulation, please leave a comment and let us know what you found out.

Virtual PC 2007 Service Pack 1

The service pack has new sound emulator drivers for Vista and Windows Server 2008.  Be sure to install it and setup your VMC as a Windows Vista or Windows Server 2008 virtual machine.  As far as I can tell, the only difference between the operating systems you pick are the sound drivers and the memory allocation.  I normally tweak the memory allocation anyway.

Installing the Sound Drivers

To install the sound drivers, you need to install Virtual Machine Additions first, reboot, and then install the sound drivers from the C:\Program Files\Virtual Machine Additions folder on the VHD.

  1. Install Virtual Machine Additions (File > Install or Update Virtual Machine Additions).  This will mount a virtual drive and run a setup program to install the VM additions.
  2. After installing the software, reboot the VPC as directed
  3. If you get the Found New Hardware dialog, you can point it to the C:\Program Files\Virtual Machine Additions folder to install the drivers from there
  4. If you don’t get the Found New Hardware dialog (you disabled it because it was bugging you to death), you can install the device driver from the Device Manager
    1. Open the Device Manager (Start > Control Panel > Device Manager)
    2. Under the Other devices, you’ll see a yellow icon indicating you have a problem with the Multimedia Audio Controller
    3. Right-click the Multimedia Audio Controller and select the Update Device Driver option
    4. Select the option to “Browse my computer” and point it to the C:\Program Files\Virtual Machine Additions folder
    5. Click Next to install the device drivers
  5. After the device driver setup is complete, your sound should start working, and you’ll no longer have an annoying device driver warning when you startup your VPC

Installing Windows Media Player on Windows Server 2008

Windows Server 2008 does not have Windows Media player installed by default.  If you want to get streaming media audio running, you’ll need to install it.  To install the Media Player, you need to install the “Desktop Experience” feature.

The Desktop Experience feature enables a bunch of stuff that is by default present on a Vista workstation, but is not included by default on a Server 2008 installation.desktop OS.  Most importantly it includes Windows Media player, Themes, and the Aero related features.

  1. Open Server Manager (Start > Administrative Tools > Server Manager)
  2. Select Features > Add Features
  3. Check the Desktop Experience feature and click Next
  4. Click Install to install the feature
  5. Reboot as directed
  6. When the machine comes back up, WIndows Media Player will be there

After installing the Desktop Experience on Windows Server 2008, Windows Media Player will be available.  Themes and Aero will be installed but disabled, but I don’t need them bogging down my VPC anyway.


Greg Low’s Bit Bucket – Playing videos and sound in Windows Server 2008 using a Virtual PC (VPC) it!

digg it!