Exchange 2007 Outlook anywhere RPC endpoint 6004 error


I was attempting to get outlook anywhere to work. My environment is Exchange 2007 SP3 with the latest rollup package (as of 2/27/13) running on W2K8R2. I am using a UCC certificate from godaddy with my external name “” and my Subject Alternative Names are;; etc…

This is a small environment so every exchange role is installed on the same server.
The error pops up when I run the RPC over HTTP test at

and get an error on the following test:

Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server.

I checked a few things on this:
1. I made sure that the “valid ports” registry key in HKLM/Software/Microsoft/RPC/RpcProxy had the following:


2.I added my internal server name to my DNS hosts (I’m not sure if this made a difference) I’m going to remove it and test at a later time.

3. Following someone’s advice (and what I really think solved the problem) was that I edited the hosts file on the exchange server and put in 2 entries ( is my internal ip address for my exchange server) MYMXINTERNALSRVNAME

This seemed to solve the problem with that 6004 error. I believe it has something to do with an IPv6/IPv4 incompatibility problems with Outlook Anywhere/rpcoverhttp.

More info at:

FreeNAS won’t boot from USB


I was setting up FreeNAS 8.03 and ran into a problem when trying to boot off the USB stick as is recommended by the FreeNAS documentation.  I am using a Dell Poweredge R610, and It kept locking on the F1:FreeBSD screen. The solution to this was to go into the BIOS, into Boot Options and change the USB Emulation to Hard Disk. After this it booted properly off the USB drive.

I found the answer at the bottom of the forum the following link which has another solution as enabling the EHCI Hand Off BIOS setting. Not sure what kind of brand of server/bios this was but it may point you in the right direction.

Hope this saves someone some time.

Convert OEM Version of Windows Server 2003 to a VMWare Virtual Machine (P2V)


One thing that’s a problem with converting to a vm, is if you have an OEM version of Windows installed. An OEM license is tied to the hardware that you have it was installed on which means that you cannot move this to another machine. The problem arises when you have been using that server for years, have a lot of software and settings on it, the hardware is getting old, and you need to convert it to a VM.  When you convert it to a VM, Windows Activation notices that an OEM license is installed on new hardware, and basically will not allow you to login and will shut the server down.  The most frustrating part about this is that you may have a valid open license,  but W2k3 does not allow you to upgrade the license by any conventional means.

NOTE: W2k8 DOES allow you to switch licenses, so if you have an OEM license installed, BEFORE you convert it, you simply need to right-click on Computer, go to properties, and click “change key” towards the bottom, enter your valid key, and it should convert with no licensing problems.

My environment is I am using VMWare ESXi, 5.x

NOTE: This should be done in a test environment only after a valid backup to your server.  I am merely providing you with instructions that worked for me. They may not work for you. I am not responsible if this does not work or something does not work properly for you. It shouldn’t be a problem since you will not be altering the original server, and if something goes wrong or you run out of time, you can just delete the VM and turn the original machine back on.  Just in case always have a backup of your machine before you try anything.

To do this you must have the following, if you don’t have these, then don’t start the project:

  1. A valid open Windows 2003 license for either the 32bit or 64bit version that you are converting to a virtual machine.
  2. A valid W2k3 Volume License CD or ISO.  You may need use Disk 2 of the server install so keep that in mind.  If you’re using ISO’s you should mount both of the disks before you start the VM, that way you don’t have to worry about it.
  3. Download VMware-converter  (I used version 5.0.0-470252)
  4. Obviously a working vmware server.
  5. A timetable of around 3-5 hours depending on how big your server takes to convert, your internet connection speed to download/install the updates.

