>Even if it's possible to disable the warnings it's a bad idea to do so, those warnings are there for a good reason.
>
>There are several possibilities:
>
>1. The cert is obsolete/no longer in use. In that case it can simply be removed/deleted from your certificate store and/or detached from services such as Exchange, and the warnings will stop
>
>2. The cert is required/actively used:
>
>2a. It is about to expire. To avoid possible interruption to services it should be renewed ASAP, by default you only start getting these warnings in the last 30 days of the cert. It's relatively easy to renew a required cert. It is much more difficult to get a replacement cert for one that has already expired, and then attach that cert to the various services that require it
>
>2b. The cert has expired. Depending on its importance this can cause service failures (e.g. e-mail delivery) or will force Windows to fall back to less secure or insecure transport methods. This fallback procedure may cause timeouts or delays, so will manifest as decreased performance
>
>Maybe there are obsolete certs (#1 above) causing these warnings. If so deal with it/them. You don't want to disable these warnings because you don't want to miss legitimate warnings for required certs.

Yes, but, I really need to avoid getting those warnings. First of all, I do not want to have those records created on daily basis for the next 30 days. Also, that domain is scheduled to go by itself. So, the situation is controlled and we do not need to be reminded about it. Also, the process of renewal, handling those certificates is highly detailed and managed by other mechanisms. So, basically, I wouldn't rely on that for knowing what to do. :)

But, thanks for the info