Thursday 14 November 2013

Exchange 2013 Hybrid - Sorry, it looks like your outbound connectors aren’t set up correctly.

This one was doing my head in.

When adding a domain into 365 for mailflow that was already in my On-Premise environment, i was constantly presented with:

Sorry, it looks like your outbound connectors aren’t set up correctly.

After setting my on-premise outbound connectors in every config possible I then realised I was being a fool and this had to be completed in the Office 365 outbound connector:

Office 365 --> Admin --> Exchange --> Mailflow --> Connectors --> Outbound Connectors

I then added my domain into the scope and hey presto, a verified domain.

Wednesday 8 May 2013

BitLocker Key Recovery



Well its happened to me, quite happily using Windows 8 with BitLocker (full HDD protection) when I hit the dreaded BSOD (with that stupid smiley face!). Windows has an error and it entered a boot loop. I have BitLocker setup to use a password as I don't have a TPM module on my laptop.

I went through the repair and it was asking for the BitLocker recovery key. OK no problem I thought.... Couldn't find it anywhere and panic set in after a day of looking for it. To cut a long story short, after reading lots of articles it looked like i had no hope and may data was lost. So I thought I would have a try at retrieval as no harm done. This is what worked for me (and was very simple!)


  1. I removed the HDD from the Laptop
  2. I plugged it into my Desktop Machine (also running Windows 8)
  3. I was greeted with this screen:

    As you can see it has the BitLocker symbol so it has obviously recognised this as a BitLocker device
  4. Right click on the BitLocker HDD and select the unlock option to get presented with:
  5. Insert your BitLocker password and it will then unlock and mount the drive meaning you can access your data. We need the recovery key so continue:
  6. Open an Administrative Command Prompt and type the following replacing <drive> with the drive letter of your BitLocker HDD

    manage-bde -protectors <DRIVE>: -get

    (e.g  manage-bde -protectors f: -get)
  7. Hey presto you will have your BitLocker Recovery Key password to do with as you please. 
    Just remember to keep it safe so you don't have to go through this process again.
  8. Simply hook up your HDD back to your laptop, etc and you can use it where required.


Sunday 21 April 2013

Exchange 2010 co-exist with 2010 accessing 'EAC' for the first time?

I have just installed exchange 2013 co-existing with Exchange 2010.

Looking for the EMC I discovered it is now the 'EAC' which is all now web based.

The URL is now: https://<CASSERVER>/ecp

However if your accessing the 'EAC' with a mailbox that is still on the Exchange 2010 server you need to access it with the URL:

https://<CASSERVER>/ecp/?ExchClientVer=15

Saturday 20 April 2013

Having issues installing Windows Server 2012 on ESXi 5.0?


Having issues installing Windows Server 2012 on ESXi 5.0?

If your just seeing the black screen with the white stats ring you will need to enable EFI bios in the VM's settings and perform another install:

  1. Right-click the virtual machine and click Power > Shut Down Guest.
  2. Right-click the virtual machine and click Edit Settings.
  3. Click the Options tab.
  4. Click Boot Options.
  5. Click EFI under Firmware.
  6. Click OK
  7. Power on the virtual machine.

Thursday 10 November 2011

VCP 5 Study Begins!

I am currently a VCP 4, VTSP 4 & 5 so I am taking the plunge to obtain my VCP 5. I have Scott Lowe's book - Mastering VMware vSphere 5 in hand, VM Workstation 8 on the laptop and my PowerEdge Server with VMware 5.0 ready to whirl into action.

Some of the good features I have played about with so far are the Auto deploy and the upgrade options. I'm liking vSphere 5, however the new licencing options mean i'm not rolling it out as much as I would like at work and most are still 4.1. Lets face it, 4.1 is still pretty good.

Well the blog shall be becoming populated during my study and I will get some old content (before my old blog imploded) back on!