Skip to content
October 2, 2015 / Don

Exchange Server build numbers

Product name

Release date

Build number

Exchange Server 2016 RTM  (2013 SP1)

2015-Oct-01

15.01.0225.042

Exchange Server 2016 Preview (2013 SP1 Beta)

2015-Jul-22

15.01.0225.016

Exchange Server 2013 CU10

2015-Sep-15

15.00.1130.007

Exchange Server 2013 CU9

2015-Jun-17

15.00.1104.005

Exchange Server 2013 CU8

2015-Mar-17

15.00.1076.009

Exchange Server 2013 CU7

2014-Dec-09

15.00.1044.025

Exchange Server 2013 CU6

2014-Aug-26

15.00.0995.029

Exchange Server 2013 CU5

2014-May-27

15.00.0913.022

Exchange Server 2013 SP1

2014-Feb-25

15.00.0847.032

Exchange Server 2013 CU3

2013-Nov-25

15.00.0775.038

Exchange Server 2013 CU2

2013-Jul-09

15.00.0712.024

Exchange Server 2013 CU1

2013-Apr-02

15.00.0620.029

Exchange Server 2013 RTM

2012-Dec-03

15.00.0516.032

Update Rollup 11 for Exchange Server 2010 SP3

2015-Sep-15

14.03.0266.002

Update Rollup 10 for Exchange Server 2010 SP3

2015-Jun-17

14.03.0248.002

Update Rollup 9 for Exchange Server 2010 SP3

2015-Mar-17

14.03.0235.001

Update Rollup 8v2 for Exchange Server 2010 SP3

2014-Dec-12

14.03.0224.002

Update Rollup 8v1 for Exchange Server 2010 SP3 (recalled)

2014-Dec-09

14.03.0224.001

Update Rollup 7 for Exchange Server 2010 SP3

2014-Aug-26

14.03.0210.002

Update Rollup 6 for Exchange Server 2010 SP3

2014-May-27

14.03.0195.001

Update Rollup 5 for Exchange Server 2010 SP3

2014-Feb-24

14.03.0181.006

Update Rollup 4 for Exchange Server 2010 SP3

2013-Dec-09

14.03.0174.001

Update Rollup 3 for Exchange Server 2010 SP3

2013-Nov-25

14.03.0169.001

Update Rollup 2 for Exchange Server 2010 SP3

2013-Aug-08

14.03.0158.001

Update Rollup 1 for Exchange Server 2010 SP3

2013-May-29

14.03.0146.000

Exchange Server 2010 SP3

2013-Feb-12

14.03.0123.004

Update Rollup 8 for Exchange Server 2010 SP2

2013-Dec-09

14.02.0390.003

Update Rollup 7 for Exchange Server 2010 SP2

2013-Aug-03

14.02.0375.000

Update Rollup 6 for Exchange Server 2010 SP2

2013-Feb-12

14.02.0342.003

Update Rollup 5v2 for Exchange Server 2010 SP2

2012-Dec-10

14.02.0328.010

Update Rollup 5 for Exchange Server 2010 SP2

2012-Nov-13

14.03.0328.005

Update Rollup 4v2 for Exchange Server 2010 SP2

2012-Oct-09

14.02.0318.004

Update Rollup 4 for Exchange Server 2010 SP2

2012-Aug-13

14.02.0318.002

Update Rollup 3 for Exchange Server 2010 SP2

2012-May-29

14.02.0309.002

Update Rollup 2 for Exchange Server 2010 SP2

2012-Apr-16

14.02.0298.004

Update Rollup 1 for Exchange Server 2010 SP2

2012-Feb-13

14.02.0283.003

Exchange Server 2010 SP2

2011-Dec-04

14.2.247.5

Update Rollup 8 for Exchange Server 2010 SP1

2012-Dec-10

14.01.0438.000

Update Rollup 7 v3 for Exchange Server 2010 SP1

