Questions about steps to upgrade Ex07 to SP2 w a CCR cluster

  • Thread starter Mike O.
  • Start date Views 1,396
Status
Not open for further replies.
M

Mike O.

This weekend, we're planning to apply SP2 to our Exchange 2007 environment.

We currently have two HUB/CAS servers and two Mailbox servers in a CCR

cluster, everything running on Windows 2003 R2.

Since the initial setup early last year, I've installed the various Windows

patches and Exchange rollups, but this is the first time I'll be installing

an Exchange service pack into our cluster (when we started, we used Exchange

2007 with SP1 already included)

I've done some research and believe I have the correct sequence, but I just

wanted to make sure I'm not missing anything.

1. Update each HUB/CAS server

2. On the CCR cluster inactive node, run "setup /Mode:upgrade" from command

prompt

3.Reboot server

4. Stop clustered mailbox server using Powershell or EMC

5. Move clustered mailbox server to passive node using Powershell or EMC

6. Update the CMS (setup /upgradeCMS) from command prompt

7. Go to original active node (now the passive one) Setup /Mode:Upgrade from

command prompt

I know while the CMS is being upgraded that users won't be able to access

email. Is there any way to estimate the outage window? We have fairly

recent hardware (four dual core 3Ghz processors, 32GB of RAM), and about

5,000 users

Any comments would be appreciated.

Mike O.
 
E

Ed Crowley [MVP]

First, Exchange 2007 SP2 includes a schema update. You may want to run the

setup.com /PrepareSchema, /PrepareAD and /PrepareDomain steps separately

before you update the server if you haven't already.

I don't think you need step 4. Where did you read that you need to stop the

CMS?

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"Mike O." <MikeO> wrote in message

news:761971E0-087A-4BF4-AB69-3905DBEA347E@microsoft.com...
> This weekend, we're planning to apply SP2 to our Exchange 2007
> environment.
> We currently have two HUB/CAS servers and two Mailbox servers in a CCR
> cluster, everything running on Windows 2003 R2.

> Since the initial setup early last year, I've installed the various
> Windows
> patches and Exchange rollups, but this is the first time I'll be
> installing
> an Exchange service pack into our cluster (when we started, we used
> Exchange
> 2007 with SP1 already included)

> I've done some research and believe I have the correct sequence, but I
> just
> wanted to make sure I'm not missing anything.

> 1. Update each HUB/CAS server
> 2. On the CCR cluster inactive node, run "setup /Mode:upgrade" from
> command
> prompt
> 3.Reboot server
> 4. Stop clustered mailbox server using Powershell or EMC
> 5. Move clustered mailbox server to passive node using Powershell or EMC
> 6. Update the CMS (setup /upgradeCMS) from command prompt
> 7. Go to original active node (now the passive one) Setup /Mode:Upgrade
> from
> command prompt

> I know while the CMS is being upgraded that users won't be able to access
> email. Is there any way to estimate the outage window? We have fairly
> recent hardware (four dual core 3Ghz processors, 32GB of RAM), and about
> 5,000 users

> Any comments would be appreciated.

> Mike O.
 
M

Mike O.

I knew it had a schema update, one of the reasons I want to go with SP2 now

is so that we can get ready for Exchange 2010, probably sometime next

month.. I was wondering about the schema changes, though, whether it

automatically went in as part of the first system I applied SP2, or if I had

to install it separately (sounds like I should run it first). If/when the

schema update is running, does it affect any active systems? I assume I

need to wait until it's done before I start applying SP2 to the systems and

was wondering if I could start the schema update prior to my maintenance

"outage" window.

As for the stopping the CMS, my list was pretty much taken from this:

http://technet.microsoft.com/en-us/library/bb676320(EXCHG.80).aspx

steps 8 and 9 say to stop the clustered mailbox server and then move it to

the updated, previously passive node.

This also matches

http://www.messagingtalk.org/ms-exchange-server-2007-sp1-upgrade-sp2-part-2

and some other sites.

Is there any kind of estimate available as to how long the CMS upgrade will

take? We have a maintenance window, and I think I've allowed plenty of

time, but I was just wondering so that I know how long after I start it

before I need to start getting worried...

Mike O.

"Ed Crowley [MVP]" <curspice@nospam.net> wrote in message

