The impact of Exchange Server 2007 SP1 in Windows Vista and Windows 2008
Exchange 2007 supports new generation Windows operating systems including Windows Server 2008 and Windows Vista (for management purposes).
For Windows 2008 and Windows Vista users or administrators, we must install using the latest media with the integrated RTM and SP1 versions. There is no other way to install RTM and then run the SP1 upgrade.
For users who are using Exchange 2007 RTM, we can upgrade the current installation using the SP1 upgrade package, but make sure you are using XP SP2 or 2003 as well.
Prepare Forests and Domains through command line utilities
Exchange Server 2007 Service Pack 1 has a domain upgrade and schema. This process can be done automatically by the SP1 Wizard, but in a wide environment or disconnected permissions, we can prepare the forest and domain using the table below:
Order to run
Order
Permission required
first
Setup / PrepareSchemaSchema Admins and Enterprise Admins Groups
2
Setup / PrepareADEnterprise Admins Group
3
Setup / PrepareDomain
or
Setup / PrepareAllDomainsDomain Admins
To validate the version of the schema, we can retrieve the objectversion property from the Exchange Organization item via Adsiedit.msc, the possible values are: 10666 for the RTM version and 11221 for SP1.
Upgrade Exchange Server 2007 to Service Pack 1
The GUI process is quite simple and it can be applied in most Exchange Server 2007 environments, except when we have a CMS (Clustered Mailbox Server) scenario, because this scenario requires an interest. special steps and steps, all of these steps will be introduced in the last part of this article. Before running the installation, you must validate the permissions: First, the upgrade must be done by the Exchange Organization Administrators role and must be the internal administrator of the current server.
Before upgrading to SP1, there are a few things to keep in mind:
• No need to delete any updates installed because this installation will recognize them and will be deleted automatically.
• If we have multiple server and local environments, SP1 should be installed first at CAS servers that are directly connected to the Internet.
• Verifying software from third-party vendors running on SP1, an upgrade may be necessary for them to upgrade to SP1 properly.
• Start the remote registry service.
Here are some steps involved in upgrading Exchange Server 2007 RTM to Service Pack 1:
1. Double-click Setup.exe to extract SP1 or SP1 media files, and then click Install Microsoft Exchange Service Pack 1 (Figure 1).
Figure 1
2. Introduction page. A summary of the new features that will be introduced in your environment will be displayed here, click Next to continue.
3. The License agreement page. If you agree with the registration agreement, click on I accept . and click Next .
4. Page Readiness . The current system will be validated and if the current server has any serious problems, the installation will not continue, in the case of the image below, just a warning about the .Net Framework SP1 being installed. . Just click Upgrade to start the upgrade process.
Figure 2
5. Completion page. The final screen of the wizard will show you that all installed roles have been successfully upgraded.
Figure 3
Important
After upgrading to Exchange Server 2007 you will not be able to uninstall it. When performing an uninstall via Add / Remove Programs, you will remove the entire product.
Upgrade to Exchange Server 2007 SP1 via the command line utility
To upgrade Exchange Server 2007 using the command line utility, we just need to run setup / mode: upgrade from SP1 source files, as shown in Figure 4.
Figure 4
Upgrade Clustered Mailbox Servers (CMS) to Service Pack 1
Once we have deployed CCR / SCC, the process involved in upgrading the CMS to SP1 has some differences from the usual process as seen in the previous sections.
In this article, we will upgrade the CCR cluster - the two-node component - the image of the process involved in upgrading both nodes can be seen in Figure 5. The basic process consists of isolation Passive node (srv-node02) and proceed to upgrade it to SP1; convert the offline CMS into the installed SP1 node (srv-node02) and then upgrade the CMS to SP1; Finally upgrade the RTM button (srv-node01) to SP1.
Figure 5
This is just a snapshot of what to do, see details of the necessary steps:
1. First, extract the SP1 files to a local directory of each server.
2. Make sure all resources are in the first node. To move the CMD to the first node we use the Move-ClusteredMailboxServer cmdlet; To move the Cluster Group we use Cluster Administrator .
3. In the second button . Stop all processes and services to count MOM Agent agents.
4. In the second button . Make sure that Windows Firewall is started and restart the Remote Registry service. We can perform two tasks through this cmdlet in PowerShell Session:
Set-Service SharedAccess -StartupType: Automatic or Manual
Start-Service SharedAccess
Restart-Service RemoteRegistry
Note :
The installation process will add the exception of Windows Firewall to Exchange services and we can disable it at the end of the process.
5. In the second button . Now we will upgrade bin files, run setup / mode: upgrade (see Figure 6). After the SP1 installation has finished, we need to restart the server.
Figure 6
6. In the second button . Open Exchange Management Shell to stop and switch CMS.
Note : During the process, CMS will not serve clients. These cmdlets should be run:
Stop-ClusteredMailboxServer -StopReason 'Upgrade to SP1', type Y to confirm the operation
Move-ClusteredMailboxServer -TargetMachine Srv-Node02 -MoveComment 'SP1 upgrade'
7. In the second button . At this point, the second node is upgraded to SP1 and it has CMS resources, the next step is to upgrade the CMS to SP1. To do that, we need to run: setup / UpgradeCMS , see Figure 7.
Figure 7
8. Now the CMS and the second node are running SP1, we must upgrade the remaining node to SP1. To perform this task, follow steps 3 to 5 in the first button.
9. If you do not use Windows Firewall, it can be disabled for the above two buttons ( Set-Service SharedAccess –StartupType: Disabled )
10. Finally, your CMS has been upgraded to SP1.
If you have a SCC environment, the environment may have more than two nodes, steps 3 through 5 must be repeated for all nodes.