Page 1 of 3

Technology Manager Feature Ideas

Posted: Mon Jan 07, 2013 2:59 pm
by clingmann
Thinking as a community we could provide some feedback on features that would be helpful for inclusion in tm.lds.org. Since the only category now is Firewalls, starting there.

Firewalls:
  • Ability to email a user defined list of email addresses when a firewalls "online status" changes to down
  • Ability to view number of active/used DHCP leases
  • Ability to view DHCP Leases by MAC
  • Assign static DHCP reservations
  • Ability to select and block MAC addresses from receiving an IP
  • Ability to view Device system log to assist in troubleshooting
  • Access Point Status, Connected/Historical/Up-Down

Re: Technology Manager Features Request

Posted: Mon Jan 07, 2013 3:25 pm
by rolandc
Ability to remote reboot the router
Ability to Disable all WiFi
Ability to have remote access

Re: Technology Manager Features Request

Posted: Mon Jan 07, 2013 4:31 pm
by brogers
- historical record of bandwidth used
- ability to receive / view messages from "CHQ / IS Dept"
- visibility into wireless configuration
- visibility into wireless channels used
- ability to do site survey from a given WAP

Re: Technology Manager Features Request

Posted: Mon Jan 07, 2013 4:48 pm
by pingsteve
* Ability to disable wifi during stake conference broadcasts
* Ability to change wifi to less-used channels
* Ability to give priority to streaming media

Re: Technology Manager Features Request

Posted: Fri Mar 29, 2013 1:45 pm
by rogerscr
-Ability to set permanent #1 priority to stream.lds.org (or as appropriate for Webcast transmission/reception)
-Ability to reduce priority of/lock out non-lds.org sites

Moderator note

Posted: Fri Mar 29, 2013 2:37 pm
by jdlessley
Everyone should note the lack of any posts from church employees to this thread. If your intent in posting your feature requests is to provide feedback for the tool/site, you may want to consider using the feedback link on the LDS.org home page and many other, but not all, pages with the link. I do not know if the TM site has a feedback link. If it does not then any other LDS.org page with the link will suffice.

These forums are primarily user-to-user support. But do not expect your feature requests will reach those who have authority or the ability to make the changes requested.

Re: Moderator note

Posted: Fri Mar 29, 2013 2:44 pm
by mfmohlma
jdlessley wrote:I do not know if the TM site has a feedback link.
It indeed does, and even has a "Feedback Type" of "New Feature Request". You're right in that feedback should rightly be done through that channel.

Re: Technology Manager Features Request

Posted: Fri Mar 29, 2013 2:48 pm
by clingmann
I happen to be in the same Stake with an individual with input to the TM tool. Rather than just giving him my own ideas I thought it would be nice to get some community input.
*Edit*

Since as technology specialist we don't actually ever see each other, I would have thought using the forums for such a discussion would be quite productive. Even beneficial in us figuring out what are the best ideas others have to improve the tool.

Re: Technology Manager Features Request

Posted: Fri Mar 29, 2013 2:54 pm
by jdlessley
Clingmann wrote:Your post effectively tells everyone don't bother posting here, as it won't be heard.
The post is telling everyone the best channel to get these requests to the correct people. You will note I stated these forums are user-to-user support. We can discuss these requests, which is what the forums are all about. But to expect the results of the discussions or even the ideas to reach the proper people most likely will result in frustration since these forums are not the official channel to get these changes made. We may be fortunate to have an ICS employee visit from time to time but those who do may not belong to the organization or have the connection to the right people.

Re: Technology Manager Features Request

Posted: Fri Mar 29, 2013 2:55 pm
by russellhltn
There's a fine line between discussing what we'd like to see and build a consensus to what would be useful - and raising false hopes that the information would be used. As such, it's sometimes hard to tell if a discussion is a good idea or not. I think it does raise some good ideas, but I also think it tends to raise frustration levels.

I don't think JD is trying to quell the discussion, but rather set guarded expectations for the outcome.