news:u8cQ%23wUfKHA.1112@TK2MSFTNGP04.phx.gbl...
> First, Exchange 2007 SP2 includes a schema update. You may want to run
> the setup.com /PrepareSchema, /PrepareAD and /PrepareDomain steps
> separately before you update the server if you haven't already.

> I don't think you need step 4. Where did you read that you need to stop
> the CMS?
> > Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .

> "Mike O." <MikeO> wrote in message
> news:761971E0-087A-4BF4-AB69-3905DBEA347E@microsoft.com...
> > This weekend, we're planning to apply SP2 to our Exchange 2007
> > environment.
> > We currently have two HUB/CAS servers and two Mailbox servers in a CCR
> > cluster, everything running on Windows 2003 R2.
>

>> Since the initial setup early last year, I've installed the various
> > Windows
> > patches and Exchange rollups, but this is the first time I'll be
> > installing
> > an Exchange service pack into our cluster (when we started, we used
> > Exchange
> > 2007 with SP1 already included)
>

>> I've done some research and believe I have the correct sequence, but I
> > just
> > wanted to make sure I'm not missing anything.
>

>> 1. Update each HUB/CAS server
> > 2. On the CCR cluster inactive node, run "setup /Mode:upgrade" from
> > command
> > prompt
> > 3.Reboot server
> > 4. Stop clustered mailbox server using Powershell or EMC
> > 5. Move clustered mailbox server to passive node using Powershell or EMC
> > 6. Update the CMS (setup /upgradeCMS) from command prompt
> > 7. Go to original active node (now the passive one) Setup /Mode:Upgrade
> > from
> > command prompt
>

>> I know while the CMS is being upgraded that users won't be able to access
> > email. Is there any way to estimate the outage window? We have fairly
> > recent hardware (four dual core 3Ghz processors, 32GB of RAM), and about
> > 5,000 users
>

>> Any comments would be appreciated.
>

>> Mike O.

>
 
E

Ed Crowley [MVP]

I stand corrected. I guess I haven't applied SP2 on existing systems, just

installed it new.

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"Mike O." <putthespam@thecan.com> wrote in message

news:e2zA0xgfKHA.5036@TK2MSFTNGP04.phx.gbl...
> I knew it had a schema update, one of the reasons I want to go with SP2 now
> is so that we can get ready for Exchange 2010, probably sometime next
> month.. I was wondering about the schema changes, though, whether it
> automatically went in as part of the first system I applied SP2, or if I
> had to install it separately (sounds like I should run it first). If/when
> the schema update is running, does it affect any active systems? I assume
> I need to wait until it's done before I start applying SP2 to the systems
> and was wondering if I could start the schema update prior to my
> maintenance "outage" window.

> As for the stopping the CMS, my list was pretty much taken from this:
> http://technet.microsoft.com/en-us/library/bb676320(EXCHG.80).aspx

> steps 8 and 9 say to stop the clustered mailbox server and then move it to
> the updated, previously passive node.

> This also matches
> http://www.messagingtalk.org/ms-exchange-server-2007-sp1-upgrade-sp2-part-2
> and some other sites.

> Is there any kind of estimate available as to how long the CMS upgrade
> will take? We have a maintenance window, and I think I've allowed
> plenty of time, but I was just wondering so that I know how long after I
> start it before I need to start getting worried...

> Mike O.

> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> news:u8cQ%23wUfKHA.1112@TK2MSFTNGP04.phx.gbl...
> > First, Exchange 2007 SP2 includes a schema update. You may want to run
> > the setup.com /PrepareSchema, /PrepareAD and /PrepareDomain steps
> > separately before you update the server if you haven't already.
>

>> I don't think you need step 4. Where did you read that you need to stop
> > the CMS?
> > > > Ed Crowley MVP
> > "There are seldom good technological solutions to behavioral problems."
> > .
>

