Exchange 2010 SP1, SP2 or Sp3 Error: Setup cannot continue with the upgrade because the “beremote()” process has open files.

Setup cannot continue with the upgrade because the “beremote()” process has open files:

The error listed above is not something to really stress about.

If you running Symantec Backup Exec you will need to stop the services and then retry the checks, they should all pass and allow you to carry on with your installation.

Hope it helps:


Exchange 2010 Service Pack Update Error – No more endpoints available from the endpoint mapper.

Today I encountered another error whilst doing an upgrade from Exchange 2010 SP2 to SP3. This was an error on my part as I will explain shortly. The error you can get when updating the UM Role is as follows:

“There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)”. There are no more endpoints available from the endpoint mapper.”

Simple fix, the windows firewall service is disabled and needs to be enabled, once enabled you need to reboot the Exchange Server, once that is done make sure that the service is started and then run your setup again.

I disabled the service quite a while back that is why I go this error.

Hope it helps.

Exchange 2010 SP3 Upgrade Error

Today whilst busy updating one of my other sites I encountered the following error:

Some controls aren’t valid. Setup previously failed while performing the action “Install”. You can’t resume setup by performaing the action “BuildToBuildUpgrade”.

For some reason Exchange thinks it did not install correctly when the previous installation was done. To fix this you need to edit the Registry, please take note doing so you do at your own risk. Make a backup of your Registry before commencing with the mods.

Open regedit (Start -> run), navigate to the following key:
-> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14

Under each role, Mailbox, Hub Transport, Client Access, have a look for an action and watermark entry, delete these 2 keys and then reboot your Exchange Server. You can now run the installation again of your Service Pack.

Hope it helps.

Exchange 2010 SP3

Today I started with upgrades to Service Pack 3 for Exchange 2010. The download is around 549MB.

Because all my sites run DAG’s I started with the smallest one. Starting with the Passive server I ran the upgrade, the install runs through a list of checks. A new feature that needs to be installed is the RPC over HTTP Proxy. If this is not installed the checks will fail.

The upgrade takes approximately 45 min, time might be different on another set of hardware. SP2 for Exchange is removed and the SP3 installed. So far no issues experienced after the upgrade.

Once the Passive server was completed you need to move your database to the upgraded server and then run the upgrade on the Active one. You should also lockdown your DAG so that the DB does not automatically failover.

Do take note that you still cannot run in coexistence with Exchange 2013 until CU1 is released for Exchange 2010 SP3.

Here is the URL to download SP3:

Also make sure you read the System Requirements prior to upgrading:

Hope it helps.

Exchange 2010 SP2 Federation Trust Setup

Today I got round to setting up a Federation Trust in Exchange 2010.

The steps are pretty straight forward but you need to make sure of the following:

  • Autodiscover for your organization resolves externally, you can test this via the following link:
  • Autodiscover External URL is setup in Exchange.
  • TXT records.

If you open up the EMC in Exchange and click on Organization Configuration you can create a new Federation Trust or Hybrid trust if you running earlier versions of Exchange.

When you create the Trust it gives a warning that you need to create TXT records in DNS. Basically you will have 2 TXT records created, one with you domain name, e.g. and another one

What you need to do is open up the EMS and running the following command to get the proof address:

Get-FederationDomainProof -DomainName
Get-FederationDomainProof -DomainName

You now copy the Proof entry and add this to your TXT record for each one. Allow DNS to replicate, I normally allow mine to replicate for 24 hrs.

The next step is to create a new Accepted domain for and set it to authoritive.

After that click the Organization Configuration node and select the Microsoft Federation Gateway trust under the Federation Trust tab.
Then click Manage Federation in the Actions pane.
Then click Next to bring up the Manage Federated Domains window, click Add and select the Microsoft Federated Trust accepted domain you just created.
Lastly click on Manage.

If your TXT records have not propagated yet you might get the following error:

“Proof of domain ownership has failed. Make sure that the TXT record for the specified domain is available in DNS. The format of the TXT record should be “ IN TXT hash-value” where “” is the domain you want to configure for Federation and “hash-value” is the proof value generated with “Get-FederatedDomainProof -DomainName”.  The proof of domain ownership is not valid or is missing.”

The last part of this is to setup the Organization Relationships:

Click the Organization Relationships tab on the Organization Configuration node in the EMC.
Then click New Organization Relationship in the Actions pane. The New Organization Relationship wizard will start.  Enter a name, you can call it Calendar Share etc., then
select the Enable free/busy information access check-box and specify the free busy data access level you wish to share using the drop-down box.
Then click Next and enter the external domain name or manually enter the information if you have it.

If you get the following error below there are a few things to check:

Error: Federation information could not be received from the external organization.

  • Check that Autodiscover is resolving correctly as mentioned above.
  • Run nslookup to test if the TXT records are showing: nslookup -querytype=TXT
  • Get-FederationInformation -Verbose
  • Check that your External URL property is set, you can check it by typing in the following:

Get-WebServicesVirtualDirectory | fl name,server,InternalURL,ExternalURL

  • If the URL is blank or has the wrong info you can fix it as follows:

Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -ExternalURL

Now you can test by opening a calendar and see if you are able to view calendars. If you get any errors check your application logs on your Exchange server.

Hope it helps.

Exchange 2010 Personal Archives and Outlook 2010 Standard

Today I decided that our environment needs to be cleaned up and PST files that are a major headache are the first things that need to be looked at.

To start off with, MS say that Office 2010 Standard does not support Personal Archives, however I enabled it on my account and it shows, however on a colleagues machine it doesn’t.

So as a work around all I did was give the user full access to there mailbox using the EMC and there you go, that user is able to view his personal archive.

So is this just a permission thing that they don’t tell you about or do you still need to fork out all the money for a Professional Plus Office 2010 License?

Hope it helps.