Microsoft Exchange Server Build Numbers

KB ID 0000344

Problem

To find out what service pack and rollups have been applied to Microsoft Exchange you need to locate its “Build Number”.

2000/2003

2007

2010

Warning: After SP3 the build number does not update.

To find your build number in Exchange 2010 (after SP3,) use the following command;

exsetup | %{$_Fileversioninfo}

2019, 2016, and 2013

Find Exchange 2019 / 2016 and 2013 Build numbers from EMC (PowerShell)

Run the following PowerShell command;

[box]

Get-ExchangeServer | select Name,AdminDisplayVersion

[/box]

Exchange 2019 Build Numbers

Produce Name Build number Date KB
Exchange Server 2019 CU5 15.02.0595.003 17/03/2020  
Exchange Server 2019 CU4 15.02.0529.005 17/12/2019  
Exchange Server 2019 CU3 15.02.0464.005 17/09/2019  
Exchange Server 2019 CU2 15.02.0397.003 18/06/2019  
Exchange Server 2019 CU1 15.02.0330.005 12/02/2019  
Exchange Server 2019 RTM 15.02.0221.012 22/10/2018  
Exchange Server 2019 Preview 15.02.0196.000 24/07/2018  

Exchange 2016 Build Numbers

Produce Name Build number Date KB
Exchange Server 2016 Preview 15.1.225.16 22/06/2015  
Exchange Server 2016 RTM 15.1.225.42 28/09/2015  
Exchange Server 2016 Cumulative Update 1 15.1.396.30 14/03/2016 KB3134844
Exchange Server 2016 Cumulative Update 2 15.01.0466.034 21/06/16 KB3135742
Exchange Server 2016 Cumulative Update 3 15.01.0544.027 20/09/2016 KB3152589
Exchange Server 2016 Cumulative Update 4 15.01.0669.032 13/12/2016  
Exchange Server 2016 Cumulative Update 5 15.01.0845.034 13/12/2017  
Exchange Server 2016 Cumulative Update 6 15.01.1034.026 27/06/2017  
Exchange Server 2016 Cumulative Update 7 15.01.1261.035 19/09/2017 KB4018115
Exchange Server 2016 Cumulative Update 8 15.01.1415.002 19/12/2017 KB4035145
Exchange Server 2016 Cumulative Update 9 15.01.1466.003 20/05/2018 KB4055222
Exchange Server 2016 Cumulative Update 10 15.01.1531.003 19/06/2019 KB4471392
Exchange Server 2016 Cumulative Update 11 15.01.1591.010 16/10/2018

KB4134118

Exchange Server 2016 Cumulative Update 12 15.01.1713.005 12/02/2019  
Exchange Server 2016 Cumulative Update 13 15.01.1779.003 18/06/2019  
Exchange Server 2016 Cumulative Update 14 15.01.1847.003 17/09/2019  
Exchange Server 2016 Cumulative Update 15 15.01.1913.005 17/12/2019  
Exchange Server 2016 Cumulative Update 16 15.01.1979.003 17/03/2020  

Exchange 2013 Build Numbers

Product name Build number Date KB
Microsoft Exchange Server 2013 Preview 15.0.466.13 7/16/2012  
Microsoft Exchange Server 2013 RTM 15.0.516.32 10/11/2012  
Exchange Server 2013 Cumulative Update 1 (CU1) 15.0.620.29 04/27/2013 KB2816900
Exchange Server 2013 Cumulative Update 2 (CU2) 15.0.712.24 07/09/2013 KB2859928
Exchange Server 2013 Cumulative Update 3 (CU3) 15.0.775.38 11/25/2013 KB2892464
Exchange Server 2013 Service Pack 1 (SP1 aka CU4) 15.0.847.32 02/25/2014 KB2926248
Exchange Server 2013 Cumulative Update 5 (CU5) 15.0.913.22 05/27/2014 KB2936880
Exchange Server 2013 Cumulative Update 6 (CU6) 15.0.995.29 08/26/2014 KB2961810
Exchange Server 2013 Cumulative Update 7 (CU7) 15.0.1044.25 12/09/2014 KB2986485
Exchange Server 2013 Cumulative Update 8 (CU8) 15.0.1076.9 03/17/2015 KB3030080
Exchange Server 2013 Cumulative Update 9 (CU9) 15.0.1104.5 06/16/2015 KB3049849
Exchange Server 2013 Cumulative Update 10 (CU10) 15.0.1130.7 09/14/2015 KB3078678
Exchange Server 2013 Cumulative Update 11 (CU11) 15.0.1156.6 12/10/2015 KB3099522
Exchange Server 2013 Cumulative Update 12 (CU12) 15.0.1178.4 3/14/2016 KB3108023
Exchange Server 2013 Cumulative Update 13 (CU13) 15.00.1210.003 21/06/2-16 KB3135743
Exchange Server 2013 Cumulative Update 14 (CU14) 15.00.1236.003 20/09/2016 KB3177670
Exchange Server 2013 Cumulative Update 15 (CU15) 15.00.1263.005 13/12/2017  
Exchange Server 2013 Cumulative Update 16 (CU16) 15.00.1293.002 21/03/2017  
Exchange Server 2013 Cumulative Update 17 (CU17) 15.00.1320.004 27/06/2017  
Exchange Server 2013 Cumulative Update 18 (CU18) 15.00.1347.002 19/09/2017 KB4022631
Exchange Server 2013 Cumulative Update 19 (CU19) 15.00.1365.001 19/12/2017 KB4037224
Exchange Server 2013 Cumulative Update 20 (CU20) 15.00.1367.003 20/05/2018 KB4055221
Exchange Server 2013 Cumulative Update 21 (CU21) 15.00.1395.004 19/06/2019  
Exchange Server 2013 Cumulative Update 22 (CU22) 15.00.1473.003 12/02/2019 KB4345836
Exchange Server 2013 Cumulative Update 23 (CU23) 15.00.1497.002 18/06/2019 KB4489622

