As a result of my unusual setup, this was a bit more complicated than Sembee posted above,
I joined the 2012 R2 Essentials to the domain, making it an AD Domain Controller. So all the Exchange 2007 objects carried over to the 2012 server. These objects, it turns out, seem to be "hidden", and cannot be found using Active Directory sites and services - more specifically inside Services.
I then synced 2012 R2 to Azure, and migrated Exchange 2007 to Exchange Online. I then demoted the SBS 2008 and removed it from the domain entirely, as it is a VM, and we are migrating all our VMs to AZURE.
Unfortunately all the old SBS 2008 and Exchange 2007 objects are still a part of AD on the 2012 Server, even though Excahnge 2007 is not compatible with 2012.. Meaning, as I understand it, that these objects are not easily accessible... specifically the SCP object.
So the solution:
I managed to find a script to find the SCP via powershell -
$obj = @()
$ADDomain = Get-ADDomain | Select DistinguishedName
$DSSearch = New-Object System.DirectoryServices.DirectorySearcher
$DSSearch.Filter = '(&(objectClass=serviceConnectionPoint)(| (keywords=67661d7F-8FC4-4fa7-BFAC-E1D7794C1F68)(keywords=77378F46-2C66-4aa9-A6A6-3E7A48B19596)))'
$DSSearch.SearchRoot = 'LDAP://CN=Configuration,'+$ADDomain.DistinguishedName
$DSSearch.FindAll() | %{
$ADSI = [ADSI]$_.Path
$autodiscover = New-Object psobject -Property @{
Server = [string]$ADSI.cn
Site = $adsi.keywords[0]
DateCreated = $adsi.WhenCreated.ToShortDateString()
AutoDiscoverInternalURI = [string]$adsi.ServiceBindingInformation
}
$obj += $autodiscover
}
Write-Output $obj | Select Server,Site,DateCreated,AutoDiscoverInternalURI | ft -AutoSize$obj = @()
This revealed the objects that were still inside AD somewhere, and I was then able to use AD Administrative Centre to run a "global catalog search" for all objects that were under the name of the SCP, and from those results, I was able to find the SCP object and delete it. Strangely enough, right clicking and selecting "Locate" fires an error saying location cannot be found.. Sort of expected due to the lack of compatibility. However luckily, deleting the object from here, works.
I came upon this problem, as our all our Outlooks clients started to fire a certificate issue when logging in, even though we were connecting directly to Exchange Online / Office 365, and not to a local server.
Here is the link to the site where I found this script:
http://vanhybrid.com/2012/11/21/retrieving-exchange-autodiscover-scp-information-from-ad-via-powershell/