>> "Mike O." <MikeO> wrote in message
> > news:761971E0-087A-4BF4-AB69-3905DBEA347E@microsoft.com...
> >> This weekend, we're planning to apply SP2 to our Exchange 2007
> >> environment.
> >> We currently have two HUB/CAS servers and two Mailbox servers in a CCR
> >> cluster, everything running on Windows 2003 R2.
> >
>>> Since the initial setup early last year, I've installed the various
> >> Windows
> >> patches and Exchange rollups, but this is the first time I'll be
> >> installing
> >> an Exchange service pack into our cluster (when we started, we used
> >> Exchange
> >> 2007 with SP1 already included)
> >
>>> I've done some research and believe I have the correct sequence, but I
> >> just
> >> wanted to make sure I'm not missing anything.
> >
>>> 1. Update each HUB/CAS server
> >> 2. On the CCR cluster inactive node, run "setup /Mode:upgrade" from
> >> command
> >> prompt
> >> 3.Reboot server
> >> 4. Stop clustered mailbox server using Powershell or EMC
> >> 5. Move clustered mailbox server to passive node using Powershell or EMC
> >> 6. Update the CMS (setup /upgradeCMS) from command prompt
> >> 7. Go to original active node (now the passive one) Setup /Mode:Upgrade
> >> from
> >> command prompt
> >
>>> I know while the CMS is being upgraded that users won't be able to
> >> access
> >> email. Is there any way to estimate the outage window? We have fairly
> >> recent hardware (four dual core 3Ghz processors, 32GB of RAM), and about
> >> 5,000 users
> >
>>> Any comments would be appreciated.
> >
>>> Mike O.

> >

>
 
M

Mike O.

No problem.

Any information about the other questions about whether the schema update

can be done without disrupting "live" systems and any estimate on the

updateCMS outage time?

"Ed Crowley [MVP]" <curspice@nospam.net> wrote in message

news:OCo8W4ifKHA.2780@TK2MSFTNGP05.phx.gbl...
> I stand corrected. I guess I haven't applied SP2 on existing systems, just
> installed it new.
> > Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .

> "Mike O." <putthespam@thecan.com> wrote in message
> news:e2zA0xgfKHA.5036@TK2MSFTNGP04.phx.gbl...
> >I knew it had a schema update, one of the reasons I want to go with SP2
> >now is so that we can get ready for Exchange 2010, probably sometime next
> >month.. I was wondering about the schema changes, though, whether it
> >automatically went in as part of the first system I applied SP2, or if I
> >had to install it separately (sounds like I should run it first).
> >If/when the schema update is running, does it affect any active systems?
> >I assume I need to wait until it's done before I start applying SP2 to the
> >systems and was wondering if I could start the schema update prior to my
> >maintenance "outage" window.
>

>> As for the stopping the CMS, my list was pretty much taken from this:
> > http://technet.microsoft.com/en-us/library/bb676320(EXCHG.80).aspx
>

>> steps 8 and 9 say to stop the clustered mailbox server and then move it
> > to the updated, previously passive node.
>

>> This also matches
> > http://www.messagingtalk.org/ms-exchange-server-2007-sp1-upgrade-sp2-part-2
> > and some other sites.
>

>> Is there any kind of estimate available as to how long the CMS upgrade
> > will take? We have a maintenance window, and I think I've allowed
> > plenty of time, but I was just wondering so that I know how long after I
> > start it before I need to start getting worried...
>

>> Mike O.
>

>
>> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> > news:u8cQ%23wUfKHA.1112@TK2MSFTNGP04.phx.gbl...
> >> First, Exchange 2007 SP2 includes a schema update. You may want to run
> >> the setup.com /PrepareSchema, /PrepareAD and /PrepareDomain steps
> >> separately before you update the server if you haven't already.
> >
>>> I don't think you need step 4. Where did you read that you need to stop
> >> the CMS?
> >> > >> Ed Crowley MVP
> >> "There are seldom good technological solutions to behavioral problems."
> >> .
> >
>>> "Mike O." <MikeO> wrote in message
> >> news:761971E0-087A-4BF4-AB69-3905DBEA347E@microsoft.com...
> >>> This weekend, we're planning to apply SP2 to our Exchange 2007
> >>> environment.
> >>> We currently have two HUB/CAS servers and two Mailbox servers in a CCR
> >>> cluster, everything running on Windows 2003 R2.
> >>
>>>> Since the initial setup early last year, I've installed the various
> >>> Windows
> >>> patches and Exchange rollups, but this is the first time I'll be
> >>> installing
> >>> an Exchange service pack into our cluster (when we started, we used
> >>> Exchange
> >>> 2007 with SP1 already included)
> >>
>>>> I've done some research and believe I have the correct sequence, but I
> >>> just
> >>> wanted to make sure I'm not missing anything.
> >>
>>>> 1. Update each HUB/CAS server
> >>> 2. On the CCR cluster inactive node, run "setup /Mode:upgrade" from
> >>> command
> >>> prompt
> >>> 3.Reboot server
> >>> 4. Stop clustered mailbox server using Powershell or EMC
> >>> 5. Move clustered mailbox server to passive node using Powershell or
> >>> EMC
> >>> 6. Update the CMS (setup /upgradeCMS) from command prompt
> >>> 7. Go to original active node (now the passive one) Setup /Mode:Upgrade
> >>> from
> >>> command prompt
> >>
>>>> I know while the CMS is being upgraded that users won't be able to
> >>> access
> >>> email. Is there any way to estimate the outage window? We have fairly
> >>> recent hardware (four dual core 3Ghz processors, 32GB of RAM), and
> >>> about
> >>> 5,000 users
> >>
>>>> Any comments would be appreciated.
> >>
>>>> Mike O.
> >>