Exchange 2010 (SP3) Build Numbers

Product name Build number Date KB
Update Rollup 1 for Exchange Server 2010 SP3 14.3.146.0 5/29/2013 KB2803727
Update Rollup 2 for Exchange Server 2010 SP3 14.3.158.1 8/13/2013 KB2866475
Update Rollup 3 for Exchange Server 2010 SP3 14.3.169.1 11/25/2013 KB2891587
Update Rollup 4 for Exchange Server 2010 SP3 14.3.174.1 12/10/2013 KB2905616
Update Rollup 5 for Exchange Server 2010 SP3 14.3.181.6 2/25/2014 KB2917508
Update Rollup 6 for Exchange Server 2010 SP3 14.3.195.1 5/23/2014 KB2936871
Update Rollup 7 for Exchange Server 2010 SP3 14.3.210.2 8/26/2014 KB2961522
Update Rollup 8-v2 for Exchange Server 2010 SP3 14.3.224.2 12/12/2014 KB2986475
Update Rollup 9 for Exchange Server 2010 SP3 14.3.235.1 3/17/2015 KB3030085
Update Rollup 10 for Exchange Server 2010 SP3 14.3.248.2 6/16/2015 KB3049853
Update Rollup 11 for Exchange Server 2010 SP3 14.3.266.1 9/11/2015 KB3078674
Update Rollup 12 for Exchange Server 2010 SP3 14.3.279.2 12/10/2015 KB3096066
Update Rollup 13 for Exchange Server 2010 SP3 14.3.294.0 3/14/2016 KB3141339
Update Rollup 14 for Exchange Server 2010 SP3 14.3.0301.000 14/06/2016 KB3151097
Update Rollup 15 for Exchange Server 2010 SP3 14.03.0319.002 20/09/2016 KB3184728
Update Rollup 16 for Exchange Server 2010 SP3 14.03.0336.000 13/12/2017  
Update Rollup 17 for Exchange Server 2010 SP3 14.03.0352.000 21/03/2017  
Update Rollup 18 for Exchange Server 2010 SP3 14.03.0361.001 11/07/2017  
Update Rollup 19 for Exchange Server 2010 SP3 14.03.0382.00 19/12/2017 KB4035162
Update Rollup 20 for Exchange Server 2010 SP3 14.03.0389.001 05/05/2018 KB4073537
Update Rollup 21 for Exchange Server 2010 SP3 14.03.0399.002 07/05/2018  
Update Rollup 22 for Exchange Server 2010 SP3 14.03.0411.000 19/06/2018 KB4295699
Update Rollup 23 for Exchange Server 2010 SP3 14.03.0417.001 13/08/2018 KB4340733
Update Rollup 24 for Exchange Server 2010 SP3 14.03.0419.000 05/09/2019 KB4458321
Update Rollup 25 for Exchange Server 2010 SP3 14.03.0435.000 08/01/2019 KB4468742
Update Rollup 26 for Exchange Server 2010 SP3 14.03.0442.000 12/02/2019 KB4487052
Update Rollup 27 for Exchange Server 2010 SP3 14.03.0452.000 09/04/2019 KB4491413
Update Rollup 28 for Exchange Server 2010 SP3 14.03.0461.001 07/06/2019 KB4503028
Update Rollup 29 for Exchange Server 2010 SP3 14.03.0468.000 09/07/2019 KB4509410
Update Rollup 29 for Exchange Server 2010 SP3 14.03.0496.000 11/02/2020 KB4536989

Exchange 2010 (SP2) Build Numbers

