IT BS thread

My company activated a new circuit for our network and when I ran a speed test this is the result... I don't think it's correct considering we started with 8mbs and supposed to jump to only 50

 

i would understand it better if it was 127.0.0.1

 

Needs to be ::1 on the middle finger to be forward looking.

 

I suspect someone with tats like that isn't one to look forward. Reminds me of people that get tattoos they think look cool but are really stupid.

 

Any of you guys ever use or heard of GFI Lan Guard?

Any opinions would be great.

Ty.

 

This so fits here:

 

I just got into it with a team of developers who want us to remove the firewall restrictions to SourceForge. I don't care if they've "cleaned up" and aren't bundling possible malware with their installers, there's a reason that the site is still blocked.

Oh, wait, you're downloading Microsoft software packages, you say?

If only Microsoft had it's own download site for Windows installers that was already tested and certified, and NOT blocked by the firewall...









...I swear, some of the smartest people I know are freaking idiots.

 

I hate dealing with our McAfee team. They are so F'n stupid. We have firewalled machines that can only talk to a specific McAfee EPO server. We get everything working, then they push a policy that doesn't allow the agents to talk to that EPO server. Then I have to touch every fucking server to fix it. They have don'e this no less than 4 times now.

 

They only know things within their little box......

I see it all the time. Frustrates the hell out of me.

 

At a previous employer we had some Windows servers that used Windows clustering (I know, what were we thinking, but we were actively working to remove them). Our server patching team had instructions on how to patch the environment without breaking it (you know, one at a time, let it fail over and then do the other one, not rocket science). Three patch cycles in a row, they just let the patches roll out and all servers in the cluster just reboot when complete. smh.

 

What are they using for patching? when we used WSUS, it was more difficult to setup groups like this. Using SCCM it's super simple.

 

Why is it that every place struggles with change control? I've only worked in one shop that actually had it implemented.

Today our hosted phone vendor pushed a change that broke a bunch of systems. I hate our phone vendor. (but, I love the job security they provide, if it weren't for idiots I might not have a job.)

 

Evening folks, just noticed this thread.. I knew there had to be IT on here somewhere!!

RJ

 

Can't remember, but WSUS sounds familiar. They did complain about their tool not supporting it easily, but that fell into the realm of "not my problem."

Not sure why this is hard, but we had a similar situation last week that was pretty significant and embarrassing (just internally, thank goodness). Not a change done by my team, but affected services provided by my team. So, guess what I get to do? Revamp our change management processes, yay!

 

I just got involuntarily migrated to O365.

I want to find the asshat who thinks “cloud is better” and choke them until I feel the life leave their body. The only thing cloud is better at is separating us from our budget.

 

Change management sucks. If you let the wrong people run it, it's impossible to get anything done. On the other hand you have cowboys making changes that they don't understand the grand scope and Fubaring everything.

 

Years ago, like 15 or so, I tested a change mgmt app, it was pricey, I work for local Govt so it wasn't going to happen, but was it ever sweet... They have since gone out of business, I can only assume they priced themselves out of the market as the product itself was outstanding..

RJ

 

I'm with you.. We too moved to cloud for email. Whomever designed our cert process should be fired. Not sure if MS or someone within. What's even more disturbing is that the contact came back indicating to follow troubleshooting docs. Well duh, you take these fucking calls then

 

The one shop I’ve worked that had a decent change control was a big pharma place. It was draconian as hell and I hated it, at first. To make a change required
• An RFC (request for change), with approval from the department manger
• testing in the Dev environment
• approval by the change committee (which consisted of IT department managers, business reps, and the QA group.)
• coordinated implementation (that way the network guys didn’t drop the network while the server guys were trying to do their changes.)
• review and confirmation that the change didn’t break anything.

There were emergency and standard change procedures too, so windows patches didn’t gum up the works. And, if something went down hard we could get it back up again. My current shop fights anything but rudimentary change control and we get bit in the butt all the time.

 

That’s per NIST, and exactly how the government does it.