Posts Tagged ‘schema’

The Exchange Team is pleased to announce that in the first half of calendar year 2013 we will be releasing Exchange Server 2010 Service Pack 3 (SP3) to our customers. With SP3, the following new features and capabilities will be included:

Coexistence with Exchange 2013: Customers that want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.

Support for Windows Server 2012: With Service Pack 3, you will have the ability to install and deploy Exchange Server 2010 on machines running Windows Server 2012.

Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema. We are communicating the required changes ahead of the release date in order to assist our customers with planning their upgrade path ahead of time.

We hope these announcements come as welcome news to you. It is our custom to provide ongoing improvements to features, functionality and security of Exchange Server, based largely on customer feedback, and to provide continual innovation on an already great messaging product. We look forward to receiving your comments and announcing more detailed information as we continue to develop the features that will be included in SP3.

Kevin Allison
General Manager
Exchange Customer Experience

(Source:  EHLO Blog)

If you want to figure out the Exchange Schema version Microsoft offers an updated TechNet Article of all Exchange Schema versions and the different methods to find out hte version:

Exchange Schema Versions – Common Questions & Answers

Cheers,

Chris

Hi,

to locate the server responsible for a FSMO role open ADSI-Edit. The responsible attribute is in every case:

fSMORoleOwner

PDC-Emulator role
Naming context: DefaultNamingContext
Path: DC=DOMAIN,DC=LOCAL
(Right-click – properties -> fSMORoleOwner)

RID Master role
Naming context: DefaultNamingContext
DC=DOMAIN,DC=LOCAL,CN=System,CN=Rid Manager$
(Right-click – properties)

Schema Master role
Naming context: Schema
DC=DOMAIN,DC=LOCAL
(Right-click – properties -> fSMORoleOwner)

Infrastructure Master role
Naming context: DefaultNamingContext
DC=DOMAIN,DC=LOCAL,CN=Infrastructure
(Right-click – properties -> fSMORoleOwner)

Domain Naming Master role
Naming context: Configuration
CN=Configuration,DC=DOMAIN,DC=LOCAL,CN=Partitions
(Right-click – properties -> fSMORoleOwner)

Cheers,

Chris

Yesterday I ran into a problem which was often discussed before by my colleagues and me.

I wanted to prepare the AD schema update before installing Exchange 2010. The “setup /pad” and “setup /ps” commands ran without any errors so I started to install Exchange 2010 (SP2).

The Installation itself ran without any errors, too. After rebooting the freshly installed Exchange 2010 server I wanted to opend the EMC and the EMS – and got one of these annoying WinRM management startup failures.

So I did it as recommended by MS and used the articles provided by TechNet and EHLO Team Blog and finally used the Exchange Management Troubleshooter (EMTShooter) without any hint or solution – the EMTShooter only detected an unknown error.

I called my colleague Stephan H.  (A big thank you, Stephan, for the memory of this topic) and he put me on the right track. A virus scanner was installed and activated on the schema master. Several times he had this issue: The schema update seemed to run properly but after installing Exchange 2010 strange errors occured.

The solution was very easy. I deactivated the virus scanner on the schema master and rerun Exchange 2010’s “setup /ps”. After finishing the PrepareSchema I rebooted the Exchange 2010 server and everything worked fine. In this case the AntiVirus software blocked the “evil” remote PowerShell.

Cheers,

Chris