ICPs include release notes that must be carefully reviewed because they describe prerequisites for the ICP, and they address known problems that the ICP does not solve. When you read the release notes, consider your answers to the following questions:

• Are there any prerequisites that must be implemented before you apply this ICP? Generally, the only prerequisite for an ICP site server installation is that it must be installed on an English-language operating system. However, other requirements might be listed.
  
  
• Does this ICP change Configuration Manager 2007 enough so that you must notify other people who are affected by this change? The people who need notification might include other Configuration Manager 2007 administrators, managers, technical staff, people responsible for the files and security of the domain controllers, people who monitor bandwidth usage, people who use the Configuration Manager 2007 services, and the end users.
  
  
• Does deploying this ICP cause additional load on the network, servers, or clients? If so, then planning the deployment of the service pack can minimize this effect.
  
  
• Is your environment large enough or complex enough to warrant treating the deployment of this ICP as a formal project?
  
  
• Do you have problems with clients that might prevent a successful upgrade? If so, you must resolve these issues before upgrading your clients.
  
  
• How large are the client upgrade components? To determine the size of your upgrade, see the "Determine the size of client component upgrades" section later in this chapter.
  
  

Checking versions

ICPs are released in numbered versions including ICP1 and ICP2. Each version supports a greater number of client operating system languages, including the operating system languages of the earlier version.

When you install an ICP on a U.S. English site, the ICP version must be compatible with a previously installed Configuration Manager 2007 service pack version. For example, you must use the Configuration Manager 2007 SP1 version of ICP2 if U.S. English Configuration Manager 2007 SP1 is installed on the site server. You cannot install the SP2 version of the ICP on a U.S. English SP1 site.

After an ICP is installed, you must be aware of the timing of subsequent ICP releases. ICPs are released shortly after each service pack. When a new service pack is released you must wait for the subsequent ICP release before installing the service pack. After you have obtained the ICP, install the service pack, and then install the ICP.

If you are concerned about the stability of the site after you install the service pack, you can wait for the service pack installation to stabilize before you install the ICP. However, your international clients will have an older version of the localized client files until the ICP is installed.

Applying updates

To apply client hotfixes, also called product updates, to an ICP site, you must obtain a hotfixed version of the ICP you have installed. You can identify service pack, ICP, and hotfix numbers from the version number. These minor releases and revisions are the last four digits of the Configuration Manager 2007 version number.

You can determine whether an ICP is installed by checking for multiple language folders, such as the 00000409 folder for English and the 00000407 folder for German on the site server. There is a folder for each client language supported by that ICP.

The first digit of the fourth part of the version number, such as x in x000, is the service pack release number. For example, 2.50.2485.2000 denotes SP2. If the Configuration Manager 2007 version number is 2.50.2485.3000 or higher, then the service pack is SP3.

Additionally, ICP1 has a 4 as the third-to-last digit. For example, 2.50.2485.2400 indicates SP2 ICP1, and 2.50.2485.3400 indicates SP3 ICP1. Likewise, ICP2 has a 7 as the third-to-last digit. For example, 2.50.2485.3700 indicates SP3 ICP2.

The last three digits are the hotfix version number, which can range from .0001 to .0299.

If you apply Configuration Manager 2007 SP2 ICP1 to a Configuration Manager 2007 SP2 U.S. English site that has had several hotfixes installed after SP2 was installed, and files with the same name are included in ICP1, then ICP1 overwrites the newer files because the files in ICP1 do not contain the bug fixes. If the ICP overwrites new files, whatever problems caused you to apply the hotfixes might reappear. For example, you might have previously applied a hotfix to prevent Configuration Manager 2007 APM32 from using the CPU at 100 percent. Later you apply ICP1, which does not contain the hotfix. After ICP1 installation, your site server CPU usage is back to 100 percent. To prevent this from occurring, contact Microsoft Product Support Services and obtain the version of the hotfix that correctly matches the ICP you intend to install before ICP installation. Then, after you install the ICP, immediately install the hotfixes that were released later than the ICP.

Because ICPs are cumulative and are released as they become available, you might need to plan the deployment of language-specific versions of Configuration Manager 2007 server and client software when the ICP you need becomes available. ICPs have their own setup program and can be installed sequentially onto a site server without any change to the existing clients. All new clients can install in any of the languages from the most recently installed ICP.

Consider the size of the ICPs in relation to the available bandwidth of your network. Later versions of ICPs are larger because each consecutive version contains the languages of the previous versions. Plan the deployment of any language client pack for light network usage periods to minimize degradation of network performance for your users.

Microsoft often releases service packs and client packs on the Web, so that the latest updates can be made available to customers as quickly as possible. The ICPs released by Microsoft contain the current service pack files, in addition to the ICP files, to reduce the number of required installations. These releases are available at http://go.microsoft.com/fwlink/?LinkId=93900.

Installation of Configuration Manager 2007 ICP occurs in three phases:

• Installing an ICP on the site server: Installing an ICP starts with running the ICP setup program on a site server. When the site server is upgraded with the ICP, it automatically upgrades the client source files.
  
  
• Installing an ICP on management point: The client files on management points are automatically upgraded.
  
  
• Installing an ICP on a client: Clients are not automatically upgraded. If an upgrade is required, the administrator must determine the method.
  
  

Site component ICP installation methods can be seen in the following table:

