Currently we are implementing a config to alert via smtp when a warning happens on the clients. My question is what happens if 3000 clients can't connect to the server because it goes down over the weekend. I am concerned about exchange.
Hello aluminex, If you set the verbosity high, you can have it only send emails when an infection is detected. That way if there are errors getting updates, they won't all send emails and overload your mail server.
Wayne, Are you sure? My event logs says the error getting updates are critical warnings.. screenshot http://i50.tinypic.com/313q2qa.jpg
The errors in your screenshot are critical warnings because they are not update errors that will clear once the client does update. The client will show a critical warning if it has not updated in a long time or if there was a problem with updating that will most likely require intervention. Many times if you see these errors, clearing the update cache will most likely be necessary on that client.
Hi Wayne, I seem to recall a very serious problem with this a while back, so... Don't you think this should happen automatically? Say, after x failed updates? Manually clearing the cache on 3000 clients doesn't sound like much fun.
I would have to agree with that... especially when technically for us this task should be shifted to a separate department and it may never get done.
You should never have that many clients with errors like those. If that does happen, there is most likely an issue somewhere other than the clients or the mirror. If the server goes down, the clients will keep checking for updates and will fail silently for a period of time until they are a couple of days out of date and then will start showing a notification to the user as well as sending an email.