2012-Nov-13

14.01.0421.003

Update Rollup 7 v2 for Exchange Server 2010 SP1

2012-Oct-10

14.01.0421.002

Update Rollup 7 for Exchange Server 2010 SP1

2012-Aug-08

14.01.0421.000

Update Rollup 6 for Exchange Server 2010 SP1

2011-Oct-27

14.01.0355.002

Update Rollup 5 for Exchange Server 2010 SP1

2011-Aug-23

14.1.339.1

Update Rollup 4 for Exchange Server 2010 SP1

2011-Jul-27

14.1.323.6

Update Rollup 3 for Exchange Server 2010 SP1

2011-Apr-06

14.01.0289.007

Update Rollup 2 for Exchange Server 2010 SP1

2010-Dec-09

14.01.0270.001

Update Rollup 1 for Exchange Server 2010 SP1

2010-Oct-04

14.1.255.2

Exchange Server 2010 SP1

2010-Aug-23

14.01.0218.015

Update Rollup 5 for Exchange Server 2010

2010-Dec-13

14.0.726.0

Update Rollup 4 for Exchange Server 2010

2010-Jun-10

14.0.702.1

Update Rollup 3 for Exchange Server 2010

2010-Apr-13

14.0.694.0

Update Rollup 2 for Exchange Server 2010

2010-Mar-04

14.0.689.0

Update Rollup 1 for Exchange Server 2010

2009-Dec-09

14.0.682.1

Exchange Server 2010

2009-Nov-09

14.00.0639.021

Update Rollup 17 for Exchange Server 2007 SP3

2015-Jun-17

08.03.0417.001

Update Rollup 16 for Exchange Server 2007 SP3

2015-Mar-17

08.03.0406.000

Update Rollup 15 for Exchange Server 2007 SP3

2014-Dec-09

08.03.0389.002

Update Rollup 14 for Exchange Server 2007 SP3

2014-Aug-26

08.03.0379.002

Update Rollup 13 for Exchange Server 2007 SP3

2014-Feb-24

08.03.0348.002

Update Rollup 12 for Exchange Server 2007 SP3

2013-Dec-09

08.03.0342.004

Update Rollup 11 for Exchange Server 2007 SP3

2013-Aug-13

08.03.0327.001

Update Rollup 10 for Exchange Server 2007 SP3

2013-Feb-11

08.03.0298.003

Update Rollup 9 for Exchange Server 2007 SP3

2012-Dec-10

08.03.0297.002

Update Rollup 8-v3 for Exchange Server 2007 SP3

2012-Nov-13

08.03.0279.006

Update Rollup 8-v2 for Exchange Server 2007 SP3

2012-Oct-09

08.03.0279.005

Update Rollup 8 for Exchange Server 2007 SP3

2012-Aug-13

08.03.0279.003

Update Rollup 7 for Exchange Server 2007 SP3

2012-Apr-16

08.03.0264.000

Update Rollup 6 for Exchange Server 2007 SP3

2012-Jan-26

8.03.0245.002

Update Rollup 5 for Exchange Server 2007 SP3

2011-Sep-21

8.03.0213.001

Update Rollup 4 for Exchange Server 2007 SP3

2011-May-28

8.03.0192.001

Update Rollup 3-v2 for Exchange Server 2007 SP3

2011-Mar-30

8.03.0159.002

Update Rollup 2 for Exchange Server 2007 SP3

2010-Dec-10

8.03.0137.003

Update Rollup 1 for Exchange Server 2007 SP3

2010-Sep-09

8.03.0106.002

Exchange Server 2007 SP3

2010-Jun-07

8.03.0083.006

Update Rollup 5 for Exchange Server 2007 SP2

2010-Dec-07

8.2.305.3

Update Rollup 4 for Exchange Server 2007 SP2

2010-Apr-09

8.2.254.0

Update Rollup 3 for Exchange Server 2007 SP2

