Example Workflows to Preserve Site Security Data - Metasys - LIT-12011964 - Software Application - System Configuration Tool - 13.2

Metasys SCT: System Configuration Tool Help

Brand
Metasys
Product name
System Configuration Tool
Document type
User Guide
Document number
LIT-12011964
Version
13.2
Revision date
2020-01-21
Language
English

Supervisory Engine is the Site Director

Follow these steps when you upgrade a supervisory engine that is the Site Director.

  1. Make password definition changes online at the Site Director (which is the supervisory engine).

  2. Upload the Site Director device with SCT (which includes the security database).
  3. Using Security Copy in SCT, copy the security database from the Site Director to all other devices with SCT. (This action restores the backed-up security database to a device or devices that you then upload in the next step.)
  4. Upload all devices to preserve objects and security databases with SCT.
  5. Create a backup of the archive database.
  6. Locate the backup file just created.
  7. Zip the backup file and append the current date to its name (for example, MyADS_20130712.zip).
  8. Copy the zipped backup file to external media.

ADS/ADX/ODS as Site Director with SCT and SMP User Interface Installed

Follow these steps when the ADS/ADX/ODS is the Site Director and the SCT and SMP UI are installed on the ADS/ADX/ODS computer.

  1. Make password definition changes using the SMP UI.

    Note: SCT and SMP now have separate databases when installed on the same computer or server.
  2. Upload the Site Director device (which includes the security database) with SCT.
  3. Using Security Copy in SCT, copy the security Site Director database to one of the child network devices.
  4. Upload all devices to preserve objects and security databases with SCT.
  5. Create a backup of the archive.
  6. Locate the backup file just created.
  7. Zip the backup file and append the current date to its name (for example, MyADS_20130712.zip).
  8. Copy the zipped backup file to external media.

Supervisory Device with Locally Inaccessible Security Database (NAE35/45/NCE25 Only)

Follow these steps when a supervisory engine is accessible from the ADS/ADX/ODS Site Director, but inaccessible locally (that is, cannot log in to the engine directly because of a Security database issue). These steps apply to NAE35s, NAE45s, and NCE25s at Release 5.2 only.

  1. Try to log into the Release 5.2 engine directly using the MetasysSysAgent user.

  2. If the login fails, reset the Release 5.2 engine.
  3. Using SCT, use Security Copy to download a small security database into the engine with SCT Security selected as the source.
  4. Try to log into the Release 5.2 engine directly using the MetasysSysAgent user.
  5. If the login works, go to Step 7. If the login fails, reimage the Release 5.2 engine, then go to Step 6 of these instructions. For details on reimaging a device, refer to the NAE/NIE Update Tool Online Help PDF (LIT-12011524).
  6. If your engine is to remain at Release 5.2, use Security Copy to download a small security database into the engine, then go to Step 7. If your engine is being upgraded to a later release, follow the site policy for security.
  7. Upload the engine with the small security database with SCT.
  8. Using Security Copy in SCT with SCT Security selected, copy the security database from the engine to all other engines, which duplicates the small set of users to all engines. (This action restores the backed-up security database to a device or devices that you then upload in the next step.)
  9. Upload all devices to preserve objects and security databases with SCT.
  10. Create a backup of the archive.
  11. Locate the backup file just created.
  12. Zip the backup file and append the current date to its name (for example, MyADS_20130712.zip).
  13. Copy the zipped backup file to external media.