Configuration Manager 2007 site component	Method
Site server on primary or secondary site	Running Setup.exe from the ICP source, or package, then manually installing required language packs to the system where the SMS Provider exists.
Site server on secondary site (alternative method)	Running the Upgrade Secondary Sites or Upgrade Site option from the Configuration Manager console, depending on what kind of site node is selected.
Management point	Automatically updated by Inbox Manager.
Distribution points	Not applicable.
Component servers, such as sender servers	Not applicable.
SQL Server if it is installed on a computer other than the site server, or the SMS Provider if it is installed on the SQL Server	Manually installing the required language packs to the system where the SMS Provider exists. For additional information about manually installing language packs, see the ICP release notes.
Configuration Manager consoles on separate computers	Manually adding code pages.

Primary site server ICP installation

The ICP setup program runs on the site server. It stops all components on the site system, copies the client files to the site server, and then restarts all site components on the site system. You can monitor the progress of the setup program with the progress dialog boxes that appear on the site server screen, in the site component manager log, and in the SMSsetup.log, which is in the root of the system drive.

If you use an advertisement to distribute the ICP setup program, ensure that you monitor the status of the advertisement until the ICP installation is complete.

The ICP does not install if Terminal Services is running in execute mode on the site server. The following error message appears when Terminal Services is running in execute mode on the site server:

"Configuration Manager 2007 Setup cannot continue because of the following error: Setup has detected that Windows Terminal Server is running on this computer and the current user session is in the execute mode. You must set the current user session to the install mode in order to run Configuration Manager 2007 Setup."

For Setup to proceed in this case, you must change the user mode to install mode at the command prompt by typing change user /install.

Secondary site server ICP installation

You can upgrade secondary sites by using the Upgrade Secondary Site Wizard. The Upgrade Secondary Site Wizard is used to upgrade multiple sites at the same time. You can initiate the Upgrade Secondary Site Wizard from the Configuration Manager console by selecting the Upgrade Secondary Sites option from the Action menu when a site is selected. The Upgrade Secondary Site Wizard can transfer the necessary files, in an approximately 63-MB package for ICP1, to each site over your WAN. Transferring the files over the WAN can take a long time, depending on the link capacity that is available, so you might want to make the Configuration Manager 2007 software available at the site on CD.

If you have many sites to upgrade with the ICP, then you might want to consider automating their upgrades. This is described in the Automating the installation section in Installing International Client Packs (ICPs).

The Management Point upgrade process

All management points on the site server are upgraded when you install the ICP. When you install an ICP to a site, it typically takes less than 15 minutes to copy the files to the relevant site directories, restart the services, and copy the updated files to a management point and logon point over a 100 MB connection. The following table shows the network traffic required to apply ICPs to a management point in various scenarios.

Scenario	Network traffic
New U.S. English management point installation, no ICP	42 MB
ICP1 update of existing management point	35 MB
New ICP1 management point	48 MB
ICP2 update of ICP1 management point	72 MB

Client ICP installation

When a client starts its upgrade with a new ICP version, you can check the client status by clicking Configuration Manager in Control Panel. The Components tab of Configuration Manager indicates that the based components have changed to an install pending state. The versions of the client agents change to a pending state with a status of repair pending.

The base components take several minutes to install. The optional components take up to 60 minutes for full deployment.

As an example of the network traffic required to deploy the ICP updates to a single client, the traffic for different Configuration Manager 2007 ICPs is shown in the following table:

ICP version	Base component installation	Optional components	Client
ICP1	5.0 MB	6.9 MB	6.9 MB
ICP2	9.4 MB	11.7 MB	9.8 MB

Normally, clients are upgraded by using the same methods that are used to install them. However, Client Push Installation does not automatically upgrade existing clients.

You must plan to monitor the deployment to ensure that the project is proceeding successfully. Isolate and resolve problems while they are still small. Design and test reporting solutions during the early phases of your project and use them before you start the deployment in a production environment.

Configuration Manager 2007 version data is available from several different sources, and you can use it by employing a variety of techniques. You can choose from among the following techniques those that are appropriate to your situation:

• Try to use reporting-based monitoring techniques if you have many computers or sites, or if you want to monitor the deployment closely.
  
  
• Collect version numbers as part of hardware inventory collection if you want to enhance your reporting options, or you could check the registry entries they are stored in.
  
  
• Check the file versions on random computers, if appropriate.
  
  

If you develop reports, then create reports that address the following questions:

• Which sites have been upgraded?
  
  
• What percentage of site servers has been successfully upgraded?
  
  
• Which site servers were not upgraded?
  
  
• Which clients were not upgraded?
  
  

To enhance your reporting options, you can collect client component version numbers during hardware inventory collection. For more information, see the "Check the client component versions" section later in this chapter.

To determine the version of a file

For troubleshooting assistance, view the server logs at the sites during your upgrade.

Before you deploy an ICP at any site, consider performing a backup. For additional information about backing up your site, see Overview of Backup and Recovery. Whether or not you perform a backup at the site is determined by the following:

• The risk that the ICP installation poses to the site. In the early stages of the deployment the risk is higher than in later stages, especially if you do not thoroughly test the ICP deployment.
  
  
• The cost involved in restoring a site to a backup, or rebuilding the site, or if the ICP causes irreparable problems. This varies by site and includes the cost of the work itself and of the lack of Configuration Manager 2007 services. The most costly site to lose is typically your central site, and the least costly site to lose is a small site at the lowest levels of your hierarchy. The cost also relates to your business dependence on Configuration Manager 2007 at that site.
  
  

The only other preparations required for each site are those required by your project plan or those required by the ICP itself.

Other Resources

Tasks for International and Multi-Language Configuration Manager Clients
Deploying Configuration Manager Sites in International and Multi-Language Environments