Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Mon, 14 Apr 2008 12:14:28 +0100,    group: microsoft.public.exchange.clustering        back       


CCR   
Quick one -

i need to physically move all our Exchange servers 2 x CCR and 1 x HT\Cas - 
what is the preferred method?
Do I stop the CCR usign Stop-ClusteredMailboxServer and then power them on 
or is there an alternative way?

I had an issue before where I had to update hte passive node as I got event 
id 2056
date: Mon, 14 Apr 2008 12:14:28 +0100   author:   IT

Re: CCR   
If by move, you mean physically move them, then the process would be to:

1. Stop the CMS using Stop-ClusteredMailboxServer.
2. Shut down the passive node.
3. Shut down the active node.
4. Shut down HUB/CAS (which I assume hosts the share for the FSW).

Then, when powering up:

1. Power up HUB/CAS.
2. Power up active node.
3. Power up passive node.
4. Start the CMS using Start-Clustered MailboxServer.

Hope this helps.
-- 
Regards,

Scott Schnoll
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.


"IT"  wrote in message 
news:ueex1CinIHA.4744@TK2MSFTNGP06.phx.gbl...
> Quick one -
>
> i need to physically move all our Exchange servers 2 x CCR and 1 x 
> HT\Cas - what is the preferred method?
> Do I stop the CCR usign Stop-ClusteredMailboxServer and then power them on 
> or is there an alternative way?
>
> I had an issue before where I had to update hte passive node as I got 
> event id 2056
>
date: Mon, 14 Apr 2008 11:49:49 -0700   author:   Scott Schnoll [MSFT]

Re: CCR   
That's the one - thanks


"Scott Schnoll [MSFT]"  wrote in message 
news:eue0SBmnIHA.3512@TK2MSFTNGP03.phx.gbl...
> If by move, you mean physically move them, then the process would be to:
>
> 1. Stop the CMS using Stop-ClusteredMailboxServer.
> 2. Shut down the passive node.
> 3. Shut down the active node.
> 4. Shut down HUB/CAS (which I assume hosts the share for the FSW).
>
> Then, when powering up:
>
> 1. Power up HUB/CAS.
> 2. Power up active node.
> 3. Power up passive node.
> 4. Start the CMS using Start-Clustered MailboxServer.
>
> Hope this helps.
> -- 
> Regards,
>
> Scott Schnoll
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
>
> "IT"  wrote in message 
> news:ueex1CinIHA.4744@TK2MSFTNGP06.phx.gbl...
>> Quick one -
>>
>> i need to physically move all our Exchange servers 2 x CCR and 1 x 
>> HT\Cas - what is the preferred method?
>> Do I stop the CCR usign Stop-ClusteredMailboxServer and then power them 
>> on or is there an alternative way?
>>
>> I had an issue before where I had to update hte passive node as I got 
>> event id 2056
>>
>
date: Tue, 15 Apr 2008 08:27:01 +0100   author:   IT

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us