Inside OCS » Upgrading

Lync & OCS Migration Top 10

Curtis Johnstone — Tue, 11 Jan 2011 20:58:18 +0000

Here are my Top 10 quick frequently-needed facts when you are first considering a Lync 2010 migration from OCS 2007 R2 (or if you are considering co-existence).

1. Lync 2010 Servers Can Coexist with OCS 2007 R2 Servers (in an OCS 2007 R2 Deployment)

• They can coexist in the same AD Forest and AD Domain, but not in the same OCS 2007 R2 Pool.

• Lync Server 2010 can coexist with OCS 2007 servers also, but it CANNOT coexist in an OCS deployment with BOTH OCS 2007 and OCS 2007 R2 servers. If you have a mixed OCS R1 and R2 environment, you need to finish your R2 upgrade first.

2. An Inside-Out Lync Deployment Approach is Generally Recommended

• For example, in an existing OCS 2007 R2 deployment, the internal Lync server pilot pool would be deployed first, followed by the Lync Edge Server and Director, etc…

3. Side-by-Side is the Only Supported “Upgrade” Path

• There is no ability to do an in-place upgrade of an existing OCS 2007 R2 server.

• Users can be moved from the OCS 2007 R2 server /pool to the Lync 2010 server/pool with the management console.

4. Using the Lync 2010 Client against an OCS 2007 R2 Server is not Supported.

• Using a legacy Communicator 2007 R2 client against a Lync 2010 server IS supported.

5. The Lync 2010 Client Cannot Run side-by-side with Communicator 2007 R2.

• If you install the Lync client on a client with Communicator 2007 R2 installed, it silently removes Communicator 2007 R2. It does keep registry settings such as those in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator.

6. At this time Lync Server 2010 (and OCS 2007 R2) Databases are NOT supported on SQL 2008 R2.

• See http://blogs.technet.com/b/toml/archive/2010/11/10/ocs-2007-r2-lync-server-2010-and-sql-server-versions.aspx for more information.

• This TechNet article details the supported SQL Servers for the Lync monitoring server role: http://technet.microsoft.com/en-us/library/gg413054.aspx

7. The Lync Edge and Lync Director should be Deployed in Parallel

• You should not mix Lync and OCS versions of the Edge and the Director role – they should be upgraded (or deployed in parallel) at the same time.

• A OCS 2007 R2 Edge is supported with a Lync Server 2010 pool.

• A Lync Server 2010 Edge is NOT fully supported against an OCS 2007 R2 Pool.

• See Chapter 6 – Planning for External User Access.doc – of the Microsoft Lync Server 2010 Planning Guide for more information.

8. The Lync Edge and Lync Mediation server should be Deployed in Parallel

• This is not documented well, but if you are using enterprise voice, you should not mix the Lync and OCS versions of the Edge and Mediation roles.

9. The Topology Builder or the Lync Management Shell can be used to Merge the OCS Topology into Lync

• From the Topology Builder, use the Merge Topology Wizard in the right-hand Tasks Pane.

• In the Lync Management Shell, use the Merge-CSLegacyTopology and the Import-CSLegacyConfiguration cmdlet’s. See the Import-CsLegacyConferenceDirectory cmdlet if you have OCS 2007 R2 conferencing directories.

10. The Lync and OCS Administration Tools must be used with their Respective Server Version

• With the exception that you can view a read-only copy of your OCS deployment in the Lync Topology.

