I think the question about how to do you find a good IT company and how do you find a good accountant are very closely related. There are a ton of parallels.
Take the onsite vs remote thing. In some companies they don't want to ever touch a plug, the same way they don't ever want to scan in a receipt. They want someone to show up and do the job. In other companies they have someone with enough IT knowledge to do the hands on stuff, the same way they have someone that does the daily accounting tasks, but needs help with the year end tasks.
In both lines of work when owners are searching for a service provider a recommendation from a friend will outweigh most everything else.
We found a "Computers 2 Kids" charity that we donate all PCs, servers, etc to... that are at least in good enough condition to work or get working with minimal effort. Ex: new hard drive or RAM needed.
It's local to us here in San Diego... but there may be something similar near you.
Gather knowledge from different websites and after doing depth research for the topic, you can write for the same topic in your blog too with your own words. But rewrite the same article by changing words and sentences is not good and you should have to suffer from legality.
For you second question,
Technical steps for the same topic remain mostly the same for all articles. So if you think for write the topic which you have suggested here "Installing Snipe-IT on CentOS 7" then also technical steps remain the same which is the legal. But that doesn't mean that you can copy/paste in place of write in your own words.
Content flow is also important to make content more interesting for users. This article will help you to know how to write the article in the proper way.
I think working in isolated, non-IT companies where there is no peer support at all it might be easy to forget how much training is endemic to any organization's core. If you are a lithography company and have many litho machines, many litho workers (even, say half a dozen of them) there is a natural cross training and sharing of knowledge, an automatic introduction to different equipment, styles and techniques. Even when no effort is put into training and development, which is effectively unheard of for any business in its core operations, there is a natural training effect through knowledge training. This is why cities with a high skill density for a given field have higher end people and pay more than other markets (NY for IT, SV for SE, Detroit for Automotive engineering, etc.)
Hard to compete with the Iron Mountains, and Amazon Glaciers.
Amazon Glacier and BackBlazeB2, yeah. I haven't dealt with Iron Mountain in a very long time, are they still only doing the "secure box" thing? Also, are the prices still around $500/month for the smallest containers?
I agree, I feel like I'm "wasting time" by being forced to wait for a decision etc. I really have to change how I think about business transactions.
I also had a hard time years ago with this. Sometimes I still do...
So much of our work is "waiting on this or that" to finish.
Several years ago I was called out to a retail shop.
They had issues with their network printer.
As I started checking things on site and getting the lay out. I found their network was hanging by threads. Literally the wires held everything up nothing was secured.
They also had an open and default setting network. I helped them secure the router. And got everything working for the time being. I left them with a set of plans to resolve the issue and not bandaid it.
I was working on site multple times and the manager would have "meetings sometimes for an hour" in the network room where I needed to be. And this would happen after I was on site. So I sat around... I let that clock run full steam!(I billed (my door back -out their door)
I'm over it. I will almost always bill for all of the time with someone.
They have accused me of trying to nickel and dime them. I rebutted that with you asked me to bandaid an open wound I told what needed to be done to fix it. You never approved it. Just the bandaid. These bandaids happened on multple occasions. People tampering with the systems causing all of the issues.
All problems outside of my control.
Also when they went to a static IP across the organization 17 stores. Some worked the next day. Others didnt. And I got blamed for 1 of them not working. All because TWC told them it was my fault. That's when they started blaming me!
I figured out that the problem was on TWC, and I took care of that with the customer right there. They saw I fought for them. But to this date I haven't done anymore work for them. I will likely keep it that way.
I just asked to join the service providers group. I think that's the closest I can get.
Awesome! This wasn't a knock on you, just the current functionality of ML - I rather like the way SpiceWorks does it Some name at some company - made it really easy for each employee from a company to have their own identity at the time being tied to that company.
Huh - just had a thought. What about asking all vendors who want to be known (and post as) a vendor update they name to be [email protected]?
They could but seems like that would make for easy abuse as anyone could do that.
If you had experience in the industry you would never ask that. Cisco has long locked their phones by firmware. There are threads and threads of people trying to get the "open" SIP firmware for their Cisco phones.
Yeah really there is a way to get some of the very old ones working but it's an PITA and you'd be better off spending money on a newer phone from someone else..
We have CUCM clusters and even hate a lot of the way they do thing, but when you need the scalability, load balancing that Cisco clusters offer there very few competitors. CUCM has a bad name from SMBs buying it whihout knowing what features they need and just buying cause it says Cisco..
Which is why I'm probably going to be getting the lawyer involved. It's outside my area of expertise now. Yes, we do sell products on the website, yet the pages they reference are information/education only.
Start with the single point of what they want, in this case two servers to cover the lost off one, then explain that the likeliness of a power failure is higher than the server failing, that the AC failing is higher than a single server failing, that perhaps a tornado or other natural disaster is higher than the server failing. Of course you'll have to find all of the stats as they relate to you.
Then explain that it's pointless in covering the server if you don't take care of those things first.
I'm not sure where it came from but Scott said that Dell server have a 4 hour out of 8 year expectation of down time.