Here are the steps:

  1. Install all Windows security updates to your W2k3 installation before you do this and make sure it is working properly after. This is important because you will most certainly need to reinstall all of these updates later before your server works properly.
  2. Use vmware converter to convert your server to a virtual machine.
  3. If possible shut down your old W2K3 server.
  4. If using ISO Files, upload them to your datastore (do this by using vsphere client to connect to your VMWare server, click on the Summary tab, Rt-Click on your Datastore under the resources column, and choose browse datastore)
  5. Right click your newly created VM, and click “Edit Settings”
  6. Click “Add” and choose “CD/DVD Drive”
  7. Add the CDRom of your virtual server, OR If you have iso files, then choose the path to the ISO files that you copied. If you have disk1 and disk 2, then add 2 drives. Make sure that Connected And/Or Connect at Power On is checked.
  8. While still in the “Edit Settings” screen, go to the “Options” tab, then click on “Boot Options” and click the box to force you into the bios settings.
  9. At this point you may want to shut down the original server so there are no conflicts.
  10. Open the console for the VM and start the machine
  11. It should boot to the BIOS, Go to boot options \, and make sure your cd rom is the first boot device.
  12. Save settings and exit, Let it boot, press any key to boot from the CD
  13. Choose “Install”, then when it finds your operating system, then repair it.
  14. It will now do all of the install, and reboot, and ask you to enter the CD Key in which you enter your Volume License key, let it run the install, it should take you to the login screen and allow you to login
  15. Now you want to install VMWare Tools. Do this in Vsphere Client by going to the VM menu, then Guest, then “install/upgrade VMWare Tools”. it takes about 20 seconds for the install dialogue box to come up so be patient.
  16. Now you need to install updates from Windows update until there are no more (even with the SP2 install, there were a ridiculous amount) and if everything goes ok you should be good. If it gives you an error when clicking Windows Update See The Notes Below.
  17. Change the IP address in Windows to that of the old server, remember to  shut down the old server.

Note: When changing the IP address in Windows it will give you an error about a hidden network adapter, that was the adapter that was part of your physical box on your other machine.

Note: On one machine, when trying to click Windows Update from the IE Tools menu I got an error “the requested lookup key was not found in any active activation context”  To resolve this I opened up a run prompt, navigated to c:\windows\ie8\spuninst\  and ran spuninst.exe. This uninstalled IE8 and restored the update functionality in IE6.

IPSec does not start

1 Comment

On a Windows 2003 Server I had someone “clean” my registry of their old program for an upgrade that I couldn’t complete.  All I had to do was wait after hours and reboot the server. Well when I went to reboot the server a lot of my services would not start. Including Microsoft Exchange IS  and Exchange MTA stacks (nightmare!!!)  One of the things I noticed was that the first error to pop up in the event viewer was event id 4292

“The IPSec driver has entered Block mode. IPSec will discard all inbound and outbound TCP/IP network traffic that is not permitted by boot-time IPSec Policy exemptions.”

If I went to services.msc and tried to start the service manually, it would give me the error:

“Error 10048: only one usage of each socket address (protocol/network adress/port) is normally permitted.”

First as a temporary fix  you might try the following for the heck of it which refers to it being caused by an MS update..

But if that doesn’t work try to perform this KB article which fixed my problem completely. Please note that you HAVE to reboot after this (i tried not rebooting and tried to just start the service and it didn’t resolve the problem). Before you delete the key that Microsoft instructs you to delete in the following article, you might want to right click and export it to a file just in case.  As a disclaimer I don’t take any responsibility for any registry corruption or errors.

Another thing I read was that you can disable the IPsec service and reboot server, but that would be as a last resort.  Good Luck.





Factory Restore From The Dell Recovery Partition When The Repair Option Does Not Work


Recently someone gave me their Dell Mini 1018 that didn’t work.  It was Windows 7, so, according to Dell, the instructions to perform a Factory Restore were to tap F8 when the Dell logo appears and click Repair Computer (BTW Windows XP is Ctl-F11 after you first turn on the computer).  This is great if the computer boots into the recovery partition, but if it doesn’t you’re almost out of luck.  There could be 2 reasons why your computer might not boot into the recovery partition, one is that you erased the recovery partition, in which case I think you may have to order the recovery CDs from dell and get an external CD drive or put the CD’s onto a bootable USB stick. The other one is that for whatever reason the partition is there but the computer cannot boot to it.