• See Lync and OCS Administration Tools (http://blog.insideocs.com/2010/12/10/lync-and-ocs-administration-tools/) for more information.

Lync 2010 Migration Resources

1. Microsoft TechNet Guide: Migration from Office Communications Server 2007 R2 to Lync Server 2010

2. Microsoft TechNet Guide: Migration from Office Communications Server 2007 to Lync Server 2010

3. Microsoft Video: Migrating from Office Communications Server 2007 to Lync Server 2010

4. Microsoft Lync Server 2010 Planning Guides: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da9fa26-e032-4dcf-b487-da916ddc508f

Here are 10 frequently-needed facts when you are first considering a Lync 2010 migration from OCS 2007 R2 (or if you are considering co-existence):

1. Lync 2010 Servers Can Coexist with OCS 2007 R2 Servers (in an OCS 2007 R2 Deployment)

They can coexist in the same AD Forest and AD Domain, but not in the same OCS 2007 R2 Pool.
Lync Server 2010 can coexist with OCS 2007 servers also, but it CANNOT coexist in an OCS deployment with BOTH OCS 2007 and OCS 2007 R2 servers. If you have a mixed OCS R1 and R2 environment, you need to finish your R2 upgrade first.

2. An Inside-Out Lync Deployment Approach is Generally Recommended

For example, in an existing OCS 2007 R2 deployment, the internal Lync server pilot pool would be deployed first, followed by the Lync Edge Server and Director, etc…

3. Side-by-Side is the Only Supported “Upgrade” Path

There is no ability to do an in-place upgrade of an existing OCS 2007 R2 server.
Users can be moved from the OCS 2007 R2 server /pool to the Lync 2010 server/pool with the Lync management tools (the Lync Control Panel or Lync Management Shell) after the OCS topology has been merged with your Lync topology (see #9 below).

4. Using the Lync 2010 Client against an OCS 2007 R2 Server is Not Supported.

Using a legacy Communicator 2007 R2 client against a Lync 2010 server IS supported.

5. The Lync 2010 Client Cannot Run side-by-side with Communicator 2007 R2.

If you install the Lync client on a client with Communicator 2007 R2 installed, it silently removes Communicator 2007 R2. It does keep registry settings such as those in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator.

6. There is a 32-bit and 64-bit Version of the new Lync Client

This is not entirely true. The “64-bit” version is actually just a 64-bit installer wrapping a 32-bit version.
The 64-bit installer version integrates with the 32-bit version of Microsoft Office.

7. The Lync Edge and Lync Director should be Deployed in Parallel

You should not mix Lync Server and OCS versions of the Edge and the Director role – they should be upgraded (or deployed in parallel) at the same time.
A OCS 2007 R2 Edge is supported with a Lync Server 2010 pool.
If your users are experiencing a “Presence Unknown” for federated and PIC contacts after you have recently configured your Lync pool to use the existing OCS 2007 R2 Edge, consider rebooting the OCS 2007 R2 Edge. See Quick Tip – External Contacts with Lync Coexistence for more information.
A Lync Server 2010 Edge is NOT fully supported against an OCS 2007 R2 Pool.
See Chapter 6 – Planning for External User Access.doc – of the Microsoft Lync Server 2010 Planning Guide for more information.

8. The Lync Edge and Lync Mediation server should be Deployed in Parallel

This is not well documented, but if you are using enterprise voice, you should not mix the Lync and OCS versions of the Edge and Mediation roles.

9. The Topology Builder or the Lync Management Shell can be used to Merge the OCS Topology into Lync

From the Topology Builder, use the Merge Topology Wizard in the right-hand Tasks Pane.
In the Lync Management Shell, use the Merge-CSLegacyTopology and the Import-CSLegacyConfiguration cmdlet’s. See the Import-CsLegacyConferenceDirectory cmdlet if you have OCS 2007 R2 conferencing directories.

10. The Lync and OCS Administration Tools must be used with their Respective Server Version

With the exception that you can view a read-only copy of your OCS deployment in the Lync Topology.
See Lync and OCS Administration Tools (http://blog.insideocs.com/2010/12/10/lync-and-ocs-administration-tools/) for more information.

Note: one of the original Top 10 used to be that Lync did not support SQL 2008 R2 for it’s databases. As of April 2011, Lync is fully supported with SQL 2008 R2: http://blogs.technet.com/b/nexthop/archive/2011/04/20/lync-server-2010-support-for-sql-2008-r2.aspx.

Lync 2010 Migration Resources

InsideOCS - Migrating your OCS Federated Partner Settings to Lync

Microsoft TechNet (excellent short video on the basics) - Migrating from Office Communications Server 2007 R2 to Lync Server 2010

Microsoft TechNet - Migration from Office Communications Server 2007 R2 to Lync Server 2010

Microsoft TechNet - Migration from Office Communications Server 2007 to Lync Server 2010

Microsoft Video: Migrating from Office Communications Server 2007 to Lync Server 2010

Microsoft Lync Server 2010 Planning Guides: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da9fa26-e032-4dcf-b487-da916ddc508f

Updates to Office Live Meeting and the Outlook Conferencing Add-In

Curtis Johnstone — Wed, 04 Aug 2010 02:07:47 +0000

The July, 2010 updates to the Office Live Meeting client and the Outlook Conferencing Add-In are available. This is in addition to the previously released July 2010 Updates to Communicator and OCS Server (Cumulative Update 6).

Office Live Meeting Window Client

Download the Microsoft Office Live Meeting 2007 client (http://office.microsoft.com/en-us/help/download-the-microsoft-office-live-meeting-2007-client-HA010173383.aspx). This update installed version 8.0.6362.190 from the last update 8.0.6362.187.
Description of the update package for the Windows-based Live Meeting 2007 client: July 2010 (http://support.microsoft.com/kb/2029026)

Conferencing Add-in for Microsoft Office Outlook

Download the Conferencing Add-in for Microsoft Office Outlook (http://office.microsoft.com/en-us/help/redir/XT101961398.aspx?CTT=5&origin=HA010236890)
Description of the update for the Live Meeting Conferencing Add-in for Outlook: July 2010 (http://support.microsoft.com/kb/2029027)

OCS and .NET Framework 4.0 Issues

Curtis Johnstone — Thu, 29 Jul 2010 20:19:38 +0000

A quick update on the reported issues with installing OCS 2007 R2 on machines that have .NET 4.0.

In a nutshell, if you try to install any of the OCS 2007 R2 roles or Group Chat Server, on a server that has the .NET 4.0 Framework installed along side the .NET Framework 2.0 or .NET Framework 3.5 Service Pack 1 (SP1), you’ll get an error.

A Knowledge Base article was released this morning that provides more details and gives a workaround: You cannot install Office Communications Server 2007 R2, Unified Communications Managed API 2.0 Core Redist or Office Communications Server 2007, Unified Communications Managed API v1.0 Redist.

July 2010 Updates to Communicator and OCS (Cumulative Update 6)

Curtis Johnstone — Fri, 23 Jul 2010 16:28:24 +0000

There has been a new round of updates for Communicator 2007 R2, OCS 2007 R2, and OCS 2007 R2 Group Chat – known as Cumulative Update 6 (CU6).

** Sept 2, 2010 Update **: Microsoft has temporarily removed the Cumulative Update 6 (CU6) until an issue with the Response Group Service can be fixed. See News: Office Communications Server 2007 R2 Response Group Service Fails After Applying July 2010 Cumulative Updates for more information. The corresponding Microsoft Knowledge Base article is KB 2401878 and can be viewed here: http://support.microsoft.com/kb/2401878.

** July 30, 2010 Update **: It appears that the reported CU6 problems have been attributable to either the back end database update not being installed first, or the OCS 2007 R2 .NET Framework 4.0 issue. Having said that, there was at least one report (on this blog) of the “mismatch error” even after the database install was applied first.

** July 26, 2010 Update **: There have been several reports of problems (failure of the Front End Service to start) after applying the CU6 updates on the server. Consider holding off applying this update until more information is known. It is important to install the CU 6 update to the back end database role first (see Description of the cumulative update package for Office Communications Server 2007 R2 database: July, 2010). So far, the problems appear to be related to this, but more information to come.

Client Updates

Communicator 2007 R2:

The July, 2010 update for Communicator 2007 R2 can be found here: Description of the cumulative update package for Communicator 2007 R2: July 2010. This update brings the Communicator version up to 3.5.6907.206 from the last update in April 2010 (3.5.6907.196).
Note: the links to the knowledge base article for the individual fixes do not work right now, or not ready yet, on the Microsoft support site.
The update can be downloaded here.

Communicator 2007 R2 Phone Edition:

The July, 2010 update for Communicator 2007 R2 can be found here: http://support.microsoft.com/kb/2267962/.
The update can be downloaded here.

Communicator 2007 R2 Mobile:

This was update was released about 2 weeks ago, but the knowledge base article has been updated. The description can be found here: http://support.microsoft.com/kb/969816.
You can download the Smartphone update here.
You can download the Pocket PC packager here.

OCS 2007 R2 Group Chat Client:

The July 2010 update can be found here: Description of the update for Office Communications Server 2007 R2 Group Chat Client: July 2010.
The update can be downloaded here.

Server Updates

OCS 2007 R2 Server:

Note: the update for the SE/EE Back End Database is here: Description of the cumulative update package for Office Communications Server 2007 R2 database: July, 2010. This update (OCS2009-DBUpgrade.msi) SHOULD BE RUN FIRST.
All of the Cumulative 6 server updates can be found here: Updates for Communications Server 2007 R2.
The updates can be downloaded here.
It looks like the update includes new hotfixes for the following server roles: Audio/Video Conferencing, Web Conferencing Server, Core Components, Communicator Web Access, Conferencing Attendant, Standard/Enterprise edition Server Back End, and the UCMA Managed API 2.0 Core Redist 64-bit.
Note: the links to the knowledge base article for the individual fixes do not work right now, or not ready yet, on the Microsoft support site.

OCS 2007 R2 Group Chat Server:

The Cumulative 6 updates for the Group Chat Server can be found here: Update package for Office Communications Server 2007 R2 Group Chat Server: July 2010.
The Group Chat Server update can be downloaded here.

OCS 2007 R2 Group Chat Admin Tool:

The update can be found here: Description of the update for the Office Communications Server 2007 R2 Group Chat Administration Tool: July 2010.
The update can be downloaded here.

There has been a new round of updates for Communicator 2007 R2, OCS 2007 R2, and OCS 2007 R2 Group Chat – known as Cumulative Update 6 (CU6).

Client Updates

Communicator 2007 R2:

• The July, 2010 update for Communicator 2007 R2 can be found here: Description of the cumulative update package for Communicator 2007 R2: July 2010. This update brings the Communicator version up to 3.5.6907.206 from the last update in April 2010 (3.5.6907.196).

• Note: the links to the knowledge base article for the individual fixes do not work right now, or not ready yet, on the Microsoft support site.

• The update can be downloaded here.

Communicator 2007 R2 Phone Edition:

• The July, 2010 update for Communicator 2007 R2 can be found here: http://support.microsoft.com/kb/2267962/.

• The update can be downloaded here.

OCS 2007 R2 Group Chat Client:

• The July 2010 update can be found here: Description of the update for Office Communications Server 2007 R2 Group Chat Client: July 2010.

• The update can be downloaded here.

Server Updates

OCS 2007 R2 Server:

• The Cumulative 6 updates can be found here: Updates for Communications Server 2007 R2.

• The updates can be downloaded here.

• It looks like the update includes new hotfixes for the following server roles: Audio/Video Conferencing, Web Conferencing Server, Core Components, Communicator Web Access, Conferencing Attendant, Standard/Enterprise edition Server Back End, and the UCMA Managed API 2.0 Core Redist 64-bit.

• Note: the links to the knowledge base article for the individual fixes do not work right now, or not ready yet, on the Microsoft support site.

OCS 2007 R2 Group Chat Server:

• The Cumulative 6 updates for the Group Chat Server can be found here: Update package for Office Communications Server 2007 R2 Group Chat Server: July 2010.

• The Group Chat Server update can be downloaded here.

OCS 2007 R2 Group Chat Admin Tool:

• The update can be found here: Description of the update for the Office Communications Server 2007 R2 Group Chat Administration Tool: July 2010.

• The update can be downloaded here.

Future OCS Licensing Changes

Curtis Johnstone — Mon, 26 Apr 2010 18:22:57 +0000

Thanks to Tommy Clarke’s blog post for alerting me to this.

Microsoft recently released a licensing brief (Base and Additive Client Access Licenses: An Explanation) which details future licensing changes upcoming in the next release of OCS (OCS Wave 14).

Here is a summary of the key changes:

1) A new OCS Voice CAL:

Will include the OCS Wave 14 voice capabilities plus some of the voice functionality in today’s OCS 2007 R2 Enterprise CAL (ECAL).
Will be additive on top of the OCS Wave 14 Standard CAL.
Can be licensed with or without the OCS Wave 14 Enterprise CAL.
Will not be included in the Enterprise CAL when Wave 14 launches.
Will include new voice capabilities that will enable “Enterprise Ready Voice” for future releases of OCS (beyond Wave 14).

2) The OCS Wave 14 Enterprise CAL price will decrease to reflect the move of the voice functionality to the new OCS Voice CAL.

3) Will my current OCS Enterprise CAL give me access to the new OCS Voice CAL?

If you purchased your existing OCS Enterprise CAL after July 1, 2009 and before the release of OCS Wave 14, and your Software Assurance was maintained, you will have the equivalent access rights to the new OCS Voice CAL. You will then need to renew to OCS Voice CAL separately at your first renewal after the OCS Wave 14 launch.
If you purchased your existing OCS Enterprise CAL before July 1, 2009 or did not buy or maintain Software Assurance, you will need to separately purchase the new OCS Voice CAL.

More information about OCS Wave 14 can be found here: Microsoft Announces Microsoft Communications Server “14”.

OCS 2007 R2 Support for Windows Server 2008 R2

Curtis Johnstone — Tue, 30 Mar 2010 19:47:00 +0000

In case you missed it, Microsoft recently released a support article which details a supported scenario for:

1) Installing OCS 2007 R2 on a Windows Server 2008 R2 server.

2) Installing OCS 2007 R2 into a Windows Server 2008 R2 Active Directory (i.e. at least one DC was upgraded to Windows Server 2008 R2).

Prior to this, OCS 2007 R2 was not supported on a Windows 2008 R2 operating system, and if you upgradeed your AD forest using Windows Server 2008 R2 x64, OCS 2007 R2 would not work correctly.

See the Knowledge Base article for the steps to follow: http://support.microsoft.com/kb/982020/.

Important Exceptions:

Upgrading your OCS 2007 R2 server from Windows 2008 to Windows 2008 R2 is not supported.

OCS 2007 R2 Group Chat Server is NOT supported on Windows 2008 R2, or in a Windows 2008 R2 domain.

In case you missed it, Microsoft recently released a support article which details a supported scenario for:

Installing OCS 2007 R2 on a Windows Server 2008 R2 server.
Installing OCS 2007 R2 into a Windows Server 2008 R2 Active Directory (i.e. at least one DC is running Windows Server 2008 R2).

Prior to this OCS 2007 R2 was not supported on a Windows 2008 R2 operating system, and if you upgradeed your AD forest using Windows Server 2008 R2 x64, OCS 2007 R2 would not work correctly.

See the Knowledge Base article for the steps to follow: http://support.microsoft.com/kb/982020/.

Important Exceptions:

Upgrading your OCS 2007 R2 server from Windows 2008 to Windows 2008 R2 is not supported.
OCS 2007 R2 Group Chat Server is NOT supported on Windows 2008 R2, or in a Windows 2008 R2 domain.

January 2010 Updates – Communicator 2007 R2 and OCS 2007 R2

Curtis Johnstone — Tue, 12 Jan 2010 04:44:16 +0000

The January 2010 updates have been released for the Office Communicator 2007 R2 Client and the OCS 2007 R2 Server.

Office Communicator 2007 R2

The download and more details can be found here: Description of the Communicator 2007 R2 cumulative update: January 2010 (KB 976135).
This update brings the Communicator 2007 R2 version number to 3.5.6907.83 (.83 from the last update which was .56).
There are 3 new Communicator 2007 R2 Client issues fixed in this hotfix:
Note: this hotifx also fixes some issues with Outlook 2010 Beta integration with Communicator on a 64-bit platform (although it is not mentioned in the KB article).

Office Communications Server 2007 R2

The download and more details can be found here: Updates for Communications Server 2007 R2 (KB 968802).
There are 4 new updates and a cumulative server update installer available.
Note the update for the database backend (Update for Standard/Enterprise edition Server Back End – KB 977349) will NOT be installed by the cumulative installer, and needs to be manually installed.
Four new OCS 2007 R2 Server issues fixed in this hotfix:

There are also updates reported on Aaron Tiensivu’s blog for the OCS 2007 R2 Group Chat server and the OCS 2007 R2 Tanjay Phone.

Happy updating .

OCS R2 32-bit Administrative Tools

Curtis Johnstone — Wed, 12 Aug 2009 14:44:21 +0000

Further to my post on OCS R2 Administrative Tools – Quick Facts, here is how to install the 32-bit version of the OCS R2 32-bit Administrative Tools.

Note: the 32-bit version is currently not supported on Windows XP; only Windows Vista SP1 (Business or Enterprise), Windows Server 2003 with SP2, and Windows Server 2008.

The 32-bit installation is available in the “\Support\i386” directory on the 64-bit media. The required pre-requisites are also located in this directory, and must be installed in the following order:

sqlncli.msi (SQL Server Native Client – contains the SQL OLE DB and SQL ODBC drivers in on native DLL)
vcredist_x86.exe (x86 VC++ 2008 redistributable)
.NET Framework 3.5 SP1 (download it here from Microsoft’s Web Site or use \Setup\amd64\dotnetfx35.exe)
OCSCore.msi (OCS 2007 R2 Core Components)
AdminTools.msi (Office Communications Server 2007 R2 Administrative Tools)

Note: the 64-bit Deployment Setup Wizard will install these prerequisites automatically. If you want to install the tools without running the Deployment Wizard, the AdminTools.msi can be found in the \Setup\amd64\Setup directory.

If you do not install the prerequisites in the order above, you’ll receive error messages such as “Microsoft Office Communications Server 2007 R2, Administrative Tools installation requires that a compatible version of Core Components is installed”. The OCS 2007 R2 Administrative Tools installation requires that a compatible version of the Core Components is installed.

An OCS 2007 R1 note – I ran across this known issue if you are having trouble getting the OCS Communications tab to appear in Active Directory Users & Computers (ADUC) on a x64 bit machine. Remember OCS 2007 R1 was only 32-bit, so to get the Communications tab to show up you need to start ADUC in 32-bit mode: dsa.msc -32.

Missing Share Desktop Feature in Communicator R2

Curtis Johnstone — Sun, 19 Jul 2009 15:42:34 +0000

Recently I have been involved in several cases involving users on Windows XP SP3 machines who have upgraded to the Communicator R2 client and do not have the Share Desktop feature available in Communicator R2. The whole “Share” option is completely missing from the right-click menu on a user contact!

In all cases installing MSXML 6.0 SP1 and restarting Communicator R2 has resolved the issue.

As per the Office Communications Server 2007 R2 Client System Requirements the minimum Operation System requirements for Windows XP is only SP2, but it appears the Share feature has a dependency on a more recent version of MSXML (or it is getting uninstalled during the upgrade process). Despite no mention of this prerequisite in the Communicator R2 Deployment Guide, Release Notes, or System Requirements, I found a TechNet article stating that indeed MSXML 6.0 is a requirement for Communicator R2.

Desktop Sharing is one the best new features of Communicator R2 (see my previous post: Communicator R2 Desktop Sharing Rocks!).

OCS R2 Administrative Tools – Quick Facts

Curtis Johnstone — Tue, 16 Jun 2009 12:26:30 +0000

As many OCS 2007 R1 deployments move to OCS 2007 R2, mixed deployments with both OCS R1 and OCS R2 pools are becoming more common.

Here are some notable reminders about the OCS R2 Administrative Tools in a mixed deployment that you should know about:

The R1 and R2 Admin Tools cannot be installed side-by-side together on the same machine.
The R1 and R2 Admin Tools can only administer their respective OCS server versions). For example, the R2 Administrative Tools cannot be used against an R1 pool.
The R2 Admin Tools are not supported on a Windows XP O/S. Windows 2003 SP2, Windows 2008, and Windows Vista SP1 are supported. For Vista and Windows 2008 there are some pre-requisites you must install first (follow the links when you go to install).
Although OCS 2007 R2 is only supported on a 64-bit platform, the 32-bit Administrative Tools are available in the \Support\i386 directory of the R2 installation media.
Active Directory Users & Computers is not automatically extended for R2 management (e.g. Communications Tab) like the OCS R1 administrative tools did.
The OCS 2007 R2 administrative tools are no longer installed on the OCS server itself as part of the regular installation (except for Group Chat). You can manually install them by using the same Deployment Wizard that you use to install Office Communications Server 2007 R2 (there is a hyperlink in the right-pane of the wizard).
If you want to install the R2 admin tools without the Deployment Wizard, they are located in the \Setup\amd64\Setup directory.
When Microsoft releases updates to OCS 2007, usually this includes updates to the administrative tools and the core components, so stay up-to-date.
Note: the OCS admin tools require a compatible version of the Core Components (OCSCore.msi) be installed.