2010-Mar-17

8.2.247.2

Update Rollup 2 for Exchange Server 2007 SP2

2010-Jan-22

8.2.234.1

Update Rollup 1 for Exchange Server 2007 SP2

2009-Nov-19

8.2.217.3

Exchange Server 2007 SP2

2009-Aug-24

8.02.0176.002

Update Rollup 10 for Exchange Server 2007 SP1

2010-Apr-13

8.1.436.0

Update Rollup 9 for Exchange Server 2007 SP1

2009-Jul-16

8.1.393.1

Update Rollup 8 for Exchange Server 2007 SP1

2009-May-19

8.1.375.2

Update Rollup 7 for Exchange Server 2007 SP1

2009-Mar-18

8.1.359.2

Update Rollup 6 for Exchange Server 2007 SP1

2009-Feb-10

8.1.340.1

Update Rollup 5 for Exchange Server 2007 SP1

2008-Nov-20

8.1.336.1

Update Rollup 4 for Exchange Server 2007 SP1

2008-Oct-07

8.1.311.3

Update Rollup 3 for Exchange Server 2007 SP1

2008-Jul-08

8.1.291.2

Update Rollup 2 for Exchange Server 2007 SP1

2008-May-09

8.1.278.2

Update Rollup 1 for Exchange Server 2007 SP1

2008-Feb-28

8.1.263.1

Exchange Server 2007 SP1

2007-Nov-29

8.01.0240.006

Update Rollup 7 for Exchange Server 2007

2008-Jul-08

8.0.813.0

Update Rollup 6 for Exchange Server 2007

2008-Feb-21

8.0.783.2

Update Rollup 5 for Exchange Server 2007

2007-Oct-25

8.0.754.0

Update Rollup 4 for Exchange Server 2007

2007-Aug-23

8.0.744.0

Update Rollup 3 for Exchange Server 2007

2007-Jun-28

8.0.730.1

Update Rollup 2 for Exchange Server 2007

2007-May-08

8.0.711.2

Update Rollup 1 for Exchange Server 2007

2007-Apr-17

8.0.708.3

Exchange Server 2007

2007-Mar-08

8.0.685.25

Exchange Server 2003 post- SP2

2008-Aug-01

6.5.7654.4

Exchange Server 2003 post-SP2

2008-Mar-01

6.5.7653.33

Exchange Server 2003 SP2

2005-Oct-19

6.5.7683

Exchange Server 2003 SP1

2004-May-25

6.5.7226

Exchange Server 2003

2003-Sep-28

6.5.6944

Exchange 2000 Server build numbers

Product name

Release date

Build number

Exchange 2000 Server post-SP3

August 2008

6.0.6620.7

Exchange 2000 Server post-SP3

March 2008

6.0.6620.5

Exchange 2000 Server post-SP3

August 2004

6.0.6603

Exchange 2000 Server post-SP3

April 2004

6.0.6556

Exchange 2000 Server post-SP3

September 2003

6.0.6487

Exchange 2000 Server SP3

July 18, 2002

6.0.6249

Exchange 2000 Server SP2

November 29, 2001

6.0.5762

Exchange 2000 Server SP1

June 21, 2001

6.0.4712

Exchange 2000 Server

November 29, 2000

6.0.4417

Exchange Server 5.5 build numbers

Product name

Release date

Build number

Exchange Server version 5.5 SP4

November 1, 2000

5.5.2653

Exchange Server version 5.5 SP3

September 9, 1999

5.5.2650

Exchange Server version 5.5 SP2

December 23, 1998

5.5.2448

Exchange Server version 5.5 SP1

August 5, 1998

5.5.2232

Exchange Server version 5.5

February 3, 1998

5.5.1960

Exchange Server 5.0 build numbers

Product name

Release date

Build number

Exchange Server 5.0 SP2

February 19, 1998

5.0.1460

Exchange Server 5.0 SP1

