Exchange 2010 Rollups

Nikumba

Nikumba

Nikumba

Soldato
Joined
4 Dec 2002
Posts
4,061
Location
Bourne, Lincs
I am hoping to get away with out doing some work, but can you apply a roll up to one exchange server in your organisation or do you need to do them all?

We have 4 mailbox servers, plus Edge, Hub, Cas all on their own servers.

We need the roll-up to fix an issues with OWA we are having, so can I just put it on the CAS server or does it need to go on all of them?

Cheers

Kimbie
 
We had to rollup our CAS server to migrate from Exchange 2010 in one AD forest to a hybrid 2013/365 in another forest.

I only rolled up the CAS and one mailbox server during the process.

Note though that you won't be able to connect to the rolled up servers using the non-rolled up consoles on the other exchange servers. This doesn't affect the exchange services though, just management.
 
Ah ok, so the CAS can goto Rollup 7, leave the rest on SP1 without the rollup and if we need to manage the CAS we have to do it on the CAS rather than from another server?

Second stage will be to move upto SP3, will it be better to get everyone on Rollup 7 then upgrade to SP3?
 
I wouldn't personally want to run on different versions of Exchange between servers for long, much better to update them all within a reasonable time of each other. In fact if you are on SP1 and on standard Enterprise I would roll that up to SP3 if you can and skip SP1 RU7 altogether.

MS dropped proper support for SP1 now I think as well.
 
If going to SP3 I would do RU2 at the same time as it contains a number of hotfixes for public folders (if you use them) as well as being able to delete certain types of emails, particularly those generated by 3rd party applications like RightFax who attach faxes as PDF's as Microsofts own meeting request/scheduler type emails.

Also remember SP3 changes both the AD schema and Database schema, once you have updated a DAG member and failed over any database to it, it can no longer fail back to any DAG member that has not been upgraded.
 
Thanks for the replies, well put the Rollup on and it did not fix the issue, so we are now looking at going to SP3 with RU2 at the same time, but trying to get a maintenance window outside of our usual monthly window is tricky.
 
ubern00b said:
If going to SP3 I would do RU2 at the same time as it contains a number of hotfixes for public folders (if you use them) as well as being able to delete certain types of emails, particularly those generated by 3rd party applications like RightFax who attach faxes as PDF's as Microsofts own meeting request/scheduler type emails.

Also remember SP3 changes both the AD schema and Database schema, once you have updated a DAG member and failed over any database to it, it can no longer fail back to any DAG member that has not been upgraded.
Click to expand...

I don't think that is strictly true. I'm sure when I tested previously having two DAG Members, one on SP1 and one on SP3, the Databases could be failed over back and forth without issue.

I think this problem was from a previous version of Exchange. Obviously again best to update servers as soon as possible after each other.
 
Eulogy said:
I don't think that is strictly true. I'm sure when I tested previously having two DAG Members, one on SP1 and one on SP3, the Databases could be failed over back and forth without issue.

I think this problem was from a previous version of Exchange. Obviously again best to update servers as soon as possible after each other.
Click to expand...

"If you're upgrading from Exchange 2010 SP2 or SP1 to Exchange 2010 SP3, the upgrade process takes less time, because there is no database schema upgrade. In addition, you can safely move a database between servers running Exchange 2010 SP1, SP2 or SP3. Even though you can move databases between mailbox servers running different service pack levels, you should complete the upgrade of all DAG members to the same service pack level without too much delay. We recommend that you minimize the amount of time you have your DAG members running different service pack levels."

So, you are correct. The information I had was completely wrong then. Thanks msexchange.org :(
 
We do not use DAG but that is handy to know, well I have got my window a mere 4 hours from 01:30 on Thursday morning, should be more than enough time I hope lol
 
Nikumba said:
We do not use DAG but that is handy to know, well I have got my window a mere 4 hours from 01:30 on Thursday morning, should be more than enough time I hope lol
Click to expand...

Depends on how fast your servers are and how many you are doing lol :D

I normally budget around an hour per server as stuff always takes longer than you think, and the update process itself can take some time.

Also you are meant to update: CAS >> HT >> MBX in that order so bear that in mind (sorry forget where EDGE lives in that list as we don't use them at all).

So not usually a good idea to be updating too many servers at once unless you don't care if everything goes down entirely lol!
 
Yeah we have CAS, HT, EDGE and 4 mailbox servers.

I believe Edge is before HT but I have budgeted about an hour a machine, but will run the mailbox servers at the same time.

They are beefy boxes all virtual, 32Gb RAM, 4 - 8 vCPU cores each

Kimbie
 
Well got it done, well the service pack not the rollup as over-ran my maintenance window.

No major issues, few niggles with the CAS server at teh start, but then the Mailbox servers threw a curve call, 1, 2, 3 all patched fine 4 had a error on the mailbox role big monstrous error that the link went no where, but turns out was to do the the Disocvery mailbox so had to delete it and the setup ran fine, and then recreate it, was odd that there were not all effected.

Doing the rollup in our usual monthly maintenance window
 
You must log in or register to reply here.
Back
Top Bottom