Whenever the SMS_def.mof file is changed on a primary site server (including when SMS is upgraded, if the SMS_def.mof has changed in the newer version of SMS), SMS loads its contents into the SMS database so that Advanced Clients can request them as policy from the management point. The SMS_def.mof is also downloaded to CAPs so that Legacy Clients can acquire it. This is also done at secondary sites. Both clients download the changes during their daily client refresh cycles.
While SMS_def.mof is loaded into the SMS site database, SMS backs up the SMS_def.mof to the \SMS\data\hinvarchive folder. If the SMS_def.mof is valid, it is backed up as SMS_def.mof.bak. If an SMS_def.mof.bak already exists, SMS_def.mof.bak is first backed up as SMS_Def.mof.bk0. If an SMS_def.mof.bk0 already exists, it is first backed up as SMS_def.mof.bk1. This continues to SMS_def.mof.bk4.
If the SMS_def.mof is not valid, it is backed up as SMS_def.mof.bad.bak. If an SMS_def.mof.bad.bak already exists, SMS_def.mof.bad.bak is first backed up as SMS_Def.mof.bad.bk0. If an SMS_def.mof.bad.bk0 already exists, it is backed up as SMS_def.mof.bad.bk1. This continues to SMS_def.mof.bad.bk4.