June 18, 1997

5.0.1458

Exchange Server 5.0

May 23, 1997

5.0.1457

Exchange Server 4.0 build numbers

Product name

Release date

Build number

Exchange Server 4.0 SP5

May5, 1998

4.0.996

Exchange Server 4.0 SP4

March 28, 1997

4.0.995

Exchange Server 4.0 SP3

October 29, 1996

4.0.994

Exchange Server 4.0 SP2

July 19, 1996

4.0.993

Exchange Server 4.0 SP1

May 1, 1996

4.0.838

Exchange Server 4.0 Standard Edition

June 11, 1996

4.0.837

https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx

Advertisements
March 3, 2014 / Don

Quest Migration Manager doesn’t see the Network

From within Quest Migration Manager I was getting the following error

“the list of servers for this workgroup is not currently available”

Wins was set up and working.

But when I would turn on Network Sharing, it would just turn off again.

To make it work I had to enable the 2 following services.

  • SSDP Discovery
  • UPnP Device Host

Once these were set I could turn on Network Discovery and Quest Migration Manager was happy.

image

March 2, 2014 / Don

Creating Users from a Spreadsheet with New-ADUser

Working in my lab, I needed a script to create some AD users. Here is what I came up with.

 

 

##################### Start of script ########################
#########################################################
#########################################################
#########################################################
### Written by Don Wilwol
###
### 3-2014
### atthedatacenter.wordpress.com
###
###Creates users from a CSV file
###Just add firstname, lastname and (important) header in the input file
###
###It logs to the log file path
###It sets the SamAccountName to first initial lastname
##It sets the UPN to the SamAccountName@domain
###It sets a primary Email address as the UPN
###It sets the SIP address as the UPN
###It surpresses the errors in the shell
###to see the errors rem out $ErrorActionPreference = "SilentlyContinue"
###Creation of a user with appended suffix is logged
###The script defaults to a password of P@ssw0rd" but the line can be changed
###Change the line with this on for "first initial, last initial, !12345"
# -AccountPassword(Convertto-Securestring -AsPlaintext ($_.Firstname.SubString(0,1) + $_.lastname.SubString(0,1) + "!12345") -Force)`

$date = (get-date).toString(‘yyyy-MM-dd’)

 

##Set input file path
$CSVPath ="c:\users.csv"

##Set YOUR domain name
$DomainN = "student.Source.lab"

##Set the OU Path you would like the users created
$Path = "OU=TestUsers,DC=Source,DC=Lab"

### Set the description for this group of users
$Description = "Student Account for Some Year, Maybe 2019"

###Set the log file path
$LogFile = "C:\$date-CreateUserlogfile.txt"

#########################################################
#########################################################
#########################################################

$ErrorActionPreference = "SilentlyContinue"

 

