Forum Discussion
Sounds great, will check it out! I wrote something similar for interfaces way back for similar reasons -- LM limitations and no clear focus on nuts and bolts stuff like this. My largest remaining annoyance on that is we use patterns via properties that examine the interface description so we can disable monitor and/or alert for interfaces based on description patterns (e.g., "Workstations"). However, because AD will skip interfaces that are operDown you cannot change the description after it is down and have the script make the necessary change. You could change the DS to discover operDown interfaces always, but that would be ridiculous in general. I filed a F/R to allow updating some fields (like the description) for instances already discovered, but AFAIK it has received no attention. Just added to our repo under GPL: https://github.com/willingminds/lmapi-scripts
Related Content
- 7 months ago