Product name Build number Date KB
Microsoft Exchange Server 2010 SP2 14.2.247.5 12/4/2011  
Update Rollup 1 for Exchange Server 2010 SP2 14.2.283.3 2/13/2012 KB2645995
Update Rollup 2 for Exchange Server 2010 SP2 14.2.298.4 4/16/2012 KB2661854
Update Rollup 3 for Exchange Server 2010 SP2 14.2.309.2 5/29/2012 KB2685289
Update Rollup 4 for Exchange Server 2010 SP2 14.2.318.2 8/13/2012 KB2706690
Update Rollup 4-v2 for Exchange Server 2010 SP2 14.2.318.4 10/9/2012 KB2756485
Update Rollup 5 for Exchange Server 2010 SP2 14.2.328.5 11/13/2012 KB2719800
Update Rollup 5-2 for Exchange Server 2010 SP2 14.2.328.10 12/10/2012 KB2785908
Update Rollup 6 for Exchange Server 2010 SP2 14.2.342.3 2/11/2013 KB2746164
Update Rollup 7 for Exchange Server 2010 SP2 14.2.375.0 8/13/2013 KB2874216
Update Rollup 8 for Exchange Server 2010 SP2 14.2.390.3 12/10/2013 KB2903903

Exchange 2010 (SP1) Build Numbers

Product name Build number Date KB
Microsoft Exchange Server 2010 SP1 14.1.218.15 8/24/2010  
Update Rollup 1 for Exchange Server 2010 SP1 14.1.255.2 10/4/2010 KB2407028
Update Rollup 2 for Exchange Server 2010 SP1 14.1.270.1 12/9/2010 KB2425179
Update Rollup 3 for Exchange Server 2010 SP1 14.1.289.3 3/7/2011 KB2529939
Update Rollup 4 for Exchange Server 2010 SP1 14.1.323.1 6/22/2011 KB2509910
Update Rollup 4-v2 for Exchange Server 2010 SP1 14.1.323.6 7/27/2011 KB2579150
Update Rollup 5 for Exchange Server 2010 SP1 14.1.339.1 8/23/2011 KB2582113
Update Rollup 6 for Exchange Server 2010 SP1 14.1.355.2 10/27/2011 KB2608646
Update Rollup 7 for Exchange Server 2010 SP1 14.1.421.0 8/13/2012 KB2743248
Update Rollup 7-v2 for Exchange Server 2010 SP1 14.1.421.2 10/9/2012 KB2756496
Update Rollup 7-v3 for Exchange Server 2010 SP1 14.1.421.3 11/12/2012 KB2778158
Update Rollup 8 for Exchange Server 2010 SP1 14.1.438.0 12/10/2012 KB2787763

Exchange 2010 Build Numbers

Product name Build number Date KB
Microsoft Exchange Server 2010 RTM 14.0.639.21 11/9/2009  
Update Rollup 1 for Exchange Server 2010 14.0.682.1 12/9/2009 KB976573
Update Rollup 2 for Exchange Server 2010 14.0.689.0 3/4/2010 KB979611
Update Rollup 3 for Exchange Server 2010 14.0.694.0 4/9/2010 KB981401
Update Rollup 4 for Exchange Server 2010 14.0.702.1 6/17/2010 KB982639
Update Rollup 5 for Exchange Server 2010 14.0.726.0 12/13/2010 KB982639

Exchange 2007 (SP3) Build Numbers

Product name Build number Date KB
Microsoft Exchange Server 2007 SP3 8.3.083.6 6/20/2010  
Update Rollup 1 for Exchange Server 2007 Service Pack 3 8.3.106.2 9/9/2010 KB2279665
Update Rollup 2 for Exchange Server 2007 Service Pack 3 8.3.137.3
12/10/2010
KB2407025
Update Rollup 3 for Exchange Server 2007 Service Pack 3 8.3.159.0
3/2/2011
KB2530488
Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3 8.3.159.2
3/30/2011
KB2530488
Update Rollup 4 for Exchange Server 2007 Service Pack 3 8.3.192.1
7/7/2011
Update Rollup 5 for Exchange Server 2007 Service Pack 3 8.3.213.1
9/21/2011
KB2602324
Update Rollup 6 for Exchange Server 2007 Service Pack 3 8.3.245.2
1/25/2012
KB2608656
Update Rollup 8 for Exchange Server 2007 SP3 08.03.0279.003
13/08/2012
 
Update Rollup 8-v2 for Exchange Server 2007 SP3 08.03.0279.005 09/10/2012  
Update Rollup 8-v3 for Exchange Server 2007 SP3 08.03.0279.006 13/11/2012  
Update Rollup 9 for Exchange Server 2007 SP3 08.03.0297.002 10/12/2012  
Update Rollup 10 for Exchange Server 2007 SP3 08.03.0298.003 11/02/2013  
Update Rollup 11 for Exchange Server 2007 SP3 08.03.0327.001 13/08/2013  
Update Rollup 12 for Exchange Server 2007 SP3 08.03.0342.004 09/12/2013  
Update Rollup 13 for Exchange Server 2007 SP3 08.03.0348.002 24/02/2014  
Update Rollup 14 for Exchange Server 2007 SP3 08.03.0379.002 26/08/2014  
Update Rollup 15 for Exchange Server 2007 SP3 08.03.0389.002 09/12/2014  
Update Rollup 16 for Exchange Server 2007 SP3 08.03.0406.000 17/03/2015  
Update Rollup 17 for Exchange Server 2007 SP3 08.03.0417.001 17/06/2015  
Update Rollup 18 for Exchange Server 2007 SP3 08.03.0445.000 01/12/2015  
Update Rollup 19 for Exchange Server 2007 SP3 08.03.0459.000 15/03/2016  
Update Rollup 20 for Exchange Server 2007 SP3 08.03.0468.000 21/06/2016 KB3151086
Update Rollup 21 for Exchange Server 2007 SP3 08.03.0485.001 20/09/2016 KB3184711
Update Rollup 22 for Exchange Server 2007 SP3 08.03.0502.000 13/12/2016  
Update Rollup 23 for Exchange Server 2007 SP3 08.03.0517.000 21/03/2017  

