MSFT has now released CU5. If you want to read about this update you can look at the link below:


Lets start. First I will put one of my Exchange Servers in Maintenance Mode. Best practice as I have seen if you don’t do this DAG copies give problems. Here are the 4 commands I will be running. You can make this a PS1 script but I like making sure each command has successfully completed. Start Maintenance Mode:

  • Set-MailboxServer <Server Name> -DatabaseCopyActivationDisabledAndMoveNow $True
  • Set-ServerComponentState –Identity <Server Name> –Component HubTransport –State Draining –Requester Maintenance
  • Suspend-ClusterNode –Name <Server Name>
  • Set-MailboxServer –Identity <Server Name>–DatabaseCopyAutoActivationPolicy Blocked

(**You need to open up the Exchange Management Shell as Administrator or point 3 will give you a permission error**)

Now we need to first prepare the Schema and AD before we can proceed with the installation.

From an elevated prompt you can run the following commands:

  • Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
  • Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Once both commands have run and finished you can now run the Exchange 2013 CU5 setup. It will check for any updates which you can skip and the proceed to the upgrade screen.

Now that the setup has completed we need to take the server out of maintenance mode to resume normal operation. We need to run 4 commands again to Stop Maintenance Mode:

(**Remember you need to run these commands as an administrator from an elevated Exchange Management Shell)

  • Set-MailboxServer –Identity <Server Name> –DatabaseCopyAutoActivationPolicy Unrestricted
  • Resume-ClusterNode –Name <Server Name>
  • Set-ServerComponentState –Identity <Server Name> –Component HubTransport –State Active –Requester Maintenance
  • Set-MailboxServer –Identity <Server Name> –DatabaseCopyActivationDisabledAndMoveNow $False

Now that everything is online you can check the DAG Status etc.

Hope it helps

Failed to connect to the configuration database when adding server to SharePoint 2013 farm

Today I installed a new SharePoint 2013 Server to add to my existing farm.

I installed SQL and all the prerequisites for SharePoint, rebooted a couple of times.

After all the installs I installed the April 2014 CU for SharePoint as the second server needs to match the existing one.

The install takes a little while but all was successful. When I launched the SharePoint Products Configuration Wizard and chose to connect to the existing farm I was presented with the error below:

sharepoint product configuration

When I tried to open the data base of the existing server on this server from SQL Management Studio I was presented with the follow error:

  • The target principal name is incorrect. Cannot generate SSPI context.

In Active Directory, I opened the computer record for the Database server. In the attribute list, the servicePrincipalName attribute showed the following entries:

Delete the two MSSQLSvc entries as well as the RestrictedKrbHost entries. Restart the DB server and the problem should be resolved.

Hope it helps

SharePoint 2013 Upgrade Error

Today I ran the SharePoint 2013 April 2014 CU. The extraction and installation was successful.

Upon running the SharePoint Configuration Wizard after the restart, PSCONFIG failed immediately on step 3 with the following error:

  • This upgrade session has been stopped. Possible causes include the process being terminated abruptly or the OS has rebooted. Please restart the upgrade again.

Trying to rack my brain, i remembered i changed the farm admin account password a few weeks ago. Could this be a permission error?

I fired up the SharePoint Management Shell and ran the following command:

  • stsadm -o updatefarmcredentials -userlogin <domain\name> -password <password>

I was presented with this error:

  • Error deploying administration application pool credentials. Another deployment may be active. An object of the type Microsoft.SharePoint.Administration.SPAdminAppPoolCredentialDeploymentJobDefinition named “job-admin-apppool-change” already exists under the parent Microsoft.SharePoint.Administration.SPTimerService named “SPTimerV4”. Rename your object or delete the existing object.

To fix this we need to delete this job. Here is the command I used:

  • $app = Get-SPTimerJob -Identity “job-admin-apppool-change”


After this I ran the above command to update the farm account password and it worked. The command completed successfully.

I now went and ran “PSCONFIG.EXE -cmd Upgrade -inplace b2b -wait”  again and the April 2014 CU for SharePoint Server updated within a matter of minutes.

Now if I go and check the version SharePoint Server 2013 is now on : 15.0.4605.1000

Hope it helps!

SCOM 2012 R2 and SQL 2014

As with the previous post where I upgraded SCCM SQL from 2008 to 2014, I did the same with System Center Operations Manager.

You need to make sure that SQL 2008 is on SP2 and that SQL 2012 is on SP1 or the upgrade will fail on the checks.

After I upgraded these I proceeded to do the upgrade and received an error about custom security settings within SSRS.

I made a copy of the reportserver.config file and then removed all the authentication and security info in the config file. I then ran the checks again and it passed.

SQL 2008 was upgraded to SQL 2014. After the reboot SCOM opened but I received an error on reporting.

I ran the setup for SCOM, removed the reporting feature and then rebooted. After the reboot I went into SQL Reporting and configured it again, pointing to the correct report DB’s for SCOM.

I then re-ran the SCOM setup and installed the Reporting Feature, after the last reboot I was able to login to SCOM and run reports.

I don’t think that SQL 2014 with SCOM 2012 R2 is really supported yet but I wanted to write about this for anyone who wants to test it.

Hope it helps

SCCM 2012 R2 CU1 and SQL 2014

Today I got my hands on SQL 2014. I decided to upgrade my System Centre Configuration Manager Server.

It took a couple of hours as SQL 2008 R2 needed to be on SP2 and SQL 2012 R2 needed to be on SP1.

After 2.4GB’s of updates the SQL 2014 checks passed. The upgrade from SQL 2008 R2 or SQL 2012 takes about 30-60 min.

After the upgrade I rebooted the server, upon starting up SCCM I clicked on the Monitoring tab and went to Reports and lone and behold I was presented with a SOAP error.

I removed the Reporting Services Point, rebooted the machine and the event log was flooded with alerts that SQL Reporting was not functioning. I then attempted to Add the Reporting Services Point back and it wouldnt show the SQL Reporting Services Instance.

Upon some investigation I found CU1 for SCCM 2012 R2. After I applied this I rebooted the server, logged back in and then configured SQL Reporting Services. I made sure that it was looking at the correct DB’s which is ReportServer.

I then stopped and started the Reporting Service, waited a few minutes and no more errors were logged. I went back into SCCM -> Monitoring -> Reports and all 469 reports were showing.

Upon running them I didn’t get a SOAP error again and the reports showed correctly.

Hope it helps.