> >

>
 
E

Ed Crowley [MVP]

My experience with that schema change and others is that they don't affect

anything in your network except potentially causing some extra replication.

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"Mike O." <putthespam@thecan.com> wrote in message

news:uqyIV1rfKHA.3792@TK2MSFTNGP02.phx.gbl...
> No problem.

> Any information about the other questions about whether the schema update
> can be done without disrupting "live" systems and any estimate on the
> updateCMS outage time?

> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> news:OCo8W4ifKHA.2780@TK2MSFTNGP05.phx.gbl...
> >I stand corrected. I guess I haven't applied SP2 on existing systems,
> >just installed it new.
> > > > Ed Crowley MVP
> > "There are seldom good technological solutions to behavioral problems."
> > .
>

>> "Mike O." <putthespam@thecan.com> wrote in message
> > news:e2zA0xgfKHA.5036@TK2MSFTNGP04.phx.gbl...
> >>I knew it had a schema update, one of the reasons I want to go with SP2
> >>now is so that we can get ready for Exchange 2010, probably sometime next
> >>month.. I was wondering about the schema changes, though, whether it
> >>automatically went in as part of the first system I applied SP2, or if I
> >>had to install it separately (sounds like I should run it first). If/when
> >>the schema update is running, does it affect any active systems? I assume
> >>I need to wait until it's done before I start applying SP2 to the systems
> >>and was wondering if I could start the schema update prior to my
> >>maintenance "outage" window.
> >
>>> As for the stopping the CMS, my list was pretty much taken from this:
> >> http://technet.microsoft.com/en-us/library/bb676320(EXCHG.80).aspx
> >
>>> steps 8 and 9 say to stop the clustered mailbox server and then move it
> >> to the updated, previously passive node.
> >
>>> This also matches
> >> http://www.messagingtalk.org/ms-exchange-server-2007-sp1-upgrade-sp2-part-2
> >> and some other sites.
> >
>>> Is there any kind of estimate available as to how long the CMS upgrade
> >> will take? We have a maintenance window, and I think I've allowed
> >> plenty of time, but I was just wondering so that I know how long after I
> >> start it before I need to start getting worried...
> >
>>> Mike O.
> >
>>
>>> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> >> news:u8cQ%23wUfKHA.1112@TK2MSFTNGP04.phx.gbl...
> >>> First, Exchange 2007 SP2 includes a schema update. You may want to run
> >>> the setup.com /PrepareSchema, /PrepareAD and /PrepareDomain steps
> >>> separately before you update the server if you haven't already.
> >>
>>>> I don't think you need step 4. Where did you read that you need to
> >>> stop the CMS?
> >>> > >>> Ed Crowley MVP
> >>> "There are seldom good technological solutions to behavioral problems."
> >>> .
> >>
>>>> "Mike O." <MikeO> wrote in message
> >>> news:761971E0-087A-4BF4-AB69-3905DBEA347E@microsoft.com...
> >>>> This weekend, we're planning to apply SP2 to our Exchange 2007
> >>>> environment.
> >>>> We currently have two HUB/CAS servers and two Mailbox servers in a CCR
> >>>> cluster, everything running on Windows 2003 R2.
> >>>
>>>>> Since the initial setup early last year, I've installed the various
> >>>> Windows
> >>>> patches and Exchange rollups, but this is the first time I'll be
> >>>> installing
> >>>> an Exchange service pack into our cluster (when we started, we used
> >>>> Exchange
> >>>> 2007 with SP1 already included)
> >>>
>>>>> I've done some research and believe I have the correct sequence, but I
> >>>> just
> >>>> wanted to make sure I'm not missing anything.
> >>>
>>>>> 1. Update each HUB/CAS server
> >>>> 2. On the CCR cluster inactive node, run "setup /Mode:upgrade" from
> >>>> command
> >>>> prompt
> >>>> 3.Reboot server
> >>>> 4. Stop clustered mailbox server using Powershell or EMC
> >>>> 5. Move clustered mailbox server to passive node using Powershell or
> >>>> EMC
> >>>> 6. Update the CMS (setup /upgradeCMS) from command prompt
> >>>> 7. Go to original active node (now the passive one) Setup
> >>>> /Mode:Upgrade from
> >>>> command prompt
> >>>
>>>>> I know while the CMS is being upgraded that users won't be able to
> >>>> access
> >>>> email. Is there any way to estimate the outage window? We have
> >>>> fairly
> >>>> recent hardware (four dual core 3Ghz processors, 32GB of RAM), and
> >>>> about
> >>>> 5,000 users
> >>>
>>>>> Any comments would be appreciated.
> >>>
>>>>> Mike O.
> >>
>>>

