[anthonymking]

I’ll refer you to this other Bluetooth thread as it is more appropriate than this one I started;

viewtopic.php?f=25&t=929

I followed the instructions from the AsciiWolf’s post on Sun Oct 18, 2009 3:11 pm. They include a link to instructions on another forum;

http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2networking/thread/1ea7b245-684e-4fd0-8784-44fa08ce3ebd

These instructions result in a complete functional bluetooth stack with the proper control panel (they do require driver signature enforcement off). I can now use bluetooth networking and all of the other features of the built in microsoft stack.

Unfortunately, the built in stack does not include bluetooth stereo audio. On Windows 7, I can get this by installing the latest WIDCOMM drivers. The WIDCOMM installer will not run on Server 2008 R2. I have not taken the time to figure out how it determines the OS.

I believe the WIDCOMM installation sits on top of the Microsoft stack. So, I am fairly confident that everything would work as desired if I could trick the WIDCOMM installer into running on my Server 2008 R2 box now that I have the Microsoft stack working completely.

[anthonymking]

For that laptop, it depends on the processor installed and bios version. The Hyper-V role won’t even install if you don’t have hardware virtualization.

[anthonymking]

For that laptop, it depends on the processor installed and bios version. The Hyper-V role won’t even install if you don’t have hardware virtualization.

[anthonymking]

Unfortunately, it is a known issue. Please see;

http://support.microsoft.com/kb/961661

If you are like me, and you use Hyper-V and business applications during the day, and do games and graphics at night, then you can turn Hyper-V on and off. On the other hand, if your workflow is mixed, you will need a different virtualization solution.

When I stop working (around 6PM), I run a batch file that applies the following registery change and shuts down the computer;

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetserviceshvboot]
“Start”=dword:00000003

When I stop non-work (around 11PM), I run a batch file that applies the following registry change and shuts down the computer;

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetserviceshvboot]
“Start”=dword:00000001

Also, make sure you have the latest NVIDIA driver (I am using 190.38). The latest drivers have reduced the usage of the offending feature (and thus improved the performance somewhat). For getting the latest drivers running on your mobile GPU, I strongly recommend;

http://www.laptopvideo2go.com/

[anthonymking]

Unfortunately, it is a known issue. Please see;

http://support.microsoft.com/kb/961661

If you are like me, and you use Hyper-V and business applications during the day, and do games and graphics at night, then you can turn Hyper-V on and off. On the other hand, if your workflow is mixed, you will need a different virtualization solution.

When I stop working (around 6PM), I run a batch file that applies the following registery change and shuts down the computer;

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetserviceshvboot]
“Start”=dword:00000003

When I stop non-work (around 11PM), I run a batch file that applies the following registry change and shuts down the computer;

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetserviceshvboot]
“Start”=dword:00000001

Also, make sure you have the latest NVIDIA driver (I am using 190.38). The latest drivers have reduced the usage of the offending feature (and thus improved the performance somewhat). For getting the latest drivers running on your mobile GPU, I strongly recommend;

http://www.laptopvideo2go.com/

[anthonymking]

Sure.

FYI; What I did was intall Windows 7 on my laptop. Then I went through several cycles of updating (using Windows Update) until every device was working. My bluetooth device was the only device that required a third party driver. The Windows device installer pointed me to this vendor link;

http://www.broadcom.com/support/bluetooth/update.php

After installing the above, everything in the laptop worked under Windows 7. Then, I searched %SYSTEMROOT%System32DriverStoreFileRepository for every client-only driver (by looking for INF files containing NTamd64…1). I copied all of these drivers (24 in all) to a removable hard drive, and edited all the INF files to NTamd64…3.

Then, I installed Windows Server 2008 R2. I let Windows install drivers for everything that it could find automatically. For the remaining devices, I installed them by manually updating and browsing to the modified files I saved from Windows 7. This worked perfectly for several devices (SD memory card reader, modem, tethered cell phone). This also appeared to work for bluetooth (in that the device drivers installed and started). However, I am missing the bluetooth control panel. Thus, I have no way to actually manage bluetooth connections.

You can find my modified drivers here;

http://cid-9698f03ad765e594.skydrive.live.com/self.aspx/.Public/FileRepository.zip

[anthonymking]

I can confirm that it works on Windows 2008 R2 RTM.

[Author]

Posts