As an added note, Custom Fields on the End of Support web page show the dates backwards. In other words the custom fields show YYYY/MM/DD and then a T and the time, while the non-custom property files, EOL and EOS, show mm/dd/yyyy and no time. I’ve put a ticket in to support on this. The odd thing about it is when you look at these custom fields in the Custom Property editor in NPM they dates show correctly
From: Norton, Jeff
Sent: Wednesday, August 28, 2013 10:24 AM
To: 'jive-466250685-51a-2-4iuc@solarwinds.hosted.jivesoftware.com'
Subject: RE:
- Give us Feedback on the New End-of-Life Feature
Ok so while this works it is extremely cumbersome in that the dates have to be entered in two places. I cannot enter the custom field dates on the same screen that I enter the EOL/EOS dates. Somehow Solarwinds needs to allow custom fields to be assigned to specific functions such as life cycle management. More so than just nodes, interfaces, etc