Exchange 2007 (SP2) Build Numbers

Product name Build number Date KB
Microsoft Exchange Server 2007 SP2 8.2.176.2 8/24/2009  
Update Rollup 1 for Exchange Server 2007 Service Pack 2 8.2.217.3 11/19/2009 KB971534
Update Rollup 2 for Exchange Server 2007 Service Pack 2 8.2.234.1 1/22/2010 KB972076
Update Rollup 3 for Exchange Server 2007 Service Pack 2 8.2.247.2 3/17/2010 KB979784
Update Rollup 4 for Exchange Server 2007 Service Pack 2 8.2.254.0 4/9/2010 KB981383

Exchange 2007 (SP1) Build Numbers

Product name Build number Date KB
Microsoft Exchange Server Exchange 2007 SP1 8.1.240.6 11/29/2007  
Update Rollup 1 for Exchange Server 2007 Service Pack 1 8.1.263.1 2/28/2008  
Update Rollup 2 for Exchange Server 2007 Service Pack 1 8.1.278.2 5/8/2008  
Update Rollup 3 for Exchange Server 2007 Service Pack 1 8.1.291.2 7/8/2008 KB949870
Update Rollup 4 for Exchange Server 2007 Service Pack 1 8.1.311.3 10/7/2008 KB952580
Update Rollup 5 for Exchange Server 2007 Service Pack 1 8.1.336.1 11/20/2008 KB953467
Update Rollup 6 for Exchange Server 2007 Service Pack 1 8.1.340.1 2/10/2009 KB959241
Update Rollup 7 for Exchange Server 2007 Service Pack 1 8.1.359.2 3/18/2009 KB960384
Update Rollup 8 for Exchange Server 2007 Service Pack 1 8.1.375.2 5/19/2009 KB968012
Update Rollup 9 for Exchange Server 2007 Service Pack 1 8.1.393.1 7/17/2009 KB970162
Update Rollup 10 for Exchange Server 2007 Service Pack 1 8.1.436.0 4/9/2010 KB981407

Exchange 2007  Build Numbers

Microsoft Exchange Server 2007 8.0.685.24 12/9/2006  
Microsoft Exchange Server 2007 8.0.685.25 12/9/2006  
Microsoft Exchange Server 2007 SP1 8.1.240.6 11/29/2007  
Microsoft Exchange Server 2007 SP2 8.2.176.2 8/24/2009  
Microsoft Exchange Server 2007 SP3 8.3.083.6 6/20/2010  

Exchange 2003 Build Numbers

Exchange Server 2003
Product name Build number Date  
Microsoft Exchange Server 2003 6.5.6944 6/30/2003  
Microsoft Exchange Server 2003 SP1 6.5.7226 5/25/2004  
Microsoft Exchange Server 2003 SP2 6.5.7638 10/19/2005  

 

Related Articles, References, Credits, or External Links

NA

Event ID 9314

KB ID 0000358

Problem

Event ID 9314

The account specified for the Microsoft Exchange Server Mailbox Manager Administrator is invalid. No mailboxes will be processed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Either the account specified to run the Mailbox Manager process does not have rights, or an account has not been specified.

 

Solution

1. Launch Exchange System Manager on one of your Exchange 2003 Servers. (Start > All Programs > Microsoft Exchange > system Manager).

2. Expand the Organisation > Administrative Groups > Administrative group name (i.e. First Administrative Group) > Servers > Servername > Right Click > Properties > Mailbox Management > Browse.

3. Select the Administrator account and add it in > Apply > OK.

4. At this point I would restart all the exchange services and apply the “Cup Of Coffee Rule” before proceeding.

5. After waiting a while right click each server that’s running the policy and select “Start Mailbox Management Process”.

