How to change the time limit a Client Security or Server Security considers update databases to be old?

Issue:

How to change the time limit for Client Security and Server Security how quickly they consider the malware definition and engine updates (databases) to be old or very old? 

For example, if we have Client Security or Server Security installed in an isolated or offline environment, we do not want to have the user interface warning of old or very old databases as quickly. 

Resolution:

The time limit in days for how quickly a Client Security or Server Security client considers update databases to be old can be changed from the Policy Manager policy settings:

1. Log in to the Policy Manager Console
2. Select a host or policy domain from the domain tree
3. Open the Settings tab
4. Navigate to Windows > Centralized management 
5. In the Automatic updates section, modify the days value for:
   1. Time limit for considering update databases old (in days)
   2. Time limit for considering update databases very old (in days)
6. Distribute the policy (Ctrl + D)

The default value for old is 7 days, while the default value for very old is 30 days.