Originally Posted by KC Fish (Post 8419744)

Anyone who has actually had the responsibility of purchasing and maintaining a complex network infrastructure for any reasonably sized organization wouldn't think twice about a decision like this. It's easy for the users to say "Throw us a little bone, it isn't hurting anything." All the while, they're sitting in front of a company computer loaded with company software using company bandwidth for doing something that is not work related and can be distracting from doing actual work.

Maintaining balance and a happy work environment is certainly important. But there are countless ways to do that which would conform to company policy and not set a precedent that could be abused later. Because I know from experience that if you give the users an inch, they'll expect to take a mile next time. If you say "Ahh it's OK, go ahead and watch the game this once.", then Judy McLazyass down the hall hears about it and justifies watching Judge Joe Brown, because Bob gets to watch basketball. Then it snowballs to the point of slowing the network down. And at that point, people begin bitching at IT because they don't have enough bandwidth. Which of course is also IT's fault.

This may seem to the common user to be something minor and would never actually cause any harm. But I can tell you from experience that it adds up very quickly.

Originally Posted by KC Fish (Post 8419744)

Anyone who has actually had the responsibility of purchasing and maintaining a complex network infrastructure for any reasonably sized organization wouldn't think twice about a decision like this. It's easy for the users to say "Throw us a little bone, it isn't hurting anything." All the while, they're sitting in front of a company computer loaded with company software using company bandwidth for doing something that is not work related and can be distracting from doing actual work.

Maintaining balance and a happy work environment is certainly important. But there are countless ways to do that which would conform to company policy and not set a precedent that could be abused later. Because I know from experience that if you give the users an inch, they'll expect to take a mile next time. If you say "Ahh it's OK, go ahead and watch the game this once.", then Judy McLazyass down the hall hears about it and justifies watching Judge Joe Brown, because Bob gets to watch basketball. Then it snowballs to the point of slowing the network down. And at that point, people begin bitching at IT because they don't have enough bandwidth. Which of course is also IT's fault.

This may seem to the common user to be something minor and would never actually cause any harm. But I can tell you from experience that it adds up very quickly.

Originally Posted by htismaqe (Post 8419754)

One could de-prioritize CBS Sports streaming video in the network, allowing it to only consume X amount of bandwidth if no mission critical traffic is present, and not have to mandate anything to anyone.

Originally Posted by Deberg_1990 (Post 8419809)

Well said. Slippery slope....

Originally Posted by NJChiefsFan (Post 8419824)

The point about the non-basketball fan is a good one though. If a user doesn't like basketball how do you explain to them that they can't recieve the same benifits that a basketball fan does? Do you let them watch whatever they want as well? Are they only allowed to do that during the time the NCAA tournament is on? What if what they want to watch is during a different time of day or time or year?

Originally Posted by htismaqe (Post 8419754)

One could de-prioritize CBS Sports streaming video in the network, allowing it to only consume X amount of bandwidth if no mission critical traffic is present, and not have to mandate anything to anyone.

Originally Posted by KC Fish (Post 8419846)

You're recommending implementing additional administration work to allow users to violate company policy to use company resources for non work related consumption of bandwidth. No thanks. Much easier and more efficient to simply block it. I've been a system administrator for nearly 10 years now, and if there's anything I've learned, it's that you don't let your users set the rules. Sorry if the user is sad that they'll miss a game on company time. But it's not IT's responsibility to provide happiness for its users by breaking policy for them.

Originally Posted by htismaqe (Post 8419754)

One could de-prioritize CBS Sports streaming video in the network, allowing it to only consume X amount of bandwidth if no mission critical traffic is present, and not have to mandate anything to anyone.

Originally Posted by Saulbadguy (Post 8420065)

Leave the rule making (and enforcing) to management, and just do what they tell you to do.

Originally Posted by Saul Good (Post 8420104)

But people who don't own companies always know how to run companies better than those who do.