Note: Depending on the size of the mail store(s) this can take some time (tip – Right click the servername and if you see “Stop the mailbox Management Process” it’s not finished yet.

Related Articles, References, Credits, or External Links

NA

Event ID 3

KB ID 0000341 

Problem

Event ID 3

Source: SystemServiceModel

Error: WebHost failed to process a request. Sender Information.

Exception: System.ServiceModel.ServiceActivationException: The service ‘/EWS/exchange.asmx’ cannot be activated due to an exception during compilation.  The exception message is: Security settings for this service require ‘Anonymous’ Authentication but it is not enabled for the IIS application that hosts this service.. —> System.NotSupportedException: Security settings for this service require ‘Anonymous’ Authentication but it is not enabled for the IIS application that hosts this service.

It’s simple permissions error in IIS.

Solution

1. Locate the Virtual Directory in the error message, in the example above that the EWS virtual directory. (Exchange Web Services).

2. Click Start > Administrative Tools > Internet Information Services (IIS) Manager > Expand Sites > Default Web sites > locate the problem virtual directory > Select it then open authentication.

3. Make sure “Anonymous Authentication” is set to enabled.

4. Then restart web services, click Start > in the run/search box type cmd{enter} > Execute the following command,

[box]iisreset /noforce[/box]

Related Articles, References, Credits, or External Links

NA

Exchange – Slow Shutdown and Reboot on a Domain Controller

 

KB ID 0000565 

Problem

To be fair Microsoft recommend that you DO NOT install Exchange on a domain controller. Not only does it cause quite a performance hit on the server, but because of the way services are stopped on the server at shutdown time, the Exchange services take AGES to stop (In fact they end up timing out).

Quite how this explains SBS (Which is a domain controller with Exchange on it) I’m not really sure, perhaps because it’s limited to 75 users Microsoft think that’s OK? But you will still come across Exchange on Domain controllers. I’ve even seen people promote Exchange servers to be domain controllers to fix replication problems. Also If you are in a test environment having one server is more sensible than two (All my test Exchange boxes are domain controllers to save space).

Solution

You can of course manually stop all the Exchange services every time you want to reboot or shutdown. That’s fine in principle but every time you forget you will have annoyed users asking how long it’s going to be down for.

To save that happening I’ve got a script that puts a shutdown shortcut on your desktop (or in the Quick Launch bar if your running on Windows Server 2003). There’s a different one for each version of Exchange, 2010, 2007, and 2003.

Exchange 2010 Slow Shutdown and Reboot on Domain controller.

1. Download this zip file > Extract it > Run the Install.bat file.

2. Then use the shortcut, that’s created to shutdown or reboot the server.

Exchange 2007 Slow Shutdown and Reboot on Domain controller.

1. Download this zip file > Extract it > Run the Install.bat file.

2. Then use the shortcut, that’s created to shutdown or reboot the server.

Exchange 2003 Slow Shutdown and Reboot on Domain controller.

1. Download this zip file > Extract it > Run the Install.bat file.

2. Then use the shortcut, that’s created to shutdown or reboot the server.

Related Articles, References, Credits, or External Links

NA

Allow a Server to “Relay” Through Microsoft Exchange

KB ID 0000542

Problem

Back in the early days of email, just about all mail servers let you relay mail though them. That was fine until someone worked out you could then get someone else to send out your “spam”, and they would look like the guilty party. Even today people misconfigure their Exchange servers and make them an open relay.

But what happens if you have a particular server or machine that you want to let use your Exchange server as a relay? e.g. a Linux server that sends mail, or a SQL server running SQLMail? Then you need to allow relaying from either that IP address, or the network it’s on.

Allow Relay from an IP with Office 365 (Exchange Online)

Allow Relay from an IP with Exchange 2016 & 2013

Allow Relay from an IP with Exchange 2010

Allow Relay from an IP with Exchange 2007

Allow Relay from an IP with Exchange 2003

Allow Relay from an IP with Exchange 2000

Solution

Allow Relay from an IP with Exchange 2010 and 2007

1.From the Exchange Management Console > Server Configuration > Hub Transport > New Receive Connector.

2. Give the connector a name and select Custom > Next.

3. Next.

4. Add > Add in the IP address(s) or network you want to allow relay from > OK.

5. Select the 0.0.0.0 255.255.255.255 entry and click DELETE.

Warning: Leaving this entry in will make your Exchange Server an Open Relay. (Note: This does NOT mean that your default connector is an “Open Relay” as this uses “authentication”

6. Next.

7. New.

8. Finish.

9. Select your new connector then right click > Properties.

10. On the Permission Groups tab ensure “Exchange Servers” is selected.

11. On the Authentication Tab > Tick “Externally Secured (for example with IPSEC).” > Apply > OK.

Allow Relay from an IP with Powershell

The following Powershell does the same as above;

[box]New-ReceiveConnector -Name “Server2 Allow Relay” -usage Custom -Bindings ’0.0.0.0:25′ -RemoteIPRanges 172.16.254.207 -server DC2A – -permissiongroups ExchangeServers -AuthMechanism ‘TLS, ExternalAuthoritative’[/box]

Allow Relay from an IP with Exchange 2003 and 2000

1. Launch Exchange System Manager > Administrative Groups > Administrative group Name > Servers > Servername > SMTP > Right click Default SMTP Virtual Server > Properties.

Note: If you can’t see administrative groups right click the top level (in this case “First Organization (Exchange)) and tick the box to show administrative groups.

2. Access Tab > Authentication > Ensure “Anonymous Access” is enabled.

3. Click Relay > Ensure the default of “Only the list below” is selected > Add.

4. Add in the IP addresses(s) networks or domains you want to allow ‘relaying’ from > OK.

5. OK > Apply > OK.

 

Related Articles, References, Credits, or External Links

Exchange – Are you an Open Relay?

Exchange – New User(s) Not Showing Up On Global Address List

KB ID 0000775 

Problem

If you create a new user, give them a mailbox, and they seemingly fail to appear then don’t panic!

Firstly and fore mostly: If you do anything in Exchange: Apply the “cup of coffee rule”, never make a change then go and prove that change works straight away! check it later.

However most of us work in the real world and you have a user who needs to use this mailbox yesterday!

Bear in mind, the process you need to follow is;

1. Make sure the user does have a mailbox.
2. Make sure that user/mailbox is on the GAL.
3. Make sure the OAB you are looking at, has been updated from the GAL.
4. If using Outlook, query the GAL directly, or download the latest OAB.

Solution

Make sure the User Does Have a Mailbox

1. Before you do anything send the user you created a ‘Test Email’ from your own account. If you receive an error message then you can investigate further (Note: Set your Outlook client to send you a delivery report on the test email as well). Then check the mailbox Exists (See Check for existence of mailbox sections below).

Check for the Existence of the mailbox (Exchange 2000 /2003)

1. Click Start > All Programs > Microsoft Exchange > System Manager.

2. Expand the Exchange Organisation > Administrative groups > Administrative group name (First Administrative group is the default).

Note: If you cannot see Administrative Groups right click the Very top object > Properties > Tick Display Administrative Groups.

3. Expand Servers > Server-name > Storage Group (First Storage group will be the default) > Mailbox Store > Mailboxes.

4. The Mailbox SHOULD be in the right hand window (Providing you are in the correct administrative group, on the correct server, and in the correct mailbox store!).

Check for the Existence of a mailbox (Exchange 2007/2010)

Remember with Exchange 2007 / 2010 you create the mailbox with the Exchange system Manager anyway!

1. On the Exchange Server, Start > All Programs > Microsoft Exchange Server 2007 > Exchange Management Console.
2. Expand recipient Configuration > Mailbox.
3. The Mailbox should be listed in the centre window.

Check for the Existence of a mailbox (Exchange 2013/2016)

Connect to the Exchange admin center > recipients > mailboxes > locate your user.

Mailbox is there but the user is not listed on the Global Address List

1. Make sure the user is not “Hidden from the Global Address List”

Exchange 2000/2003

On the Exchange Server > Click Start > run > dsa.msc {enter} >Locate the user in question > Right Click the user > Properties > Exchange Advanced Tab > Ensure “Hide from Exchange Address Lists” is NOT ticked.

Exchange 2007/2010

On the Exchange Server > Start > All Programs > Microsoft Exchange Server 2007 > Exchange Management Console Expand recipient Configuration > Mailbox > Locate the Mailbox for the user in question > Right Click the Mailbox > Properties > General Tab > Ensure “Hide From Exchange Address Lists” is NOT ticked.

Exchange 2013/2016

Connect to the Exchange admin center > recipients > mailboxes > locate your user > Edit > Ensure “Hide From Exchange Address Lists” is NOT ticked.

Make sure the user is on the Global Address List on the server.

The easiest way to do this is simply connect to Outlook Web Access, and query the GAL directly (OWA uses the GAL no the OAB like Outlook running in cached mode does).

Exchange 2000/2003

Click Start > All Programs > Microsoft Exchange > System Manager > Expand Recipients >All Global Address Lists > Right Click Default Global Address List > Properties > General Tab > Preview > Check the user is on this list.

Exchange 2007/2010

On the Exchange Server > Start > All Programs > Microsoft Exchange Server > Exchange Management Console > Select Organisation Configuration > Mailbox > Address Lists Tab > Locate the all users Object > Double Click it > Select Preview > Check the user is on this list > OK > Cancel.

Exchange 2013/2016

Connect to the Exchange admin center > organization > address lists > Default Global Address List > Edit > Preview recipients in the global address list includes… > Locate the user.

The User/Mailbox IS listed on the Server But NOT in Outlook.

Remember, if you are looking at the Global Address List in Outlook then you are NOT looking at the Servers Global Address List*. If you are using Outlook  you may be in “Cached Mode”, and you are looking at a copy called the “Offline address book” This only gets updated Every 24 hours, and the copy on the server only gets updated every 24 hours at 04:00 (by default). In addition to this there a a few methods by which your Outlook clients get the offline address book.

*Note: Unless you are NOT in cached mode.

Outlook 2003 (and older)* clients get their OAB from a public folder, Outlook 2007 (and newer) clients can get their OAB from ‘Web-based distribution’ (basically form the website on the Exchange (or Exchange CAS) server. So there are three factors stopping you seeing that new user on the GAL (I personally advise you simply wait, however if that’s not an option, read on).

*Exchange Supported versions of Outlook

Support for Outlook 2000 was dropped with Exchange 2007, Exchange 2010 only supports Outlook 2003 (post SP2). Exchange 2013 only supports Outlook 2007 (post SP3 and cumulative update), and Outlook 2010 must be at SP1 with cumulative update.

a. Firstly force update the Offline Address Book.
b. Force your Outlook Client to Download the Offline Address book.
c. Check that the OAB is getting distributed from the Exchange/CAS server.

Update the Offline Address Book from the Global address List

Exchange 2000 / 2003

Click Start > All Programs > Microsoft Exchange > System Manager > Expand Recipients > Offline Address Lists > Right Click the “Default Offline Address Book” > Rebuild > HEED THE WARNING > OK > Right Click it again > Properties, You will see the time it updates (by default) you can change that here..

Exchange 2007 / 2010

1. On the Exchange Server > Start > All Programs > Microsoft Exchange Server 2007 > Exchange Management Console > Select Organisation Configuration > Mailbox > Offline address book tab > Right Click the Default Offline Address Book > Update > HEED THE WARNING > OK > Right Click Again > Properties > You can change the Schedule at which it updates.

Exchange 2013/2016

You can also force the OAB update with the following PowerShell command;

[box] get-offlineaddressbook | update-offlineaddressbook [/box]

Check the OAB is getting Distributed to Outlook

Exchange 2000 / 2003

Click Start > All Programs > Microsoft Exchange > System Manager > Expand the Exchange Organisation > Administrative groups > Administrative group name (First Administrative group is the default) > Expand Servers > Server-name > Storage Group (First Storage group will be the default) > Public Folder Database > Ensure it is mounted.

Then expand Folders > Public Folders > OFFLINE ADDRESS BOOK > Make sure it’s displayed as per the image below.

Exchange 2007 / 2010

On the Exchange Server > Start > All Programs > Microsoft Exchange Server > Exchange Management Console > Select Organisation Configuration > Mailbox > Offline address book tab > Right Click the Default Offline Address Book > Properties > Distribution.

Note: Make sure the Generation Server is set to a server that exists, and it’s online.

In the diagram below you can see this server is performing public folder AND web based distribution, this is probably because you ticked this box when you installed the product.

For public folder distribution ensure the public folder database is mounted, and at least one server holds a replica. Also in the properties of the mailbox database, your users are using, make sure it points to the correct public folder database.

For web-based distribution make sure the site is up.

Exchange 2013/2016

Exchange 2013/2016 will only be distributing the OAB via web-distribution. make sure the default website is up.

Force Outlook to Download the New Offline Address Book

For all versions of Outlook (since 2003) you have two choices, either take Outlook out of cached mode* (so it queries the ‘live’ global address list). Or force Outlook to download the latest version of the offline address book.

*Note: Disabling cached mode is not really a fix!

Outlook 2003 Download The Offline Address Book

Tools > SendReceive > Download Address Book > OK.

Outlook 2003 Turn off Cached Mode

Tools > E-mail Accounts > View or change existing email accounts > Next > Select the account > Change > un-tick “Use Cached Exchange Mode” > Next.

Outlook 2007 Download The Offline Address Book

Tools > SendReceive > Download Address Book > OK.

Outlook 2007 Turn off Cached Mode

Tools > Account Settings > Select the account > Change > un-tick “Use Cached Exchange Mode” > Next.

Outlook 2010 Download The Offline Address Book

Send/Receive > Send/Receive Groups > Download Address Book > OK.

Outlook 2010 Turn off Cached Mode

File > Account Settings > Account Settings > Select the account > Change > un-tick “Use Cached Exchange Mode” > Next.

 

Outlook 2013/2016 Download The Offline Address Book

Send/Receive> Send/Receive Groups > Download Address Book > OK.

Outlook 2013/2016 Turn off Cached Mode

File > Account Settings > Account Settings > Select the account > Change > un-tick “Use Cached Exchange Mode” > Next.

 

Related Articles, References, Credits, or External Links

Exchange 2013 – Working with and Managing the OAB

 

 

Exchange 2013 – ‘Internet Explorer has stopped working’

KB ID 0000776

Problem

When using the Exchange Admin Center with Exchange 2013, on a Server Running Internet Explorer Version 10, you see the following error (particularly when working on the recipients > mailboxes tab!

Problem Details

Problem signature:
Problem Event Name: APPCRASH
Application Name: IEXPLORE.EXE
Application Version: 10.0.9200.16384
Application Timestamp: 50107ee0
Fault Module Name: msvcrt.dll
Fault Module Version: 7.0.9200.16384
Fault Module Timestamp: 5010ae12
Exception Code: c0000005
Exception Offset: 0000986a
OS Version: 6.2.9200.2.0.0.400.8
Locale ID: 2057
Additional Information 1: a65c
Additional Information 2: a65c2884b2d8aca525c1cbb50e388db9
Additional Information 3: 396e
Additional Information 4: 396e9fe5e0fa1a3f9a73d5b2c9681128

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=190175

If the online privacy statement is not available, please read our privacy statement offline:
C:Windowssystem32en-USerofflps.txt

Solution

This is a known problem in the beta, pre-release, and the RTM versions of Exchange 2013.

There is now a fix from Microsoft here

You can also round the problem by accessing the Exchange Admin Center from a client (Windows running IE10 works fine). If you must access it on the server install the hofix or use Firefox

Related Articles, References, Credits, or External Links

NA

 

Exchange Mailbox Move Error”Property expression isn’t valid”

KB ID 0000238 

Problem

Seen when attempting to move a mailbox.

Error:
Property expression “username” isn’t valid. Valid values are: Strings that include ‘@’ where ‘@’ cannot be the last character

During the move.

When the move process has finished.

Note: If your error says

Property expression “username” isn’t valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ‘, *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.” Then click here.

Solution

This is caused because for that particular user there is no entry in the “domain” attribute on the user object.

1. Log onto a domain controller.

2. Start > Administrative tools> Active Directory Users and Computers.

3. Locate the user > Right click > Properties > Account Tab.

4. Put the domain name in the domain section. (use the drop down).

5. Now when you try and move the mailbox you will see this error instead.

Error:
The queue in ‘Mailbox Database xxxxxxxx’ database already contains a move request for {username}. While AD reports the mailbox as not being moved. It is possible that someone created the move request recently……..{text removed}…If you believe this to be an abandoned move request you can remove it by running ‘Remove-Move-Request -MoveRequestQueue ‘Mailbox Database xxxxxxx -MailboxGuid xxxxx-xxxxx-xxxxx-xx-xxx

6. Press CTRL+C to copy all that to the clipboard.

7. Open Notepad > Press CTRL+V to paste the text in.

8. Locate the command its asking you to run.

9. Launch the Exchange Management Shell > Paste in the command.

10. Now when you try and move the mailbox it should be OK.

 

Related Articles, References, Credits, or External Links

NA

Exchange 2007 / 2010 change the SMTP Banner

KB ID 0000327

Problem

If you want to shield the outside world from seeing what mail platform you are running, or even if you just want to deter the casual script kiddy who is trying to remote fingerprint a massive range of IP addresses. Changing the SMTP response banner is quite simple to do.

Out of the box we know we are running a Microsoft mail platform

Solution

1. Open Exchange System Manager and find the name of your “Receive Connector” (Server Configuration > Hub Transport > Receive Connectors).

2.Open the “Exchange Management Shell” and issue the following powershell command,

[box]Set-ReceiveConnector “name of the connector” -Banner “220 The text you want to display”[/box]

3. Then your banner should be changed (you don’t need to restart anything).

Changing the SMTP Banner for Exchange 2000 / 2003

1. Drop to command line and issue the following commands,

[box]

cd c:inetpubadminscripts
cscript adsutil.vbs set smtpsvc/vsi number/connectresponse “220 The text you want to display”

[box]

Note: c:inetpubadminscriptsadsutil path may be different in your Exchange server. And “vsi number” is the number of your SMTP virtual server, this is nearly always 1, check in your Exchange System Management console to make sure.

How to locate your VSI Number

2. Then restart the SMTP service.

Related Articles, References, Credits, or External Links

NA

Is Exchange 2010 Supported on VMware?

KB ID 0000333 

Problem

At time of writing (30/09/10) it seems I cant get a definitive answer! My colleague tried to log a third line support call with Microsoft this week, as soon as they found out that Exchange 2010 was running in a VMware environment, they (literally) hung up on him.

Solution

Well Microsoft’s own documentation says it IS

Reference:

Fair enough Exchange 2010 is supported on a “Third party Hypervisor ONLY if its been validated in the “Windows Server Virtualization Validation Program“”.

Lets check that then,

Reference:

Quote ” Products that have passed the SVVP requirements for Windows Server 2008 R2 are considered supported on Windows Server 2008 and Windows Server 2003 SP2 and later Service Packs, both x86 (32-bit), and x64 (64-bit).”

And The platform it was running on IS listed (ESXi 4.0 U1).

When presented with this evidence the response was “We will try and fix it on a “Best Endeavour” basis” and the problem (which had nothing to do with VMware, it was actually Microsoft Threat Management Gateway that caused the problem!) was resolved.

Sorry Microsoft that is just not good enough! My company pay handsomely for their gold partnership status, and we expect to get third line support on the products we sell. The product is either supported or it is NOT, don’t publish that it is, then use the fact that is running on third party virtualisation to get the problem off your support call queue. Because somewhere there is an Engineer/Consultant who has persuaded THEIR client to part with money to buy YOUR product.

I openly invite Microsoft – Third Line Exchange Support, The Exchange Development team and anyone else to respond to me. I will publish any pertinent response.

Related Articles, References, Credits, or External Links

Technet Exchange 2010 Requirements Windows Server Virtualization Validation Program VMware Platforms Supported and passed SVVP