I think, I read this as @Steve Linthicum thinks the other webinar will be more interesting than ours!! Steve, says it's not so!!
Server+ TTT - Keeping the Conversation Going
- Thread starter Rick Butler
- Start date
I think, I read this as @Steve Linthicum thinks the other webinar will be more interesting than ours!! Steve, says it's not so!!
Hey, I might be biased....but...I think we'll have more fun. /rI think, I read this as @Steve Linthicum thinks the other webinar will be more interesting than ours!! Steve, says it's not so!!
My problem is I can only utilize "preemptive multitasking" and as we all know that isn't real multitasking.
Well... companies who run services may be going server-less, but it still runs on someone else's servers
So Amazon and Azure will have plenty of data center techs running around.
This brings us full circle to the place where I'm located that will likely see a reduction in the need for technicians having the skills to operate inside a data center. As pointedly detailed in an article titled "Top 5 places to build a new data center," Southern California doesn't meet the requisite factors used to identify a suitable data center location.
I'm
I'm sure they will across the board. As the cloud gets stronger, more and more people are going to just throw their hands up and say they don't want the headache of managing their own data centers. The hold outs will be those that don't want to shell out money to pay a cloud provider or deeply rooted trust factors. But like anything else, I think the pendulum arm will swing back the other way - and I think it does that through mobility.
The biggest question of the cloud is this: How close to the edge is the data/service, with respect to the user. If the data/service isn't sufficiently available/useable with a cloud solution, folks are going to opt to have those requirements locally.
A smaller example of this is with people who keep files on their local desktop, versus pushing them into the cloud. I know a lot of people who don't want their stuff out on the cloud. There are certainly a number of personal things I won't ever put out there, that's for sure.
Good to see that Colorado made the list
I'm sure they will across the board. As the cloud gets stronger, more and more people are going to just throw their hands up and say they don't want the headache of managing their own data centers. The hold outs will be those that don't want to shell out money to pay a cloud provider or deeply rooted trust factors. But like anything else, I think the pendulum arm will swing back the other way - and I think it does that through mobility.
The biggest question of the cloud is this: How close to the edge is the data/service, with respect to the user. If the data/service isn't sufficiently available/useable with a cloud solution, folks are going to opt to have those requirements locally.
A smaller example of this is with people who keep files on their local desktop, versus pushing them into the cloud. I know a lot of people who don't want their stuff out on the cloud. There are certainly a number of personal things I won't ever put out there, that's for sure.
Good to see that Colorado made the list
Looking forward to the session today! Had CIN issues and just recently got it fixed so I had to do some catch up for this TTT session.
Homework Answers:
Q1: Gates, Fences, Lighting
Q2: Imprivata OneSign
Q3: DoS (in my lab environment)
Q1: Gates, Fences, Lighting
Q2: Imprivata OneSign
Q3: DoS (in my lab environment)
In a lot of ways, folks overlook the risk of themselves doing something to mess up their own environments, particularly if they weren't the ones standing them up.
Troubleshooting?
It's
Easy
To
I'm
Very
Diligent
Identify - Establish - Test - Implement - Verify - Document
It's
Easy
To
I'm
Very
Diligent
Identify - Establish - Test - Implement - Verify - Document
Here is my attempt. Operative words in bold. (And a bonus for those who enjoy Blackadder!)
Identify the problem and determine the scope.
Establish a theory of probable cause.
Test your theory to determine the cause.
Establish a plan of action to resolve the problem.
Implement your solution or escalate.
Verify full system functionality and if applicable, implement preventative measures.
Perform a root cause analysis.
Document your findings.
In
The
Testing
Procedure
I'm
Very
Reliable
Darling
Identify the problem and determine the scope.
Establish a theory of probable cause.
Test your theory to determine the cause.
Establish a plan of action to resolve the problem.
Implement your solution or escalate.
Verify full system functionality and if applicable, implement preventative measures.
Perform a root cause analysis.
Document your findings.
In
The
Testing
Procedure
I'm
Very
Reliable
Darling
Very True in most cases we the IT People start tweaking things that don't need tweaking bypassing Change Management
Ignoring "change management." What a great point. There are these policies/procedures issues that are ignored. Just about every certification exam's objectives list identifies policies/procedures, but do any of us effectively cover their creation and how to write them, let alone how to follow them.
The 6 step Troubleshooting process of: Identify, Establish, Test, Implement, Verify, Document
The goal was to mostly keep the first 2 letters the same for each word above to help give a hint and differentiate the two different "I" words of identify and implement.
My mnemonic to remember the 6 step process:
Ideally Escape Teds Immortal Vampire Dogs
The goal was to mostly keep the first 2 letters the same for each word above to help give a hint and differentiate the two different "I" words of identify and implement.
My mnemonic to remember the 6 step process:
Ideally Escape Teds Immortal Vampire Dogs
I must admit in most courses we go through that section very quickly, their creation and how to write them is one area that should be addressed. Almost most of the good engineers i have interviewed and had on my teams , didn't know where to start with this one .
Time to complain about academic structure. I have a BS in engineering and a JD (Law). However, when I initially thought about creating a technical writing class at my College, I met with resistance from the English Department because I did not have a master's or doctorate degree that focused on English or Communication. In order to achieve the objective, I went through the College's equivalency process, explaining that technical writing is a practical based communication methodology and with my background, I was much better suited to teach technical writing than someone skilled in writing the sort of touchy/feely typical writing taught in a freshman English class.
We got a few good mnemonics so far! Hope to see a few more from different folks.
And this is something of a niche, because most of your technical types aren't the best writers, where an organization's writers aren't very capable, technologically. And only larger organizations are going to hire technical writers, choosing to outsource that writing to a scribbler house or some other thing.
I do believe that a good technical writing course taught by someone who actually have to write within the field is a great asset to any post secondary program. One of the worst things that an organization can do ( and I'm sure your JD it's about screaming now), is pulling somebody else's policies off of the Internet, changing the logo and some of the vernacular, and publishing as organizational policy, rather than actually having a proper sitdown with the appropriate management teams to work out what the actual problems are, the things that would need to be managed by policy.
But, we don't live in a perfect world. Most organizations don't have that nifty technical writer, nor access to an external contractor who can do that technical writing. But they do have that organizational requirement usually brought on by insurance, or some other compliance organization, that says they have to have these policies in place and accessible for inspection. So, a network engineer starts the Google process: +"IT Security Policy"
This is the kind of insane elitism that is prevalent in Academia; something that I personally witnessed so many times, that it has become very cliché. But, that's the college world for you - an awful lot of ivory towers and little fiefdoms that spring up for people to feel self-important, meanwhile there are lots of good people who are capable of the task.
For example, I had to deal with this when I was building a computer technology associate degree program. While it turned out to be far more favorable and amicable in the end, there was a fair bit of surprise that a 20+ IT Technologist (with a Master's, but still), would be able to navigate the choppy waters of accreditation and build a program that would satisfy state requirements as well as requirements from the accreditor. It could have just as easily gone negative, but there was that little wisp of surprise that someone like me would actually know what he's doing in setting up a collegiate program.
/r
And this is something of a niche, because most of your technical types aren't the best writers, where an organization's writers aren't very capable, technologically. And only larger organizations are going to hire technical writers, choosing to outsource that writing to a scribbler house or some other thing.
I do believe that a good technical writing course taught by someone who actually have to write within the field is a great asset to any post secondary program. One of the worst things that an organization can do ( and I'm sure your JD it's about screaming now), is pulling somebody else's policies off of the Internet, changing the logo and some of the vernacular, and publishing as organizational policy, rather than actually having a proper sitdown with the appropriate management teams to work out what the actual problems are, the things that would need to be managed by policy.
But, we don't live in a perfect world. Most organizations don't have that nifty technical writer, nor access to an external contractor who can do that technical writing. But they do have that organizational requirement usually brought on by insurance, or some other compliance organization, that says they have to have these policies in place and accessible for inspection. So, a network engineer starts the Google process: +"IT Security Policy"
This is the kind of insane elitism that is prevalent in Academia; something that I personally witnessed so many times, that it has become very cliché. But, that's the college world for you - an awful lot of ivory towers and little fiefdoms that spring up for people to feel self-important, meanwhile there are lots of good people who are capable of the task.
For example, I had to deal with this when I was building a computer technology associate degree program. While it turned out to be far more favorable and amicable in the end, there was a fair bit of surprise that a 20+ IT Technologist (with a Master's, but still), would be able to navigate the choppy waters of accreditation and build a program that would satisfy state requirements as well as requirements from the accreditor. It could have just as easily gone negative, but there was that little wisp of surprise that someone like me would actually know what he's doing in setting up a collegiate program.
/r
Well, we got through it all...thank you all for your participation and involvement on this series! It was fun to do! A special thank you to those Eight-for-Eight'ers who hung with me through the entire series (and even that misfired session...lol).
As I mentioned before, WHEN you pass the Cert, we wanna hear about it! Get on out here and post your victory!
So you have until the two week door closes to answer that question for the Amazon card (Session 6) - and I look forward to your responses to that!
Until next we go!
Rick....I guess now known around these parts as the CIN Black Spy...?
As I mentioned before, WHEN you pass the Cert, we wanna hear about it! Get on out here and post your victory!
So you have until the two week door closes to answer that question for the Amazon card (Session 6) - and I look forward to your responses to that!
Until next we go!
Rick....I guess now known around these parts as the CIN Black Spy...?
Thanks Rick. A great job..... While I wasn't 8 for 8 in terms of live viewing, There was a well known conflict in CompTIA's schedule as Stephen S. and I (along with others) for the WASTC Faculty Development Conference that ran from 9:00a.m. to 4:00p.m. last week and the workshop that focused on Security+.
Last edited: