Archive for February, 2012


As you know Exchange 2010 SP2 Came with a requirement to update the schema,

Now quoting Michael’s Blog There are several very interesting items :

  1. The Mail-Recipient class has now gained the Company and Department attributes.
    This means that Groups (both security groups and distribution groups) and Contacts (mail contacts) can now be assigned values to the Company and Department attributes.
    From a technical perspective, the Mail-Recipient class is a system auxiliary class, for both the Group and Contact classes, and all attributes present in Mail-Recipient are available in them.

  2. The ms-Exch-Custom-Attributes class has gained 35 new custom attributes, from ms-Exch-Extension-Attribute-16 to ms-Exch-Extension-Attribute-45, and ms-Exch-Extension-Custom-Attribute-1 through ms-Exch-Extension-Custom-Attribute-5.
    This means that Contacts, Groups, Users, Public Folders, Dynamic Distribution Lists, and Recipient Policies all now have a huge number of new attributes that can be assigned arbitrary values by an organization. This is welcome news to organizations who are using many or most of the current custom attributes and are wary to extend the schema themselves.
    From a technical perspective, the ms-Exch-Custom-Attributes class is an auxiliary class for all the named classes above.

  3. Many new attributes and classes were added to provide support for Address Book Policies and to enhance access to various address lists, global address lists, and offline address lists maintained by Exchange.
    The master class is ms-Exch-Address-Book-Mailbox-Policy.

  4. There are several new attributes and one new class (ms-Exch-Coexistence-Relationship) that are probably designed to support the Hybrid Coexistence Wizard and to overall simplify the process of configuring hybrid coexistence with Exchange Online.

  5. There is a new class (ms-Exch-ActiveSync-Device-Autoblock-Threshold) and a number of new attributes that are within that class that appear to be designed to support automatic throttling of ActiveSync devices.

You can get a lot more detailes from the following link

Exchange Server Active Directory Schema Changes Reference, November 2011

Advertisements

You can use the following tables to determine which Exchange Version You have

 

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 clip_image001

Update Rollup 2 for Exchange Server 2007 Service Pack 1

8.1.278.2

5/8/2008

KB948016 clip_image001[1]

Update Rollup 3 for Exchange Server 2007 Service Pack 1

8.1.291.2

7/8/2008

KB949870 clip_image001[2]

Update Rollup 4 for Exchange Server 2007 Service Pack 1

8.1.311.3

10/7/2008

KB952580 clip_image001[3]

Update Rollup 5 for Exchange Server 2007 Service Pack 1

8.1.336.1

11/20/2008

KB953467 clip_image001[4]

Update Rollup 6 for Exchange Server 2007 Service Pack 1

8.1.340.1

2/10/2009

KB959241 clip_image001[5]

Update Rollup 7 for Exchange Server 2007 Service Pack 1

8.1.359.2

3/18/2009

KB960384 clip_image001[6]

Update Rollup 8 for Exchange Server 2007 Service Pack 1

8.1.375.2

5/19/2009

KB968012 clip_image001[7]

Update Rollup 9 for Exchange Server 2007 Service Pack 1

8.1.393.1

7/17/2009

KB970162 clip_image001[8]

Update Rollup 10 for Exchange Server 2007 Service Pack 1

8.1.436.0

4/9/2010

KB981407 clip_image001[9]


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 clip_image001[10]

Update Rollup 2 for Exchange Server 2007 Service Pack 2

8.2.234.1

1/22/2010

KB972076 clip_image001[11]

Update Rollup 3 for Exchange Server 2007 Service Pack 2

8.2.247.2

3/17/2010

KB979784 clip_image001[12]

Update Rollup 4 for Exchange Server 2007 Service Pack 2

8.2.254.0

4/9/2010

KB981383 clip_image001[13]

Update Rollup 5 for Exchange Server 2007 Service Pack 2

8.2.305.3

12/7/2010

KB2407132 clip_image001[14]

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 clip_image001[15]

Update Rollup 2 for Exchange Server 2007 Service Pack 3

8.3.137.3

12/10/2010

KB2407025 clip_image001[16]

Update Rollup 3 for Exchange Server 2007 Service Pack 3

8.3.159.0

3/2/2011

KB2492691 clip_image001[17]

Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3

8.3.159.2

3/30/2011

KB2530488 clip_image001[18]

Update Rollup 4 for Exchange Server 2007 Service Pack 3

8.3.192.1

7/7/2011

KB2509911 clip_image001[19]

Update Rollup 5 for Exchange Server 2007 Service Pack 3

8.3.213.1

9/21/2011

KB2602324 clip_image001[20]

Update Rollup 6 for Exchange Server 2007 Service Pack 3

8.3.245.2

1/25/2012

KB2608656 clip_image001[21]


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 clip_image001[22]

Update Rollup 2 for Exchange Server 2010

14.0.689.0

3/4/2010

KB979611 clip_image001[23]

Update Rollup 3 for Exchange Server 2010

