Enterprise deployment sequence: upgrade the administration server last

Here is a deployment sequence in which you upgrade the administration server for the Domino domain last.

About this task

This is provided as an example for you to consider and adapt for your environment. For example, although the steps suggest ordering upgrades by server function, in some environments you may want to factor in geographic location.
Note: In addition to these steps, keep in mind the information in Mitigating the time required to rebuild Domino directory views.

Procedure

  1. Remove all instances of the Domino directory template (PUBNAMES.NTF) from your domain(s).
  2. Configure the Domino directory replication options so that the new design can only flow in the following direction: Domino Administration Server of Domino Directory > Domino Hub Servers > Domino Spoke Servers. This ensures there is no backflow of Domino directory changes as you upgrade first Domino Spoke servers, then Domino Hub servers, and finally the Domino Administration server of the Domino directory.
    1. On the administration server, open the names.nsf file using the Domino Administrator client. Click File > Replication > Options for this application > Advanced tab.
      In the When computer field, ensure the administration server's name is present.
      In the Receives from field, select Any server.
      Uncheck the box Design elements then click OK.
    2. Open the names.nsf replica on the hub servers.
    3. Click File > Replication > Options for this application. Click the Advanced tab.
    4. Next to When computer, ensure that you see the hub server instance you are modifying. Next to Receives from, select the administration server from the list. In the Receive these elements from other replicas section, make sure the Design elements checkbox is selected.
    5. Open the names.nsf replica on the spoke servers.
    6. Click File > Replication > Options for this application. Click the Advanced tab.
    7. Next to When computer, ensure that you see the spoke server instance you are modifying. Next to Receives from, select the hub server from the list. In the Receive these elements from other replicas section, make sure the Design elements checkbox is selected.
  3. Upgrade the Domino Administrator clients that you use to administer Domino.
  4. Upgrade Domino SMTP servers.
  5. Upgrade Domino mail servers.
  6. Upgrade Domino Resource and Reservations (R&R) servers.
  7. Upgrade Domino application and web servers.
  8. Upgrade third-party and companion product servers.
  9. Upgrade Domino hub servers.
  10. Upgrade the Domino administration server of the Domino domain, including upgrading the Domino directory design.
  11. If you use Notes, upgrade the general population to the new Notes version.
  12. Replace the design of mail files with mail<ver>.ntf for the new version.
  13. Upgrade the On-Disk Structure (ODS) of Domino applications to the latest ODS format.

What to do next

Note: Steps 11 - 13 are important for taking advantage of the new features in the release. Depending on the size of your Notes client base, communication needed, training required, etc. these steps are often carried out weeks after the server upgrades. This approach allows time for production testing before rolling out to hundreds or thousands of users.