> >

>
 
M

Mike O.

I guess I was wondering that since it was dealing with Exchange specific

items, would it affect our Exchange 2007 systems if I start the schema

install while the Email systems are up.

"Ed Crowley [MVP]" <curspice@nospam.net> wrote in message

news:ea30ZEsfKHA.4636@TK2MSFTNGP04.phx.gbl...
> My experience with that schema change and others is that they don't affect
> anything in your network except potentially causing some extra
> replication.
> > Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .

> "Mike O." <putthespam@thecan.com> wrote in message
> news:uqyIV1rfKHA.3792@TK2MSFTNGP02.phx.gbl...
> > No problem.
>

>
>> Any information about the other questions about whether the schema update
> > can be done without disrupting "live" systems and any estimate on the
> > updateCMS outage time?
>

>
>> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> > news:OCo8W4ifKHA.2780@TK2MSFTNGP05.phx.gbl...
> >>I stand corrected. I guess I haven't applied SP2 on existing systems,
> >>just installed it new.
> >> > >> Ed Crowley MVP
> >> "There are seldom good technological solutions to behavioral problems."
> >> .
> >
>>> "Mike O." <putthespam@thecan.com> wrote in message
> >> news:e2zA0xgfKHA.5036@TK2MSFTNGP04.phx.gbl...
> >>>I knew it had a schema update, one of the reasons I want to go with SP2
> >>>now is so that we can get ready for Exchange 2010, probably sometime
> >>>next month.. I was wondering about the schema changes, though, whether
> >>>it automatically went in as part of the first system I applied SP2, or
> >>>if I had to install it separately (sounds like I should run it first).
> >>>If/when the schema update is running, does it affect any active systems?
> >>>I assume I need to wait until it's done before I start applying SP2 to
> >>>the systems and was wondering if I could start the schema update prior
> >>>to my maintenance "outage" window.
> >>
>>>> As for the stopping the CMS, my list was pretty much taken from this:
> >>> http://technet.microsoft.com/en-us/library/bb676320(EXCHG.80).aspx
> >>
>>>> steps 8 and 9 say to stop the clustered mailbox server and then move it
> >>> to the updated, previously passive node.
> >>
>>>> This also matches
> >>> http://www.messagingtalk.org/ms-exchange-server-2007-sp1-upgrade-sp2-part-2
> >>> and some other sites.
> >>
>>>> Is there any kind of estimate available as to how long the CMS upgrade
> >>> will take? We have a maintenance window, and I think I've allowed
> >>> plenty of time, but I was just wondering so that I know how long after
> >>> I start it before I need to start getting worried...
> >>
>>>> Mike O.
> >>
>>>
>>>> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> >>> news:u8cQ%23wUfKHA.1112@TK2MSFTNGP04.phx.gbl...
> >>>> First, Exchange 2007 SP2 includes a schema update. You may want to
> >>>> run the setup.com /PrepareSchema, /PrepareAD and /PrepareDomain steps
> >>>> separately before you update the server if you haven't already.
> >>>
>>>>> I don't think you need step 4. Where did you read that you need to
> >>>> stop the CMS?
> >>>> > >>>> Ed Crowley MVP
> >>>> "There are seldom good technological solutions to behavioral
> >>>> problems."
> >>>> .
> >>>
>>>>> "Mike O." <MikeO> wrote in message
> >>>> news:761971E0-087A-4BF4-AB69-3905DBEA347E@microsoft.com...
> >>>>> This weekend, we're planning to apply SP2 to our Exchange 2007
> >>>>> environment.
> >>>>> We currently have two HUB/CAS servers and two Mailbox servers in a
> >>>>> CCR
> >>>>> cluster, everything running on Windows 2003 R2.
> >>>>
>>>>>> Since the initial setup early last year, I've installed the various
> >>>>> Windows
> >>>>> patches and Exchange rollups, but this is the first time I'll be
> >>>>> installing
> >>>>> an Exchange service pack into our cluster (when we started, we used
> >>>>> Exchange
> >>>>> 2007 with SP1 already included)
> >>>>
>>>>>> I've done some research and believe I have the correct sequence, but
> >>>>> I just
> >>>>> wanted to make sure I'm not missing anything.
> >>>>
>>>>>> 1. Update each HUB/CAS server
> >>>>> 2. On the CCR cluster inactive node, run "setup /Mode:upgrade" from
> >>>>> command
> >>>>> prompt
> >>>>> 3.Reboot server
> >>>>> 4. Stop clustered mailbox server using Powershell or EMC
> >>>>> 5. Move clustered mailbox server to passive node using Powershell or
> >>>>> EMC
> >>>>> 6. Update the CMS (setup /upgradeCMS) from command prompt
> >>>>> 7. Go to original active node (now the passive one) Setup
> >>>>> /Mode:Upgrade from
> >>>>> command prompt
> >>>>
>>>>>> I know while the CMS is being upgraded that users won't be able to
> >>>>> access
> >>>>> email. Is there any way to estimate the outage window? We have
> >>>>> fairly
> >>>>> recent hardware (four dual core 3Ghz processors, 32GB of RAM), and
> >>>>> about
> >>>>> 5,000 users
> >>>>
>>>>>> Any comments would be appreciated.
> >>>>
>>>>>> Mike O.
> >>>
>>>
>>>

