Jump to content

Recommended Posts

Posted (edited)

I think I will wait a week or two before updating (just in case there are any issues). :)

 

Release Notes / What's New / Exchange Team Blog

 

A word of caution!. It seems that Service Pack 3 will also update the database schema of your databases. Once a database schema has been updated to SP3 you can no longer mount them on a pre-SP3 Mailbox Server. This means that you have to be particularly careful when updating Mailbox server that are part of a Database Availability Group! (Source)

 

@DrCheese. Now we just have to wait until Exchange Server 2013 CU1 is released. :(

 

Note. Exchange 2010 SP3 allows Exchange 2010 servers to coexist with Exchange 2013 CU1, which is also scheduled to be released in Q1 2013. Customers can test and validate this update in a representative lab environment prior to rolling out in their production environments as an important coexistence preparatory step before introducing Exchange Server 2013 CU1. (Source)
Edited by Arthur
Posted

Wow, it'd be great if they didn't start referring to it as sp2 half way through.

 

I know MS are a pretty small company, so can't afford a proof reader or anything....

  • Thanks 1
Posted

Hopefully this will let me install the EMC on windows 8 / 2012 Server.

 

Have no plans to move to 2013 Exchange for a long while, its horrible IMO, but the above I'm looking forward to.

Posted

outlook, outlook anywhere and activesync are working fine but OWA is messed up.

 

Ive reset the IIS dirs, can get to the login page, but then it just goes to /owa/auth.owa and no further ..

 

Anyone else testing SP3 yet?

Posted (edited)
outlook, outlook anywhere and activesync are working fine but OWA is messed up.

 

Ive reset the IIS dirs, can get to the login page, but then it just goes to /owa/auth.owa and no further ..

 

Anyone else testing SP3 yet?

 

Planning on the next move being to 2013 which I hear you have had bad experiences with too. Sorry for going off topic but would be interested in the faults that would cause you to persist with 2010, I know the migration stuff requires SP3 and 2013 (something not released yet). Currently running SP2 and updates as I usually hold back for a while on the major ones due to this very kind of situation.

 

We don't have a test environment so stuff has to work, or at least be fixable in production.

Edited by SYNACK
Posted

No bad experiences with 2013 per se, it installed fine on a test domain, I just don't like the OWA, the fact that the management console is now web based, etc. Have you seen/used it?

 

I wont be putting SP3 on my live environment for quite a while for sure, just testing it in one of the development domains.

Posted
No bad experiences with 2013 per se, it installed fine on a test domain, I just don't like the OWA, the fact that the management console is now web based, etc. Have you seen/used it?

 

I wont be putting SP3 on my live environment for quite a while for sure, just testing it in one of the development domains.

 

Haven't messed with it yet. TBH they have managed to make the console so slow and limited in Exchange 2010 that making it web based is not that much of a downgrade. Their control systems have been getting worse lately in their quest to make people use powershell as they have destroyed the GUIs.

Posted
Right think i figured this out. The Microsoft Exchange Forms Based Authentication service wasn't starting automatically. Ive started it and seem to be able to get OWA Working as expected. It didnt survive reboot so Ive set it to Automatic Delayed start and it seems to work OK.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...