NOTE: These instructions will completely wipe out your data.  You should have someone who is familiar with installing and repairing operating systems. I take no responsibility for lost data or screwing up your computer any more than it already is.  I assume if you are performing these steps you are unable to even boot your computer into Safe Mode.  If you need to get your data (pics, music) off first, a good solution would be to boot from a Ubuntu Live CD, click Try Ubuntu, and then copy all your files to a USB stick. Or if you can boot into safe mode (it will give you the option if you keep hitting F8 after the dell logo disappears) you can get your files off with a USB stick, copying to a network folder, or maybe burning a disk I will try to create instructions on how to do this in the near future and put a link here.

One of the most important parts of this is to make sure that you have not wiped out your recovery partition. One way to figure out if you have the recovery partition is when you first go into the command prompt detailed in the instructions below, try typing in d:  and then type in dir.  it should say “Volume in drive D is RECOVERY” and display a couple of files. (if you want to see all files try dir /a)

You will need to boot into recovery mode in Windows, you can do this using a Windows CD or a bootable Windows 7 USB stick, and getting to a command prompt, by clicking on repair your computer, and going to recovery options.

I received these commands from the following site:


  1. Boot into the Windows 7 Setup CD or USB stick by pressing F12 during the dell logo.
  2. After the CD loads choose your language, and then on the screen wher it says Install Now, on the bottom left there should be an option to “Repair Now” click this
  3. System Recovery Options now comes up and it will search for Windows Installations, when it’s finished make sure “use recoevery tools that can help fix problems…” is selected and click next
  4. You should now come up to a screen that has a bunch of selections, one of them being  “command prompt” click this
  5. Now it should come up with a prompt that says  X:\Sources. Type “diskpart”


  1. The prompt should change to DISKPART>, type “list disk”
    1. DISKPART>list disk
    2. You should then get something that looks like this:

DISK ###              STATUS                      SIZE                  FREE                      DYN       GPT
Disk 0                    Online                   232 GB                  0 B
Disk 1                    No Media                 0 B                     0 B

  1. Now you want to choose your disk. It will MOST LIKELY be the disk that is the largest, . In my case above it is “disk 0” at 232GB.  Yours may be different, for instance if you have an external drive attached or 2 hard drives or a USB stick plugged in.  Type the following at the DISKPART prompt replacing the disk that you have:
    1. DISKPART>select disk 0

It will say: Disk 0 is now the selected disk

  1. Now type “list partitions” to list the partitions on the selected disks
    1. DISKPART>list partitions
    2. You should get something that looks like this:

Partition ###                     Type                      Size               Offset
Partition 1                   OEM                      100 MB                 1024 KB
Partition 2                  Primary                    9 GB                  101 GB
Partition 3                   Primary                  223 GB                    9 GB

  1. If you look above, the obvious partition that stores all the files is Partition 3, because it is extremely large (223GB)  Again Be careful, if you have an external hard drive plugged in it may show up here and you could wipe it out.  I would suggest unplugging anything else beforehand just in case. Now type “select partition 3”
    1. DISKPART>select partition 3
    2. Now that you have selected the correct partition, you need to format it.  This step will wipe out your data and can take a very long time.  If you are not sure what you’re doing then type exit, if you want to continue then type “format”
      1. DISKPART>format

You are not done yet, all we did here was wipe out the data on your drive. Now that the data is wiped out, you need to apply the Dell Factory Restore image to the drive.  Here are the instructions for this.  I

  1. Type exit to leave the DISKPART> prompt  Your new prompt should look like this
    1. X:\Sources>
    2. You will now want to switch to your Recovery partition, which will most likely be drive D:\.  Type in the following 2 commands
      1. X:\Sources>d:
      2. D:\>dir
      3. You should see the following

Volume in drive D is RECOVERY
Volume Serial Number is 3ADB-70AC (this will vary)

04/18/2012                         4:54    AM                4,106     ADRInfos.xml
12/25/2010                         12:28 AM             <DIR>    Recovery
                                                  1 File(s)           4,106 bytes
                                                  1 Dir(s)    5,184,368,640 bytes free

