@scottalanmiller said in I can't even:

IOP's. That's a new way to write that.

1. Slow server? Just increase the IOP's. It's right there. In the settings. Don't worry: it exists.
2. Slow internet? Wiggle the network cable, and then flex it back and forth like a glow stick. That will get rid of any blockages in the line.
3. Slow printing? Try using a more slippery type of paper.

I think both have their place. The key philosophy being the moment that your job becomes easy, it's time to start looking. Some companies have pretty cool job rotation programs that keep you fresh, so linear progression seems like it might make sense. Additionally, if my overall goal was more of a management role at a company that I liked, I would put in some years for that.

On the other hand - I was at my last job for 6 years. A job I liked. I moved on a whim because I had this nagging feeling that I hit a ceiling. When I started my next job, it confirmed that feeling x 1000. Year 1 of new job was professionally more beneficial than 4 at my last job.

Regarding happiness, a job isn't like a wife. Happiness and loyalty only get you so far. It's one of the most important things, but not the only important thing.

Sorry, was on vacation.

@RamblingBiped said in SPF Records for Google Apps Mail:

@TAHIN So I should be able to get away with the same entry as what you have then? What does the addition of "a mx" add?

Adding the 'a mx' parameters indicates that only servers that match a public A record or public MX record of your domain are allowed to send. Generally, just saying MX is enough - you're telling the recipient to fail the mail unless the sending IP matches the IP address of one of your domain's MX records, effectively eliminating spoofing. We added 'A' to give us the flexibility to source email from an application or DMZ server. The include: parameter overrides these defaults, allowing Google to proxy.

80% of the reason we (and most companies) implement SPF is to protect their own organization from incoming spearphishing via domain spoofing. The fact that it isn't 100% adopted by all organizations shouldn't be a deterrent to use it.

Our database guy and our web guy built an application that converted our whole system to ICD10 since our EHR didn't do it natively. This app saved our finance folks about 1000 hours of work. Our CIO, who was always good at converting ideas to cash (very good quality for a non-profit) started selling it to other clinics who used the same system. eCW eventually caught wind and wanted to buy it. He gave them a price about as ridiculous as what they would have charged us for it... they refused haha. It was a good shoe on the other foot sort of story.

This isn't a general best practice to be used in every case. You're only susceptible to DDos attacks for domains that you're publicly authoritative for. You can use this site to determine if you have open resolvers for your domain: http://openresolver.com/.

It is true that AD requires recursive queries to work. Here's MS's note on securing DNS: Disable recursion on DNS servers that do not respond to DNS clients directly and that are not configured with forwarders. A DNS server requires recursion only if it responds to recursive queries from DNS clients or if it is configured with a forwarder. DNS servers use iterative queries to communicate with each other.

If you do have (and require) your internal DNS to be a public resolver, a solution I've seen is to:

1. Disable recursion on the servers that are publicly available. The DNS servers will start using root hints instead of forwarders.
2. Create a new DNS server (not publicly available). Enable recursion and set the 'outside domain' forwarders to an outside resolver (ie- ISP DNS). Set the 'inside domain' forwarders to your original DNS servers.
3. Move all AD-connected resources to point to this new server.

I've very recently come into a situation where my company is able to receive a lot of free equipment (over the amount to be untaxed -10k in most states?), and I need some advice. Can someone who is experienced with large hardware acquisitions and tax laws PM me?

Thanks!! Happy monday!

What does "he knows nothing" mean? From my perspective, knowing nothing is what I did when I was 6. After that I always knew something about computers. On a scale from 1 to 10... 1 being "The cup holder in my computer is broken!" and 10 being entry-level job ready... how do you rank his current knowledge?

Teaching him about hypervisors would be pointless without a knowledge of system architecture. Teaching him about the OSI model would be pointless if he doesn't know what TCP/IP is. You need to gauge where he's at and go from there. Maybe have him pick up a (not too dry) A+ book. Maybe watch some videos about how TCP, IP, UDP work. Ethernet, switches, routers?

Thanks, happy to be here! And for the record, this is the most un-Googlable site on Earth, lol, unless of course you want yogurt.

Does anyone have much experience with Nasuni over several WAN links? I saw over in SW that SAM used to do some consulting for them years ago, maybe you still keep in touch?

