_stump · infrastructure engineer

I like the messages MSFT sends about O365 issues. Clearly one-directional. "We noticed a problem with some email not being delivered. We'll probably fix it soon. Don't call us. Ever again."

One way to make your case for stronger security is to collect log information on the number of attacks you see at your edge devices. Bundle that data up into a short slide deck (because management-types communicate via PowerPoint, amirite?), throw in some graphics to explain that the company's networks are under constant…

See rule number 4 at the top of this thread. "Points/badges/entries will be added and accounted for at the end of the mission. If you have an inquiry as to your progress throughout the month, feel free to reach out to me and I'll look into the request. " I think we're all going to level up big time at the end of the month!

Exactly. It's hard work to keep up. But it's much harder to catch up.

If it's company owned, go ahead and track the hell out of it. I know my work laptop is for work only. But I bring my personal laptop with me to the office, so I can connect to the guest wireless and clearly separate work from non-work things. Plus, here in the public sector, everyone lives in fear of front-page coverage in…

We're in the same boat! I've never used VM6.0 (or any release of the product, for that matter). It's often difficult to tell when a feature is "new," since they're all new to me. I'm learning along the way, though. This stuff is fun, and keeping that in mind helps to look past some of the quirks of the contest. Kudos to…

O365 is SaaS! It's so easy! Just buy some subscriptions and start using it! *24 months later... So... do we have a governance plan in place for O365 yet?

You won't be disappointed.

Except falling into cloud is generally considered a good thing. I wouldn't rank it up there with falling in love, but you know.

I will always struggle with these cases and their sensitive ways.

That, can't be it, I"m always accurate. When using, punctuation?

There they are! Thank you!

That's interesting. It makes me think that a small number of tools, when properly selected, can manage and monitor everything. Maybe the "one tool to rule them all" idea should be buried. You reminded me that sprawl doesn't mean having more than one tool, it just means controlling the tools you acquire and using the ones…

The only problem here is the "other" mentality. In the not-too-distant future, you won't be able to tell a network engineer from a virtualization engineer from a server engineer. Drawing battle lines on that old organizational structure is inherently bad.

Of course, with that said, my eyes are now crossed trying to read that angled text! Which leads me to my prediction: I'll be getting new glasses in 2016.

Everybody says they want that single pane of glass, however, everyone also wants to own that single pane of glass. Totally agree. For this reason, I'm partial to a dedicated monitoring team that has no emotional ties to the technologies or solutions to be monitored. It's a way to avoid the in-fighting over who owns the…

I think we've still got exclusive ownership over complex troubleshooting and diagnostic skills, even if we need to rely on tools and data to aid in that troubleshooting. In other, I completely agree with you.

Oh yeah, that too!

Exactly. You don't need to go all-in. Cloud has matured and offers something for everyone. If you're suspicious, test the waters with an app or two.

I get the feeling that you're not a fan of cloud computing.

cbussard@idealintegrations.net wrote: "We have several great people here that have in-depth knowledge of SQL, VMware, Exchange for example." Now this is interesting. Let's talk Exchange, for a moment. You can have an Exchange guru and a VMware guru, and you can still end up with a suboptimal virtualized Exchange…

Sound like the technical debt problem. Open-source can make for an agile and responsive infrastructure, provided you have engineers with the skills needed to deploy and maintain these solutions. Support can be tough, no doubt. But costs associated with service and support contracts for enterprise-grade solutions can be…

How did you go about replacing one tool with another? Any lessons learned that you'd care to share? Consolidating tools is never as easy as it sounds.

Totally agree on the concept. We've all worked in enough IT shops to see the perils of a culture that doesn't encourage or require professional development, which is what's needed to break out of day-to-day operations and into strategic planning. Professional development is needed because the skills that make IT workers…

I generally agree, and i see that sentiment expressed on twitter ALL. THE. TIME. but to sum up any major cloud platform as "someone else's computer" is to acknowledge a fundamental misunderstanding of how cloud services are intended to be consumed. i'm as snarky as the next Internet denizen, but this one does annoy me a…

it's true! lots of InfoSec gamification events sponsored by "industry." you'll always run into a few ego-maniac neckbeards, but most people in the community are happy to help and share their knowledge.

I don't think you need to be an expert in every field. But you should at least have an understanding of the core concepts for networking, storage, server, and virtualization in order to be successful. Like kevincrouch4 said: know a little of everything and one thing well.

I think most CSPs would quickly remind customers of the shared security model, and firmly place the responsibility to protect and secure your data in your hands. what do you think?

Can't like this one enough. Plug-ins are great, but when they aren't maintained to be version concurrent, they end up holding a lot of work back.

You need to write up the technical bits for us in a Geek Speak post!