14.0.694.0

4/9/2010

KB981401 clip_image001[24]

Update Rollup 4 for Exchange Server 2010

14.0.702.1

6/17/2010

KB982639 clip_image001[25]

Update Rollup 5 for Exchange Server 2010

14.0.726.0

12/13/2010

KB2407113 clip_image001[26]


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 clip_image001[27]

Update Rollup 2 for Exchange Server 2010 SP1

14.1.270.1

12/9/2010

KB2425179 clip_image001[28]

 

Update Rollup 3 for Exchange Server 2010 SP1

14.1.289.3

3/7/2011

KB2492690 clip_image001[29]

Update Rollup 3-v3 for Exchange Server 2010 SP1

14.1.289.7

4/1/2011

KB2529939 clip_image001[30]

Update Rollup 4 for Exchange Server 2010 SP1

14.1.323.1

6/22/2011

KB2509910 clip_image001[31]

Update Rollup 4-v2 for Exchange Server 2010 SP1

14.1.323.6

7/27/2011

KB2579150 clip_image001[32]

Update Rollup 5 for Exchange Server 2010 SP1

14.1.339.1

8/23/2011

KB2582113 clip_image001[33]

Update Rollup 6 for Exchange Server 2010 SP1

14.1.355.2

10/27/2011

KB2608646 clip_image001[34]

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 clip_image001[35]

SCOM 2007 R2 Ports Requirments

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.

Operations Manager 2007 SP1 Component A

Port Number and Direction

Operations Manager 2007 SP1 Component B

Configurable

Note

root management server

1433 —>

Operations Manager database

Yes (Setup)

 

management server

1433 —>

Operations Manager database

Yes (Setup)

 

management server

5723, 5724 —>

root management server

No

Port 5724 must be open to install this component and can be closed after this component has been installed.

gateway server

5723 —>

root management server

No

 

root management server

1433 —>

Reporting data warehouse

No

 

Reporting server

5723, 5724 —>

root management server

No

Port 5724 must be open to install this component and can be closed after this component has been installed.

Operations console

5724 —>

root management server

No

 

Connector framework source

51905 —>

root management server

No

 

Web console server

5724 —>

root management server

No

 

Web console browser

51908 —>

Web console server

Yes (IIS Admin)

Port 51908 is the default port used when selecting Windows Authentication. If you select Forms Authentication, you will need to install an SSL certificate and configure an available port for https functionality for the Operations Manager 2007 WebConsole Web site.

connected root management server (Local)

5724 —>

connected root management server (Connected)

No

 

Agent installed using MOMAgent.msi

5723 —>

root management server

Yes (Setup)

 

Agent installed using MOMAgent.msi

5723 —>

management server

Yes (Setup)

 

Agent installed using MOMAgent.msi

5723 —>

gateway server

Yes (Setup)

 

gateway server

5723 —>

management server

Yes (Setup)

 

Agent (Audit Collection Services forwarder)

51909 —>

management server Audit Collection Services collector

Yes (Registry)

 

Agentless Exception Monitoring data from client

51906 —>

management server Agentless Exception Monitoring file share

Yes (Client Monitoring Wizard)

 

Customer Experience Improvement Program data from client

51907 —>

management server (Customer Experience Improvement Program End) Point

Yes (Client Monitoring Wizard)

 

Operations console (reports)

80 —>

SQL Reporting Services

No

The Operations console uses Port 80 to connect to the SQL Reporting Services Web site.

Reporting server

1433 —>

Reporting data warehouse

Yes

 

management server (Audit Collection Services collector)

1433 —>

Audit Collection Services database

Yes

 

 

Source

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

Below is the Firewall ports requirements

 

Kerberos

464

Certificate Enrollment Web Services

Domain Controllers (DC)

Allow

Source Certificate Enrollment Web Services

         

Destination: DC

         

Service: Kerberos (network port tcp/464)

LDAP

389

Certificate Enrollment Web Services

Domain Controllers (DC)

Allow

Source Certificate Enrollment Web Services

         

Destination: DC

         

Service: LDAP (network port tcp/389)

LDAP

636

Certificate Enrollment Web Services

Domain Controllers (DC)

Allow

Source Certificate Enrollment Web Services

         

Destination: DC

         

Service: LDAP (network port tcp/636)

DCOM/RPC

1024-65500

Certificate Enrollment Web Services

CA

Allow

Please see for details on RPC/DCOM configuration: http://support.microsoft.com/kb/154596/en-us

HTTPS

443

All clients requesting certs

Certificate Enrollment Web Services

Allow

Source: Windows 7 client

         

Destination:

         

Service: https (network port tcp/443)

         

Certificate Enrollment Web Services

Bottom of Form

RPC

135

All clients requesting certs

Certificate Enrollment Web Services

Allow

Source: Windows 7 client

         

Destination: CA

         

Service: RPC

         

Done in Both Directions

Bottom of Form

 

This was taken and modified from the PKI Blog