We're in the market for a centralized cloud copy provider. We use Autodesk Vault for CAD, so this would be for the 'small stuff', GIS, Office docs, etc... We're leaning between Nasuni and Panzura. Panzura used to be the cheaper option, but with Nasuni's simple Storage as a Service payment model we can very accurately calculate our costs for both implementation and ongoing. They gave us a huge break on our VM appliances so we're really only paying per TB. ($3,750/TB/Year)

Without having any experience with Panzura, it seems wholly complicated and more messy than Nasuni and holds more convoluted costs. We've been trialing Nasuni now for several months. Can anyone speak to what Nasuni does very well and not so well when compared to Panzura?

Thanks!

Haha that's a cool idea.
Here's my state. And no it's not during a blackout, we're just one giant dark zone

SSLlabs is good. I recommend selecting "Do not show the results on the boards" on each run, otherwise your result can get displayed there for the world to see, which can be pretty bad if bad guys are watching and you've only started your security project.

@dashrender said in I can't even:

@eddiejennings said in I can't even:

@scottalanmiller I do not see that ending well.

Actually I don't see it starting at all.
It started sounding like he wanted to be a sales person, but then he doesn't know the specs needed for any of the sales - so he's have to hire that part out.. so what value does he bring?

He's the idea guy! You don't have to know sales, computers, or how to properly punctuate if you have the ideas. His staff will flock to him because he has the idea and they'll work for free because they believe in him. And it will all work out and he will be rich before 2018 hits and he will buy a boat and retire from his fortune 500 company in 5 years.

I would recommend LastPass right up until LogMeIn bought them out. Their business model is to double, triple, then quadruple the price while simultaneously removing features from their free product. In fact, it's already happening.

@BBigford said in Scripting install - help:

We took them on as a client. So whoever setup their stuff in the beginning looked like they were just lazy and careless.

Might have been a gov't organization at some point? Some places in my town were run sort of like that when they were connected up with the state.

Teams and Slack both set out to solve an incredibly big problem with email: conversation-based collaboration. I really want to love it because if you run analysis on the type of email that flows between users of an organization, 70% of it is 'read once and delete' or one-liners. It's like supercharged IM. It took a while to wrap my head around the whole idea, but now I can see the overall potential, and it's staggering. But the OP comment regarding external user limitations is why we're not pursuing it. Having project collaboration for our internal users on Teams and having to import emails from external users would add too much overhead and confusion, and be a training nightmare.

Other reasons we're not using it:

• A lot of documentation doesn't exist yet. Such as if we roll this out, we'll have archiving / legal hold requirements.
• Doesn't have the kind of 3rd party product integrations that Outlook has, which we rely on.

We're actually fully licensed for it, wouldn't cost anything, but the use case isn't quite there until it can include everyone. We'll probably re-visit it in 12-18 months.

Gotta feel a little bad for them. Regardless, they already lost my business after years of being Samsung loyal. 80% of my phone choice is dependent on removable battery, headphone jack, and SD card slot. Might go LG next round - the V20 looks like a pretty fun phone to nerd out on.

@travisdh1 you can count on that!

A pair of Dell EqualLogics. 4 TB 15k SAS on one and 8 TB 7.2K SATA on the other. I call it manual disk tiering Housing Hyper-V CSV's for about 100 VM's. Most of the data is in Windows file servers for roughly 500 users.

Luckily these are aging out soon - as will this architecture.

@Dashrender said in Do you track medical records?:

@TAHIN said in Do you track medical records?:

Oh yeah HL7, it's coming back. Man you can make big bucks as an EHR integration coder.

Why is this?
Does HL7 not have all the (I'm going to talk out of my ass because I'm not a programmer and I have no clue what I'm talking about) tags it needs to identify all of the possible incoming/outgoing data points?

Or is it even worse than that - it's a jargon problem - where different areas of the country some call is soda, some call it pop, and the worst, some call everything a coke, even Dr Pepper - it's just a coke. LOL

All I remember about HL7 is that we paid someone a bunch of money to deliver something they already built for someone else. I'm not sure how hard it is but it sounds like a cushy gig. EDIT: And I know that's how software works... but this was an interface. Usually highly customized.

Our database guy and our web guy built an application that converted our whole system to ICD10 since our EHR didn't do it natively. This app saved our finance folks about 1000 hours of work. Our CIO, who was always good at converting ideas to cash (very good quality for a non-profit) started selling it to other clinics who used the same system. eCW eventually caught wind and wanted to buy it. He gave them a price about as ridiculous as what they would have charged us for it... they refused haha. It was a good shoe on the other foot sort of story.