Exchange 2013 OWA:400 Bad Request

Exchange 2013 OWA:400 Bad Request, ECP Scrambled, ECP Could not load file or assembly ‘Microsoft.Exchange.Common,

To resolve this error after doing some digging around I found that I need to

Open IIS Manager on the client access server

Sites -> Exchange Back End ->ECP -> Application settings (in the middle of the screen)

Double click on BinSearchFolders and replace the value with:

C:\Program Files\Microsoft\Exchange Server\V15\bin;C:\Program Files\Microsoft\Exchange Server\V15\bin\CmdletExtensionAgents;C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\bin

Restart IIS then do the below;

  1. Login to your Exchange 2013 CAS server
  2. Start the Exchange Management Shell
  3. Type cd “C:\Program Files\Microsoft\Exchange Server\V15\Bin\”
  4.  Type UpdateCas.ps1 Windows PowerShell script and wait a few moments.
    This script will rebuild your OWA interface.
  5. Type UpdateConfigFiles.ps1
  6. Now reload your webpage and everything should be sorted!




Deploy Windows Movie Maker through Group Policy (GPO)

I have created this guide for the roll out of Windows Movie Maker through Group Policy (GPO)

Unfortunately Movie Maker is not supplied in an MSI file so we need to use the .exe to deploy it.

For this case we will need the Offline installer file which can be downloaded from the link below

Once this has been downloaded you will need to place it in a network share which is accessible to all computers with the “Everyone” user group permissions.

Example: \\SERVER\Support\Deployment    <—Place your exe inside that folder


We now want to create a new Organisational Unit in Active Directory to TEMPORARILY place the computers in while we do the install. This is so that the computer doesn’t try to install the software each time it boots up.


-The second stage of the deployment is the creation of the Group Policy

Open up a blank notepad document and paste in the following command and chance the part in bold to the server path you made earlier. You can see that after the file path are various switches to make the install silent.

\\SERVER\Support\Deployment\wlsetup-all.exe” /AppSelect:MovieMaker /NOToolbarCEIP /NOhomepage /Nolaunch /NOMO /nosearch /q

Now click File > Save As and make sure it is saved as a .bat file (make sure you save this in a place easily accessible for the time being e.g. Desktop)



Word 2007 and 2010 opening files read only

This is something that I have seen various times which cause users inconvenience.

It’s a really simple fix and  all that is require is the following:

Windows 7;

Go to Start > Computer > In the top right hand corner you will see the preview pane button next to the question mark (help button)

Windows 8;

Go to Start > Type “Computer” > press Enter

In the top right click the arrow underneath the “X”

Click on the view tab and de-select the “Preview Pane”



Provisioning Windows Server 2008 R2

Now that you’ve installed Server 2008 R2 and you’re at your desktop. You’ll want to get a few things provisioned so that everything is ready for installing your roles.

Firstly, I would make sure that you have set a static IP Address

Click on Start > Control Panel > Network and Internet > Network and Sharing Center > Network Connections

Click on Change Adapter Settings


Right click on the network adapter and select properties


Select Internet Protocol Version 4 and Click Properties


Fill in your IP address details and click on OK


Installing Server 2008 R2

Server 2008 R2 Is a great server operating system with many powerful features. The installation is very simple and this is the first of a series of guides based on Windows Server 2008 R2.

– Firstly you want to boot into the ISO or Disc depending on how you are installing. In this environment I’m installing on a virtual machine.

-You will be presented with this screen to chose your language options



-Secondly you will be asked to Accept the License agreement



-Thirdly you will be asked “Upgrade” or “Custom”. Select Custom unless this is an upgrade of an existing server



-Now select the disk which you would like to install Windows Server onto and click next

*****You may also want to specify your partitions here by clicking on Advanced Options****




– Once you have clicked next you will be presented with the following screen which will install then require no user interaction until you are prompted for an admin password. (This usually takes around 30 minutes depending on your hardware)





MS Exchange Active Sync Error 1053

This issue occurs when Exchange hasn’t been given the correct permissions to a certain AD object. It can sometimes occur when a rename takes place or if the mailbox was created and was reconnected to a new user.

To fix this issue, the first thing you’ll want to do is;

– Make sure that you have got Active directory in Advanced Features View…Do this by clicking on View — Advanced Features

– Select the Active Directory object which is having the trouble ie user “John Smith” and right click and select properties

– Go to the security tab and then click on “Add”. Type in the group name Exchange servers as below and click on “Okay”.



– Then click on advanced and you’ll be presented with the following screen


-In the apply to box as below select Descendant msExchActiveSyncDevices objects and also make sure the Allow Modify permissions is checked


– Click on Okay 3 times and then recreate the account on the Exchange Active Sync device.



Increasing Max Send and Receive size in Exchange 2010

Message send and receive limits are by default set to 10MB. This is usually a problem for a lot of users due to the need for sending large attachments or multiple attachments. Since Exchange 2010 was launched the demand for sending large attachments has increased dramatically, most email provides support much larger receive sizes e.g Google support 25MB attachments.

Anyway, to increase the limits in Exchange you can do either of the following;

The first way is to use the Exchange Powershell;

Run these commands below, the change needs to be made in multiple locations so there are multiple commands.

Set-TransportConfig -MaxSendSize 25MB -MaxReceiveSize 25MB

Set-ReceiveConnector “your-connector-name” -MaxMessageSize 25Mb

Set-SendConnector “your-connector-name” -MaxMessageSize 25Mb

Once you have made those changes you can also set a particular mailbox to have a lower Send/Receive limit using this command;

Set-Mailbox “John Smith” -MaxReceiveSize 15Mb -MaxSendSize 15Mb


The second way is to use the Exchange Management Console (EMC);

Firstly we are going to edit the Transport Settings

Browse to Organization Configuration > Hub Transport > Global Settings > Transport Settings, click properties and you’ll the see the screen below. Change the values accordingly



Secondly we are going to change the receive connector

Browse to Server Configuration > Hub Transport > Receive Connectors >Select the Connector > Properties…Then set the required values


Finally we are going to set the Send Connector limit. Before you increase this I would suggest checking with your Smart Host or Relay the maximum sending limit you can send through them otherwise you’ll find another barrier to over come. Usually with the smart hosting  I’ve dealt with I’ve found it to be 50MB. If you send through DNS then you don’t have anything to worry about.

Browse to Organization Configuration > Hub Transport > Send Connectors, select the send connector > Properties…Then change the values accordingly


Send a test message and see if that’s working now. I’ve seen in the past that it takes up to 24 hours for the Outlook clients to accept the new send limit.

Deleted Mailbox Doesn’t Appear In Disconnected Mailbox Panel

This is something that I have found can be extremely scary in times when I have been working on Microsoft Exchange.

Sometimes your happily doing your job recreating a user account and you remove or disable the Exchange user. You head over to Disconnected Mailboxes and the mailbox isn’t there!

No worries it’s a simple task, Exchange won’t populate this field until it has done a database clean up which is a scheduled task which runs at once every 24 hours.

It can be triggered manually by running this command in Exchange powershell;

Get-Mailboxdatabase | Clean-MailboxDatabase

Once run refresh your screen on your mailbox will appear