If you see the “volume in Drive D is Recovery” then you are definitely in the right drive, if not you want to try to E: F: G: H:  etc and then do a dir until you are on the recovery drive.

  1. This is the part where you apply the image.  You will type the following:
    1. D:\>imagex /apply d:\dell\image\factory.wim 1 c:\
    2. The above command should apply the dell image to your C drive and restore your drive to factory defaults.
    3. After it’s done just type “Exit” to leave the command prompt and then click the restart button.
    4.   There could be a problem here. We’re assuming that c: is the drive that you are installing this to (check this by switching to c:, and performing a dir, there should be no data on it because we wiped it out before.
    5. Another problem (and I ran to this problem on mine) is that there is no imagex program. You will get the error message: “ ‘imagex’ is not recognized as an internal or external command, operable prgram or batch file”  In this case you will have to download the program “imagex” off of the internet (do a google search) and copy it to the D: drive.  What you can do is copy it to a USB stick, plug it into the computer.  Then figure out what directory the USB stick is named by trying the different letters E: F: G: H: I: J:, and doing a Dir to see if you see the file.  If after a dir you see it then just type xcopy imagex.exe d:’, switch back to the D drive, and run the command in step A again.  Mine happened to be located on drive H: but I also had an external CDROM plugged.

Another note is that I got the imagex program by downloading the file from Windows Automated Installation Toolkit If you need it for another OS just google it.


Yet Another Note: If you get an error 1812 (error restoring image, the specified image file did not contain a resource section), this may be due to dell splitting the image file into multiple files.  If you read Brian M. post below on Nov. 20th 2012 it will explain more, but please be careful, his recovery drive was C: and the drive that he wanted to apply the img file to was D:. If your setup is like mine, and your recovery was d: and the drive to apply it to was c: you will want to reverse the c and the d in the command that he has provided.

I hope this works flawlessly for you. If you’re familiar with Windows commands it should be relatively simple, if not you may have your tech savvy friend perform the steps for you.

Zune HD not recognized Windows 7 64bit

1 Comment

What happens here is that the Zune HD driver does not install in 64bit version of Windows for some machines no matter what you do. So if you install the software via WindowsUpdate, or manually install the software via download it says the drivers are not installed.  I’m going off the top of my head but I think you should be able to figure this out by using this as a guide.

I dont’ have screenshots for this because I fixed it on someone’s home computer, and I don’t own a zune,  but in order to get your Zune going on the 64bit version. I first had to download and install the full version of the Zune HD software which i downloaded from Microsoft Here

Install the software, and connect the Zune after, it doesn’t install the drivers correctly for whatever reason.  What I did to fix this was to go to Device Manager (right click on computer, and then choose manage, then device manager),  find your zune on the right hand side, and Double click on the Zune, go to the driver tab, click update driver, click browse my computer, then click browse. As for the location you want to choose, go to  the directory c:\program files\Zune\Drivers or something like that.  Then choose the folder with your languange (En for english) and choose the driver located in there. Then pretty much next your way through everything.  This enabled me to get the drivers to install properly for the zune.

If that doesn’t work, try to connect the zune, go to device manager, uninstall it (and delete software), reboot, and repeat the steps above.

Sonicpoint Becomes Unresponsive


I have a Sonicpoint N using POE (not sure if this matters) The problem is that everything works ok for about a day but then it becomes unresponsive. In order to get it back to a working condition i would have to unplug the power (ethernet) and then plug it back in. Apparently there are a lot of people who have had this problem as evidenced by this post. According to the post the solution to this is to set the Radio Band to “Standard – 20Mhz Channel” I’ve had it working for 2 weeks now with no problem.

Here’s the steps to get to the Radio Band setting on a Sonicwall NSA240:

1. Log into your Sonicwall (not your Sonicpoint)
2. On the left hand side, expand Sonicpoint.
3. Select Sonicpoints
4. Under Sonicpoint Provisioning Profiles, On the right hand side click “Configure”

5. Choose the 802.11N Radio Tab
6. Next to Radio Band select “Standard – 20MHz Channel

7. Click OK on the bottom.

That should be it. Hope this keeps you from smashing the Sonicpoint against the wall like I was going to do!

Older Entries Newer Entries