import-csv $CSVPath | foreach {

$SamAccountname = ($_.Firstname.SubString(0,1) + $_.lastname)
If(get-ADUser $SamAccountname) {$SamAccountname = $SamAccountname + "2";write-output "**Secondary SamAccountName**  $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "3";write-output "**3rd SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "4";write-output "**4th SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "5";write-output "**5th SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "6";write-output "**6th SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "7";write-output "**7th SamAccountName** $SamAccountName" >> $LogFile}
if(get-ADUser $SamAccountname) {$SamAccountname = $_.Firstname.SubString(0,1) + $_.lastname + "8";write-output "**8th SamAccountName** $SamAccountName" >> $LogFile}

 

$error.clear()
$UPN = $SamAccountname + "@$DomainN"
$Dname = ($_.Firstname + " " + $_.lastname)
new-aduser -Path $Path `
-Name $Dname -GivenName $_.Firstname`
-Surname $_.Lastname`
-AccountPassword(Convertto-Securestring -AsPlaintext "P@ssw0rd" -Force)`
-enabled $true `
-EmailAddress $UPN `
-SamAccountname $SamAccountname  `
-Description $Description `
-DisplayName $Dname `
-ChangePasswordAtLogon $True
write-host   ("Creating User (" + $SamAccountname + ")  " + $_.Firstname + " " + $_.lastname)
write-output "" >> $LogFile
write-output ("Creating User (" + $SamAccountname + ")  " + $_.Firstname + " " + $_.lastname) $error >> $LogFile
write-output "" >> $LogFile 

Set-Aduser -Identity $SamAccountname -Add @{userPrincipalName = $UPN;`
proxyAddresses = "SMTP:$UPN","SIP;$UPN";`
}
}

##################### End of script ########################

 

The spreadsheet is a very simple format.

firstname,lastname

Joe,Somebody

Harry,Helper

Fred,Flinstone

February 12, 2014 / Don

An interesting ADFS Error

While installing Windows 2012 R2 Active Directory Federation Services, I had an interesting issue testing a Windows 2012 R2 AD FS installation.

 

image

 

The error, as stated above

  • Activity ID: 00000000-0000-0000-0d00-0080000000fb
  • Error Time:
  • Cookie: enabled
  • User agent string: Mozilla/5.0 (Windows NT 6.1; WOW64)
  • AppleWebLit/537.36 (KHTML, like Geckp)
  • Chrome/32.o.1700.76 Safari/537.36

 

The error, which happened during initial testing. It turned out to be a slight mis spelling of

https://fs.domaion.com/adfs/ls/IdpInitiatedSignon.aspx

We had something like

https://feds.tesc.edu.com/adfs/ls/idpInitiatedSignon.aspxII  (note the “i” instead of the “L”)

I would have expected a bad URL to return a page not found or similar, but it brought up a Nice AD FS page with this error on it. Go Figure!

 

Hope it helps.

November 11, 2013 / Don

Register a DAG IP (ipconfig /registerdns for DAG’S)

I ran into an issue recently where I needed to register the IP of a DAG. I discovered this wasn’t well documented and it took a while to figure out how to get it registered.

 

I first tried running ipconfig /registerdns on the primary active manager. To find the primary active manager you must run

 

get-databaseavailabilitygroup <name> -status | select name,primaryactivemanager

 

But that did not work. What does work is running,

cluster . res "Cluster Name" /registerdns

on any of the cluster nodes.

 

Also note:

The DAG will attempt to register on its own at some random time within 2 hours of midnight.

 

Hope it helps.

dw

November 30, 2012 / Don

Exchange 2013 Certificates in my lab

So here is the process for my Exchange 2013 lab certificate creation.

Select servers, certificates.

clip_image002

Select the plus sign to create a new certificate.

clip_image004

clip_image006

clip_image008

clip_image010

clip_image012

clip_image014

clip_image016

clip_image017

clip_image018

clip_image020

clip_image022

clip_image024

Now to the CA

clip_image026

clip_image028

Select the “Advanced Certificate Request” option

clip_image030

Now Select the “Submit a certificate request by using a base 64………….”

clip_image032

Copy and paste the request into the box.

clip_image034

clip_image036

Select “download certificate”, then select “Save

clip_image038

Save and copy to Exchange server (where you saved the pending request)

Complete pending request

clip_image040

clip_image042

clip_image044

clip_image046

Assign to services

clip_image047

 

Now go play some more with your new Exchange 2013 LAB.

November 27, 2012 / Don

Co-existence With Exchange 2013

As of this writing, co-existence with Exchange 2007 and Exchange 2013 and Exchange 2010 and Exchange 2013 will come later on.

http://technet.microsoft.com/en-us/library/aa996719.aspx

 

No co-exitence with Exchange 2003 is planned, so get to 2010 asap.

 

Right now, if you want to play around in your lab, you are somewhat limited. Remember no co-existence is supported at this time, but some work can be done if you’re just looking to learn.

 

Installing Exchange 2013 into a Exchange 2013 organization isn’t possible.

the installation stops with an Error that says “Exchange 2013 all exchange 2010 servers in the organization must have Exchange 2010 Service Pack 3 or later installed” and points to this.http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.e15e14CoexistenceMinMajorVersionrequirement.aspx

MustHave 2010 SP3 error

 

So no playing around for the Exchange 2010-2013 configurations until Exchange 2010 SP3 is released.

 

Installation into an Exchange 2007 org went as planned.

 

Note a warning stating no Exchange 2010 can be installed into the organization after the Exchange 2013 setup was complete.

 

A few notes on the installation. I installed with the Administrator account which had its mailbox on the Exchange 2007 server. This meant that I couldn’t open the Exchange 2013 ECP. To fix it, I created a user in AD with the appropriate permissions and ran the enable-mailbox command from the Exchange shell. I’m sure I could have also run the New-MoveRequest command and moved a mailbox as well.

November 12, 2012 / Don

Web mail Gibberish from 2003 to 2010 Exchange

I was migrating from Exchange 2003 to Exchange 2010. Email was configured to route through Exchange 2010 and out to the Internet if needed. If a user sent and email from the Web interface of Exchange 2003 to an outside internet recipient, the message looked like the following

䠼TML dir=ltr>䠼EAD>㰊META content="text/html; charset=unicode" http-equiv=Content-Type>㰊META name=GENERATOR content="MSHTML 8.00.6001.19328"㰾/HEAD>㰊BODY> 䐼IV㰾FONT color=#000000 size=2 face=Arial>OWA 2003 Gibberish Test㱴/FONT>⼼DIV>⼼BODY㰾/HTML>

 

Note the red was the actual message. If the same thing was sent to a recipient on Exchange 2010 the message appeared just fine.

 

The issue happened once a disclaimer was set up as a transport rule. So the disclaimer was causing the issue. Disable the transport rule, the issue goes away. Enable the rule, it comes back.

 

Cause:

This problem occurs because Outlook Web Access for Exchange 2003 sets an e-mail message to an incorrect character set. When the message is routed by the Exchange 2007 or 2010 server that has the Disclaimer rule enabled, the e-mail message is converted to incorrect HTML tagging based on the incorrect character set. Then, the message is corrupted by the incorrect tagging.

 

The fix?

A patch just for this issue. Once the patch was applied to all of the Exchange 2003 servers, all was well.

 

http://support.microsoft.com/kb/935489

 

hope it helps

dw

November 2, 2012 / Don

Troubleshooting OAB downloads.

Troubleshooting Offline Address Book downloads in Exchange/Outlook 2010

First thing, verify the OAB is being generated. On the Generating server you’ll have 2 directories.

D:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB\85c8d192-d03a-4558-996e-d90c4c907d04

And

D:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB\d6ec84a4-95a2-418b-ae44-dd1ce5a4ba35

Inside both you should have an oab.xml file and numerous .lbx files looking something like this

b533b414-1388-4862-ab89-e72cd8ef38e3-mac8411-15.lzx

clip_image002 

On the other Servers, you’ll only have D:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB\ directory.

If you restart the Microsoft Exchange File Distribution service, you should see the directory update with files from the current time.

This gets updated automatically according to your maintenance schedule once a day. You’ll want to make sure that’s happening.

If you’ve only got an oab.xml file, and the files will not replicate, try deleting the oab.xml and restart the service again.

Turn up logging –

Set-EventLogLevel -Identity "MSExchangeSA\OAL Generator" –Expert

Run update-offlineaddressbook and restart the Microsoft Exchange File Distribution service, then check the event logs

If the servers are replicating and you still can’t download. Here are a few things to ask yourself.

Is the Internal and external URLs set?

Run Get-OABvirtualdirectory to see what they are.

What servers are in the distribution list?

Get-OABvirtualdirectory will show that as well.

Are you using a load balancer for the URL?

This can be bypassed with a host file (be sure to bypass all URLs), or by setting the Internal URL back to the server name.

If you are using HTTPS are all names in the certificate?

Run test-autoconfigure from the outlook client.

Run www.testexchangeconnectivity.com and test autoconfigure.

Getting the wrong URL? Did you set sitescope and affinity? If you have multiple sites with exchange, you’ll need to configure it so your sites connect to the right server(s)

Set-ClientAccessServer -Identity "ServerName" -AutodiscoverServiceInternalURI "https://internalsitename/autodiscover/autodiscover.xml&quot; -AutodiscoverSiteScope "SiteName","SiteName2","SiteName3"

Set-ClientAccessServer -Identity "ServerName(in site2)" -AutodiscoverServiceInternalURI "https://internalsitename2/autodiscover/autodiscover.xml&quot; -AutodiscoverSiteScope "SiteName4","SiteName5","SiteName6"

So how is it different in Exchange 2013? Read for yourself.

http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx

 

And

 

http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx

October 8, 2012 / Don

Exchange 2013 Preview Install

Here is my experience Installing Exchange 2013 preview on Windows 2012 Server.

The first install was a flop. I’m not sure what went wrong, but I’ll post back if I figure it out.

This is an Exchange server with both CAS and MBX role installed.

Here is the article I followed.

http://technet.microsoft.com/en-US/library/bb691354(v=exchg.150).aspx

 

In Windows 2012 server virtual server, make sure the server window is in focus. Hit the windows key.

Windows-Q will search apps.

You’ll also probably want the enable Desktop Experience is under Features\User Interface and Infrastructure for the snipping tool.

And here are some help key strokes

Windows key = Ctrl+Esc

Settings (Winkey+I)

Charms (Winkey+C)

Search (Winkey+Q)

 

Install-WindowsFeature RSAT-ADDS

image

In powershell, run the following

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

 

image

 

now run

Shutdown -r

 

For Exchange 2013 Preview, you must also uninstall Microsoft Visual C++ 11 Beta Redistributable (x64). This must be done after you’ve installed UCMA, but before you run Exchange 2013 Preview Setup. To uninstall Microsoft Visual C++ 11 Beta Redistributable (x64), do the following:

Open Control Panel > Programs and Features.

Select Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 and then click Uninstall.

In Microsoft Visual C++ 11 Beta setup, click Uninstall.

When Microsoft Visual C++ 11 Beta is uninstalled, click Close.

 

After you’ve installed the operating system roles and features, install the following software in the order shown:

Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

Microsoft Office 2010 Filter Pack 64 bit

Microsoft Office 2010 Filter Pack SP1 64 bit

 

now run

Shutdown -r

 

http://technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx

From a Command Prompt run
setup /PrepareSchema or setup /ps

 

image

 

image

image

 

 

From a Command Prompt window, run the following command.
setup /PrepareAD [/OrganizationName:<organization name>] or setup /p [/on:<organization name>]

 

image

image

image

 

 

Run setup /PrepareDomain or setup /pd to prepare the local domain

Or

run setup /PrepareAllDomains

 

I only had one at this time so setup /pd worked just fine

 

image

image

 

So now let’s run setup

 

image

image

image

image

image

image

image

image

image

image

image

image

image

image

image

 

 

 

Now go to https:/localhost/ecp

 

image

 

image

 

 

But for some reason I can’t yet explain, this wouldn’t work. I’d get HTTP 500 errors every time I tried to open ECP.

 

The fix seemed to be going to the domain controller and making a user, and adding that user to the domain admins group.

 

Then I ran the enable-mailbox for that user. The it worked.

 

image

Then, as if I didn’t know better to start with, I added the user to the Exchange organizational management group. Then the Exchange tools popped up.

 

image

 

The reason: I had trouble with the first mailbox server so I just shut it off. That’s where the mailbox for the administrator was.

%d bloggers like this: