<div>
Exchange 2007 does not use DAG configuration so applying maintenance mode when updating doesn't apply here. &nbsp;A good read for your scenario is below. &nbsp;<br />
<br />
ref link: &nbsp;<a href="https://technet.microsoft.com/en-us/library/ee221147(v=exchg.80).aspx" rel="ugc">https://technet.microsoft.com/en-us/library/ee221147(v=exchg.80).aspx</a>
</div>


Exchange 2007 does not use DAG configuration so applying maintenance mode when updating doesn't apply here.  A good read for your scenario is below.  

ref link:  https://technet.microsoft.com/en-us/library/ee221147(v=exchg.80).aspx [https://technet.microsoft.com/en-us/library/ee221147(v=exchg.80).aspx]

<div>
Plan a weekend for the update.<br />
You dont need to put in maintenance mode for RU update.<br />
<br />
Please check this for update of clustered mailbox servers<br />
<br />
Install RU on passive nodes first then make passive as active and install on the other.<br />
<br />
<a href="https://technet.microsoft.com/en-us/library/bb885043.aspx" rel="ugc">https://technet.microsoft.com/en-us/library/bb885043.aspx</a>
</div>


Plan a weekend for the update.
You dont need to put in maintenance mode for RU update.

Please check this for update of clustered mailbox servers

Install RU on passive nodes first then make passive as active and install on the other.

https://technet.microsoft.com/en-us/library/bb885043.aspx [https://technet.microsoft.com/en-us/library/bb885043.aspx]

<div>
we don't have clustering , each server is installed on VM.<br />
<br />
please outline the steps to roll up to 19 from roll up 15
</div>


we don't have clustering , each server is installed on VM.

please outline the steps to roll up to 19 from roll up 15

<div>
I have 6 different sites, each are having cas and hub server ,is it required for roll up to be installed at same time and I believe server doesn't need reboot
</div>


I have 6 different sites, each are having cas and hub server ,is it required for roll up to be installed at same time and I believe server doesn't need reboot

<div>
You can start with passive servers (passive first) then install on MBX servers. It is a straight forward process.<br />
<br />
Thanks
</div>


You can start with passive servers (passive first) then install on MBX servers. It is a straight forward process.

Thanks

<div>
as I told you I don't have clustering, can I install roll up on each server one by one
</div>


as I told you I don't have clustering, can I install roll up on each server one by one

<div>
You you start with CAS &gt;&nbsp;Hub &gt;&nbsp;Mbx<br />
<br />
Your account used to update must be member of schema master as well since it will upgrade the AD schema<br />
<br />
For mbx, if you run on CCR, please do on passive node then failover, then do on another node
</div>


You you start with CAS > Hub > Mbx

Your account used to update must be member of schema master as well since it will upgrade the AD schema

For mbx, if you run on CCR, please do on passive node then failover, then do on another node

<div>
You can install CAS/HUB first then install MBX servers
</div>


You can install CAS/HUB first then install MBX servers

<div>
<div class="content wysiwyg-content">
We have following installed .<br />
<br />
A)Update Rollup 15 for 2 CAS and 2 mailbox servers.<br />
&nbsp;Current version: 08.03.0389.002<br />
<br />
we need to go for <br />
Update Rollup 19 for 2 CAS and 2 mailbox servers.<br />
Updated version: 08.03.0459.000<br />
<br />
<br />
please let me know the steps, do we need to put the server in maintainance mode or just install the roll ups.
</div>
</div>


We have following installed .

A)Update Rollup 15 for 2 CAS and 2 mailbox servers.
 Current version: 08.03.0389.002

we need to go for 
Update Rollup 19 for 2 CAS and 2 mailbox servers.
Updated version: 08.03.0459.000


please let me know the steps, do we need to put the server in maintainance mode or just install the roll ups.

exchange 2007, roll ups

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Version control, also known as revision control or source control, is the management of changes to documents, computer programs, large web sites, and other collections of information. Changes are usually identified by a number or letter code, termed the "revision number," "revision level," or simply "revision." Version control systems (VCS) most commonly run as stand-alone applications, but revision control is also embedded in various types of software such as word processors and spreadsheets, and in various content management systems. Revision control allows for the ability to revert a document to a previous revision. Git, a widely-used VCS, has its own topic; other popular systems include CVS, Subversion, Team Foundation Server (TFS), Visual SourceSafe (VSS) and Perforce.