> >

>
 
A

Andrew Hodgson

On Thu, 17 Dec 2009 00:27:23 -0500, "Mike O." <putthespam@thecan.com
wrote:


> I guess I was wondering that since it was dealing with Exchange specific
> items, would it affect our Exchange 2007 systems if I start the schema
> install while the Email systems are up.


Not at all. I have done two of these, the first I did the schema

update during office hours then did the SP update later on, the second

I just did the SP update and it did the schema update (because it

connected to our schema master DC), both times went through fine.

On the second time I did the update first on a HT server, and it

detected the schema modifications were necessary.

Andrew.
 
M

Mike O.

Sounds good. I'm starting the update on the first HT server now...

"Andrew Hodgson" <andrew@hodgsonfamily.org> wrote in message

news:kkaqi5dtq9b94fn99kjjcrp20k70iheugm@news.giganews.com...
> On Thu, 17 Dec 2009 00:27:23 -0500, "Mike O." <putthespam@thecan.com
> wrote:
>
> >I guess I was wondering that since it was dealing with Exchange specific
> >items, would it affect our Exchange 2007 systems if I start the schema
> >install while the Email systems are up.


> Not at all. I have done two of these, the first I did the schema
> update during office hours then did the SP update later on, the second
> I just did the SP update and it did the schema update (because it
> connected to our schema master DC), both times went through fine.

> On the second time I did the update first on a HT server, and it
> detected the schema modifications were necessary.

> Andrew.
 
M

Mike O.

Just wanted to update the process.

I went ahead and ran the GUI on the first hub server, and let it do the

schema changes, no problems.

On the second hub server, it went through the pre-requesites, but when it

started the actual patch it failed saying that it couldn't stop the transport

service. I tried re-running the patch, but it then failed saying it

couldn't access the remote registry and IIS services. I rebooted and got the

same thing. I then noticed that the IIS and remote registry services had

been "disabled", apparently by the patches first attempt. I enabled them and

restarted them, then ran the patch again and this time it worked.

The CCR udpates went perfect. The big question I had was about the time for

the "updateCMS". It was only about 10 minutes and everything came up OK.

Other than having to install the installer 4.5 and reboot before applying

the patch, the whole process wasn't too bad. When the patch failed on the

first hub server it would have been nice if it would have re-enabled the

services it turned off, though.

Thanks for the comments.

Mike O.
 
Status
Not open for further replies.
Top