Archive for July, 2008

The error 0x80072f0d is received when sending/receiving from outlook 2007 connected to exchange 2007

July 10, 2008

If you have a self signed certificate on your server, continue reading:)

The problem is that the certificate is not installed on the client; navigate to https://your-server and install the certificate.

To make this work, your OAB URL should use a secure connection to your exchange server. To see this, hold ctrl down and right click on the outlook icon next to the watch (on a client). Press test connection, and fill in your password. Look for OAB URL and ensure that it starts with https. If not, go to your exchange server, Exchange Management Console, Server Configuration, Client Access, Offline Address Book Distribution, Right click on OAB, select properties, URLs; replace http with https, so it looks like

Wait until the setting is replicated to the outlook clients (restart outlook), and run the test tool again. Now everything should be running.

NB: If you have a Vista client, you have to run internet explorer as administrator to install the certificate. Do this by starting a terminal and type “runas /user:administrator iexplorer”. When installing the certificate, you have to choose the “Place all certificates in the following store”, and then “Trusted Root Certification Authorities”. Good luck…


Making Hyper-V working on HP Proliant ml350 on Server 2008 x64

July 9, 2008

Making this work have taken a couple of days, because different BSODs have appered randomly. I have been talking with HP support, and browsed almost the complete Internet for a solution. Now what I found out…

First, I installed Server 2008 from the DVD without the smartstart CD. This might be wrong, as some of the problems (as far as I know) could be avoided using the CD.

When the server was first installed (2 months ago), Hyper-V where in beta, it was later updated to a RC, and the final version can now be downloaded from:
When upgrading to RC/final, hell began…

To make everything work, make shure that you remove the old Hyper-V role before this final version is installed (did not do that: many things went wrong). When removing the role, the server might not shut down, wait, wait more, then give up and shut it down the hard way.

Start up, the removal might go wrong by saying installing updates stage 3 ??%, if you cannot boot, try again. If still no luck, start in fail safe mode, then reboot.

Install the updated version and reboot, this might go wrong as well (for me it stopped at stage 3, 71%), reboot, try again…


Now, if you get some strange errors like that the server gets a STOP 0x000000F4, try to install the newest Broadcom Netxtreme II for BCM5708C from IBM:
It will install the newest driver available.


Some other strange things happend like I where unable to copy big files (10gb approx) from one place to another on the same disk; it resulted in the same type of blue screen. This issue was resolved by installing the Proliant Support Pack:

UPDATE: If you get some strange encryption errors when remotely connecting to your guest OS, then disable “IPv4 Large Send Offload” for the broadcom nic in the advanced tab in device manager; more info:

If the virtual machines looses network connection and have problems stopping, try to set “IPv4 Checksum Offload” to None.

Now, Hyper-V runs smoothly:)
Leave a comment if you have questions, it took me long to find this out:)