"Does the October 15 issue only address opening new tickets, so I'm free to still call in after I've opened them?"
--The way I interpret the message, yes.
" One concern noted was that we didn't want people to be able to park in the parking lot and tap into the guest network. My question is still "who cares, what problem are you trying to solve?"."
--I'd guess it's a question of liability.
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Thursday, October 04, 2018 2:33 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: ibm.com / mysupport ?? Working for anyone?
If you are unsatisfied and getting "wait forever and seventeen Sundays"
then I would open a call to a duty manager.
Though I do find it unacceptable to flag a call as respond by telephone and they email me anyway with some inane question so they can update the ticket with "waiting on customer response".
I do like to start questions online and then call in. Does the October 15 issue only address opening new tickets, so I'm free to still call in after I've opened them?
You do have a legitimate concern with the customer site issue. Our "guest" network requires login and approval. It is a bit tiresome.
Businesses need to find some better way to address the problems they are facing and take "best practices" and "generally accepted practices" and discard them. Is the problem that guests are killing bandwidth? Then find the bandwidth thieves and block those sites from users who don't have to log in. For example, block NetFlix from anonymous users on the guest network. Sure you're going to run into some concerns. For example one may be using Youtube for educational videos or product presentations while another may be using it to watch a movie on their personal phone while working on their computer.
It's gotten to the point that IBM doesn't even ask for guest access anymore, they tether to their mobile devices. But, as you've said, in a bad reception building this can be an issue. In our building we're adding cell repeaters.
One concern noted was that we didn't want people to be able to park in the parking lot and tap into the guest network. My question is still "who cares, what problem are you trying to solve?". Again, if it is a bandwidth concern then block sites which use too much bandwidth from anonymous guest users. But we're located in a small complex of industries only in a rural location so it's not like six cafe's line our parking lot and they'd all be chomping bandwidth.
We already monitor and kill sessions from generic guest accounts set up to only be used in certain conference rooms. We don't want to bother limiting them automatically by WAP (some cumbersome technical reason).
Funny that it's always HR that is the violator. Paraphrasing Leona Helmsley "rules are for the little people".
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
midrange.com
