For reminders of those kinds of things, we've made a shared mailbox for a team calendar in Exchange, and set up meeting reminders in it that with members of our team as attendees. We also use that for keeping track of on-call rotation, vacation days and other things needing reminders. Everyone on the team has delegate access on the calendar, so they can set up reminders as necessary.
Other than that, if you have a tools box that's permanent, I could see a scheduled task that sends emails with a batch file, or some other home-grown solution. Kurt On Thu, Jun 16, 2016 at 9:17 AM, Jonathan Raper <[email protected]> wrote: > Thanks, but this ISN’T just about certs. Monitoring is not the solution I am > looking for. We’re also looking to manage reminders for non technical items, > like other renewals, contracts, etc. > > > > Jonathan > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Neil Standley > Sent: Thursday, June 16, 2016 12:03 PM > To: [email protected] > > > Subject: [NTSysADM] RE: Reminders for SSL certs (and other things) > > > > The PRTG free license comes with 100 sensors, and if you’re monitoring > Windows boxes you can install remote probes to monitor all sorts of things. > Otherwise you can monitor using SNMP. > > > > You just need a system to run it and access to the resource you wish to > monitor. > > > > > > > > Neil Standley > Cascadia Infotek > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Jonathan Raper > Sent: Thursday, June 16, 2016 8:45 AM > To: [email protected] > Subject: [NTSysADM] RE: Reminders for SSL certs (and other things) > > > > Unfortunately it is not that simple. Multiple sites, and some are internal > certs for dev environments, some are on network equipment that is internal, > one is on a hosted environment in a co-lo that is purely internal, but we > don’t manage the system, only the cert…. > > > > And we have a management system in place (Zenoss), and it does alert on some > of the certs, but only if the device is monitored/managed. Some devices we > do not want monitored for various reasons….but when the cert expires, it’s a > problem. Unfortunately management won’t justify the expense and overhead of > 1-3 years of monitoring for an issue that only crops up every 1 to 3 years…. > > > > Thanks, > > > > Jonathan > > From: [email protected] [mailto:[email protected]] > On Behalf Of Brian Desmond > Sent: Thursday, June 16, 2016 9:20 AM > To: [email protected] > Subject: [NTSysADM] RE: Reminders for SSL certs (and other things) > > > > You might look at how you could centralize where these certs are installed > (e.g. a load balancer/reverse proxy) so you only have one place to check as > opposed to having things scattered around. > > > > Thanks, > > Brian Desmond > > > > w – 312.625.1438 | c – 312.731.3132 > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Jonathan Raper > Sent: Wednesday, June 15, 2016 12:40 PM > To: [email protected] > Subject: [NTSysADM] Reminders for SSL certs (and other things) > > > > Hi all, > > > > We’ve been bitten by an internal cert or two expiring that caught us off > guard. We’re rying to come up with a way to have centrally managed reminder > system in place to make sure this doesn’t happen again. This is for a > large-ish network with a handful of people who could be managing this at any > given time. > > > > An Excel spreadsheet just doesn’t scale well for this, and Outlook tasks > seems kind of clumsy. > > > > Obviously paid certs you generally get a reminder because GoDaddy wants the > revenue, and Web server certs generate an event in the event log, but not > every SSL cert is going to generate an event…..and not every cert is a paid > cert…. > > > > We also have some other events and contracts that we’d like reminders for – > so this isn’t exclusive to SSL certs, though that is a driving factor. > > > > How are you all handling this? An application? A web-based “aaS” reminder > system of some sort? > > > > Thanks, > > > > Jonathan > > NOTE: This message and any attachments is intended solely for the use of the > individual or entity to which it is addressed and may contain information > that is non-public, proprietary, legally privileged, confidential, and/or > exempt from disclosure. If you are not the intended recipient, you are > hereby notified that any use, dissemination, distribution, or copying of > this communication is strictly prohibited. If you have received this > communication in error, please notify the original sender immediately by > telephone or return email and destroy or delete this message along with any > attachments immediately. > > NOTE: This message and any attachments is intended solely for the use of the > individual or entity to which it is addressed and may contain information > that is non-public, proprietary, legally privileged, confidential, and/or > exempt from disclosure. If you are not the intended recipient, you are > hereby notified that any use, dissemination, distribution, or copying of > this communication is strictly prohibited. If you have received this > communication in error, please notify the original sender immediately by > telephone or return email and destroy or delete this message along with any > attachments immediately. > > NOTE: This message and any attachments is intended solely for the use of the > individual or entity to which it is addressed and may contain information > that is non-public, proprietary, legally privileged, confidential, and/or > exempt from disclosure. If you are not the intended recipient, you are > hereby notified that any use, dissemination, distribution, or copying of > this communication is strictly prohibited. If you have received this > communication in error, please notify the original sender immediately by > telephone or return email and destroy or delete this message along with any > attachments immediately.
