Maintenance options in SCS 8.0

After you configure your system once, every now and then you will need to perform “maintenance” tasks on the machine. What are maintenance tasks?
Well, they include re-synching Intel® AMT’s internal clock so Kerberos will keep working; re-issuing any certificates that are about to expire; re-defiing administrator passwords, etc.
SCS 8 allows you to perform maintenance operations both from the local system, using the configurator, and remotely, using the RCS (for those working with a database) by defining a maintenance job to run on multiple systems. You just use the maintenance command and define which of the maintenance tasks you want performed.

But what if you don’t want to specify which tasks should be done? Maybe you don’t want to keep track of when your certificates are going to expire, and want SCS to do that for you? Exactly for that reason, we in the SCS team created the “Automatic maintenance” option. This option will review when the last time a task was performed, or when the object is going to expire, and will act accordingly. All the user has to do is to make sure automatic maintenance happens once every month or two, and SCS will take care of everything else.

Automatic maintenance is available both in non-DB mode (through the configurator) and in DB-mode (configurator and RCS). It is also available for all generations of Intel AMT supported by SCS.

P.S. Just to clarify: regular maintenance and automatic maintenance on RCS side are not identical to what is done by the configurator. The configurator has the added capability of performing “network synch” – it will make sure that the Intel AMT’s hostname and IP are set according to the policy the user defines.

For more complete information about compiler optimizations, see our Optimization Notice.