 |
 |
Usually in the case of emergencies or outages I report the problem to the helpdesk regardless of whether or not there is someone at ATS who is willing to be contacted directly. One ATS person once made a request that in certain types of situations I call the helpdesk AND call her directly. If she is available to help expedite the issue, she would prefer to do so, but she isn't always available. She isn't the only person at ATS who operates like that, but I'm pretty sure most persons prefer not being called directly. The helpdesk is the sure way to get the problem properly reported. That's a way I like to have problems reported on our end, too. In the past few years I've found the helpdesk to be quite responsive, whether I'm reporting a problem by phone or e-mail. The helpdesk people seem more eager and quick to get the problem reported to the proper persons than in olden times. It used to be I had to go into a lengthy explanation of how we're not in East Lansing, but yes, we're part of the University, but no, our connections/facilities don't follow the same pattern as everyone else's. Eventually the helpdesk person would give up trying to understand that and would report the problem to the proper persons. It just became part of my normal problem-reporting procedure: I'd have to wear them down until they'd be willing to do it. But I don't even have to go through that so much any more. John Gorentz W.K. Kellogg Biological Station At 09:55 AM 12/16/2008, Jeffrey Utter wrote: >Jae, > >Please see the following MSU Techbase article on that very subject. When in >doubt, call the help desk. >http://techbase.msu.edu/article.asp?id=1818&service=techbase > >-- >Jeff Utter > >-----Original Message----- >From: MSU Network Administrators Group [mailto:[log in to unmask]] On >Behalf Of Jae Walker >Sent: Tuesday, December 16, 2008 9:51 AM >To: [log in to unmask] >Subject: [MSUNAG] Dead building switch port? > >Whom does one contact when connectivity is lost in a single office? I'm in >Anthony (2100), and *one* office has a dead network port. Our IT department > >says that at least one other office on the same floor has the same problem, >suggesting a dead port on the (new!) building router/switch. > >I'm reluctant to call the Help desk, given past experience... but have been >out of the IT loop long enough that I'm not sure whom TO call. > >Thanks, folks! > >Jae Walker (you can take the gal out of network admin, but you can't take >the network admin out of the gal)