Exchange Server Release dates

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
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
Microsoft Exchange Server 2010	14.0.639.21	11/9/2009
Microsoft Exchange Server 2010 SP1	14.1.218.15	8/24/2010
Microsoft Exchange Server 2010 SP2	14.2.247.5	12/4/2011

Exchange Server 2007 Service Pack 1

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	KB945684
Update Rollup 2 for Exchange Server 2007 Service Pack 1	8.1.278.2	5/8/2008	KB948016
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 Server 2007 Service Pack 2

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
Update Rollup 5 for Exchange Server 2007 Service Pack 2	8.2.305.3	12/7/2010	KB2407132

Exchange Server 2007 Service Pack 3

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	KB2492691
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	KB2509911
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

Exchange Server 2010

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	KB2407113

Exchange Server 2010 Service Pack 1

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	KB2492690
Update Rollup 3-v3 for Exchange Server 2010 SP1	14.1.289.7	4/1/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

Exchange Server 2010 Service Pack 2

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

]]> http://dusk1911.wordpress.com/2012/02/23/exchange-server-and-update-rollups-build-numbers/feed/ 0 dusk1911 clip_image001 clip_image001[1] clip_image001[2] clip_image001[3] clip_image001[4] clip_image001[5] clip_image001[6] clip_image001[7] clip_image001[8] clip_image001[9] clip_image001[10] clip_image001[11] clip_image001[12] clip_image001[13] clip_image001[14] clip_image001[15] clip_image001[16] clip_image001[17] clip_image001[18] clip_image001[19] clip_image001[20] clip_image001[21] clip_image001[22] clip_image001[23] clip_image001[24] clip_image001[25] clip_image001[26] clip_image001[27] clip_image001[28] clip_image001[29] clip_image001[30] clip_image001[31] clip_image001[32] clip_image001[33] clip_image001[34] clip_image001[35] http://dusk1911.wordpress.com/2012/02/19/scom-2007-r2-ports-requirments/ http://dusk1911.wordpress.com/2012/02/19/scom-2007-r2-ports-requirments/#comments Sun, 19 Feb 2012 07:30:00 +0000 Hany George https://dusk1911.wordpress.com/?p=344 ]]> The following table shows Operations Manager 2007 component interaction across a firewall, including information about the ports used for communication between the components, which direction to open the inbound port, and whether the port number can be changed.

Source

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

This was taken and modified from the PKI Blog

PST Capture is used to discover and import Outlook Personal Folder (.pst) File Format files into Exchange Server and Exchange Online. PST Capture helps an organization that wishes to gain more control over their email data repositories by placing them into Exchange. By optionally installing PST Capture Agents on target machines, administrators can determine where .pst files are located and who their file owner is via the PST Capture Console. Administrators can import .pst files via Import Lists to Exchange Server or Exchange Online. Data can be directly imported into the primary mailbox or associated archive mailbox.

Check out this blog article describing the tool: http://blogs.technet.com/b/exchange/archive/2012/01/30/pst-time-to-walk-the-plank.aspx

And the download location: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=28767

Even if you don’t plan on importing the .PST files into Exchange, it can be very useful to determine how many .PST files you have and where they are located.

You Can use the below to manually create the Certificate request to be used in a HW or SW Reverse proxy

Open Certificate MMC

Expand Personal > Certificates

Right – Click Certificates then All Tasks then Advanced Operations Then Create Custom Request

Select Next

Select Proceed without enrollment policy

Select No template legacy Key

Select Properties

Enter a friendly name

On the Subject tab enter the Common Name and Alternative names

On the extensions tab under Key Usage choose Digital Signature and Key encipherment

Under extended key usage choose Server Authentication and Client Authentication

Under the private key tab under key options choose key size and select 2048 and select private key exportable

Under Key type choose Exchange and ensure that the key size above is set to 2048

Select OK, Choose path to save and provide the CSR to a Public CA and then import into the Personal store.

A full list of the options and uses can be found here

http://technet.microsoft.com/en-us/library/bb936621(office.12).aspx

So the first thing that comes in mind are FW ports.Normally you need to double check the TCP/UDP 50,000-59,999 Range as well as the UDP 3478. Well after looking into it the ports were open and Edge was listening on them too.

Now the issue was only with the media, the signaling was fine, So when the External User calls the internal one, the called would get a notification, but when he accepts the call it disconnects.

The General idea of connection is that during the SIP negotiation and Especially the SESSION IN PROGRESS part in the SIPSTACK log, both clients would be offered the possible means of communications in the VIA field, So if you look closely You find the means to be BOTH Clients directly to each other or through an assigned ports on the edge.

Now running a SIPSTACK log on the Front End is saw the following error

ms-client-diagnostics: 23; reason=”Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote”;CallerMediaDebug=”audio:ICEWarn=0x80012b,

After checking all ports in all directions it was still not working. So I ran a trace on the Internal Interface of the Edge and saw the internal client connecting successfully to the Assigned Port that I got from Monitoring the SIPSTACK.

What was interesting is the External Interface. When I ran the trace on the External Interface I would see the Edge Denying the connection to the client on the specified port.

Now the Edge would behave this way if the client was not authenticating to it properly, So ahead to the UCCP Logs on the client side I went which are located under %Username%\Tracing , But how would the client know where to authenticate ?

Easy when the client signs in, it receives the configuration. and we are specifically looking for the MRAS that we have configured and can be found in Lync Control Panel –> Topology –> Edge Server –> EdgeServer

Now you would ask me, how did the client know how to get there, Remember the SESSION IN PROGRESS Negotiation ?

Looking at the logs I searched for the FQDN I got from the External MRAS FQDN in the previous screen

Bingo, here is the issue. The client doesn’t know where is the AV.domain.com record. SO It means that the DNS record AV.domain.com is missing from Either their local DNS or the external one.

It was actually missing on both, So after creating this record both internally and externally to point to the NATed public IP address of the AV Edge. All Started working perfectly fine.

So in a nutshell,

If you are facing an issue with AV Not working externally check the following

1- PORTS (This is normally the issue)

2- DNS Records

3- Certificates and trusts

Hope this helps

Well lets say your Primary Domain Controller (PDC) fails, then you move the FSMO roles to another server, and THEN you forget to set the NTP for the new DC.

Well luckily we have a way to automate that and its using the GPO and its WMI filtering capabilities

To do this we need to start by creating the filter

so in the Group Policy Management Console, Expand WMI Filters

Then Create NEW then add

Select * from Win32_ComputerSystem where DomainRole = 5

this will query the DCs for whomever is the holder of the PDC role

These are all the roles you can query

Value
Meaning
0 Standalone Workstation
1 Member Workstation
2 Standalone Server
3 Member Server
4 Backup Domain Controller
5 Primary Domain Controller

Click save

Create a GPO and Link it to the Domain Controllers Container in AD and make sure you select your WMI Filter you created earlier

Then Configure the setting as below

Once you are done, you should never think or worry about forgetting this option EVER again

But given that we are publishing through UAG and due to the statement in TechNet

When creating trunks and publishing applications, using non-standard ports is not supported; servers must listen on port 80 for HTTP and port 443 for HTTPS.

From here http://technet.microsoft.com/en-us/library/dd772157.aspx

The SP1 is designed to fix that. Due to the fact that Web services are published through port 4443

From Others I see that the Dialin and Meet publishes fine but Web Services like group expansion and Address book doesn’t work.

So SP1 your UAG and have this fixed

SP1 can be found here

http://www.microsoft.com/download/en/details.aspx?id=27604

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1" -PropertyType dword