@creayt said:

Based on my recent experience w/ an R610 w/ a SAS 6/iR Integrated controller, where we found out late in the game that the controller can't/won't run the SATA SSDs at anything about 1.5 Mbps ( calls it its "negotiated speed" while listing the "3.0 Gbps capable speed" in OpenManage ) while intermingled w/ our other SAS drives, even though they're SATA III drives.

Pretty normal actually.

SAS and SATA do things slightly differently. They are electrically compatible but in order to interact with each other on the same backplane they need to negotiate down to an equal speed. Sounds as though your controller only does it at SATAII on this.

If you gank out the SAS drives, does it go at the right speed then? If you mix, does the SAS drives report and get the right speed?

Best bet is to use another device if you want to have pure SATA SSDs. A small SAN would do the trick.

Better question is, why didn't you get SAS SSDs?

@johnhooks said:

@PSX_Defector said:

@johnhooks said:

No one would think that's reasonable. Around here, you can figure around 80% is take home, until the next tax bracket.

Unless you plan on making triple what you make now, the "next" nominal bracket is the 28% one. And that rate is only for the money made after that threshold. I'm deep into that bracket.

http://www.forbes.com/sites/kellyphillipserb/2014/10/30/irs-announces-2015-tax-brackets-standard-deduction-amounts-and-more/#1425d2006f71

Let's break down what someone should be seeing in a paycheck. To make this simple, let's assume state income tax out of the equation, because they vary from flat 3.75% in Illinois, a progressive scheme of up to 5.25% in Oklahoma to 0% in Texas. We will also assume you work for a company, so standard W2 wages and we will assume they are cheap ass bastards who went "hurr durr obamacare" and refuse to offer health insurance. Medicare is 1.45% flat, no matter how much you make. FICA is 6.2% up to $118K, then it's nothing. Federal taxes are a progressive tax system, from 10% up to 39.6%. Consult your local tax professional for more info.

If you are making $40K flat, single, taking the standard deduction, your AGI would be ~34K. $2480 would go to SS, $580 would go to Medicare. The 34K would put you in the 15% tax bracket, 10% up to $9K then 15% on the rest, $3716, for $4638 total. If you set up your W4 correctly, you should have ~$620 a week net on $769 gross, or 19%.

These calculations change with your situation. I make a lot more than $40K, my tax deduction is 24% per paycheck with an effective rate of around 19% after all my deductions and such.

If you ever hear people quoting some crazy numbers on taxes, always break it down on them to find out exactly what they are getting. You will find that most people are talking out their ass.

Ah sorry I should have clarified my position more. I'm married filing jointly so the next for me would be $74,901. Plus PA state tax is 3.07% plus the local township/borough junk here which changes drastically depending on the area and is charged both where you live and where you work (in our side of the state this can end up being 2-3%). I also wasn't counting any deductions in that so that does make a difference in your favor.

With married joint, your AGI would be 13K versus the 6k. So you would be making ~90k raw before you hit my tax bracket.

People always forget it's AGI, not what you make. I made decent 6 figures last year, woo gambling wins, but my AGI is well under that.

@Carnival-Boy said:

Where I think there is the most confusion is in the differences between PaaS, IaaS and SaaS.

We used to use the acronym CaaS with big red V. We always rocked the CaaS box. Rocked the CaaS box.

https://community.spiceworks.com/topic/262865-calming-the-cfo-ensuring-godaddy-gate-never-happens-again

Still relevant, and of course, no one listened to me and setup redundancy on their DNS.

@IT-ADMIN said:

@Dashrender said:

You had an entire day of downtime on this and no one noticed?

only the one who was working on the payroll software was having a connection error, i told him that we have a problem in the server, so he stop working on it until this morning when things come back to life
fortunately the issue occur at about 6 PM and we finish the shift at 7 PM therefor the employee didn't complain because he was about to finish his shift

People who know me know I'm a gambler. I go to Vegas all the time, I blow money at various casinos throughout the country.

You just rolled a quick point on the craps table, you hit a blackjack on your first hand, you laid down $5USD on 21 red and it came up. You got seriously lucky. By pure chance you got out without anyone being the wiser.

One of the things I tell lots of people is not to rely on luck to get you through a gambling session. But this situation, as a gambler, you need to know how to hedge your bets. Your gonna reach another problem and go head strong into it, like laying down $100 on a table without knowing what the game is. You need to think through the entire scenario, what will happen if you do this, what is your fallback position, what is your backout procedure, how do you know it's done and satisfactory.

Remember, the worst thing you can do as a gambler is go and do things without thinking. When I sit down and play blackjack, I have a good idea about the cards, the odds, where we are in the deck, what is available, what is not available. I calculate the risks, rewards, and make my decisions on that. As one should do when working on anyone else's machines.

@Nic said in Ok, which one of you broke the Internet?:

@PSX_Defector they don't f***[moderated] around, so to speak

@scottalanmiller said:

You can build a lot of drivers and such into a base image. Although standardizing on a model is a good first step. You want to reduce "Model Sprawl" whenever possible.

I haven't made model specific images since the early 2000's when Win98 and Ghost ruled the land. Since about 2005 or so I've stuck with creating a universal image in Vmware and deploying it to machines.

And since the consolidation of all the hardware with AMD and Intel it's been much easier to keep OOBE in line on boot. Used to be lots of different drivers would need to be deployed, but now I can just lay down basic Windows drivers, put the updated ones on a directory, then deploy it out.

@nerdydad said in Hurricane Harvey:

@psx_defector said in Hurricane Harvey:

@scottalanmiller, @Dominica, @Texkonc, @NetworkNerd, and I are far enough inland that we won't get any thing more than a scattered shower or thunderstorm from one of the arm bands of Harvey.

Nice to see that I'm forgotten...

And how often are you on here? I forgot that you're on here.

@coliver said:

@Dashrender said:

@gjacobse said:

Why wait till 2017 to move to O365? With DirSync and other tools, you can have SSO and all the joys of on premise, and not have to worry about a physical device.

Because I am already paying a three year SA Open License agreement for my current setup that expires in 2017.

Also, before I can even consider moving, I have to either move most if not all users to OWA or fully implement a complete replacement system for our current calendaring system for physician calendars that will sync with iPhone/iPad/Android.

Outlook cached mode is completely unusable for us. I quickly discovered when we converted from Domino to Exchange that cached mode wasn't anywhere near real time when updating other people's calendars. We require realtime (or very very close to) updates so that all 80+ people viewing calendars are aware of changes/updates, etc. OWA or a third party would work for this, but O365 with Outlook in non cached mode I would only image would be a horrible experience.

Have you tried Sharepoint Online shared calendars. I'm fairly certain they can readily sync with an Android/iOS device. Maybe not as a primary calendar but then again your third party app wouldn't be primary either.

That would have been my recommendation as well.

Exchange is designed around a set of users. Sharepoint is designed to share, hence it's name. And you can integrate them together

http://blogs.technet.com/b/ptsblog/archive/2011/05/31/sharepoint-and-exchange-calendar-together.aspx

http://www.theregister.co.uk/2015/11/20/level3_outages_reported_in_us/

Hit us too.

@anonymous said:

There are not interested in a cloud option.

Why the hell not?

Putting it on any cloud provider would eliminate the whole ISP slow link issue, be centralized in a managed environment, and bring forth DFS pretty easy.

You are shooting yourself in the foot if you don't consider it.

With the numbers you are quoting on the backups, with the sizes of the databases, looks as though don't go through that much in changes. ~10GB of churn in a year is nothing for Sharepoint. I'm thinking you have a few numbers off. Ive seen it in clusters of 20-30 front ends with two massive database servers behind them churn 30GB a day.

Easiest way to get some scalability is to make sure your database server has enough horsepower. With that much data, a two proc/32GB machine should be sufficient. Get it into a Windows Failover Cluster, and you should have plenty of room to run.

The front ends are much easier to deal with. Load balance them using whatever and have them join the farm. Adding a web node is trivial in Sharepoint.

The rest is just knowing what you plan on doing in Sharepoint. If you are just presenting a website and using it for a CMS, nothing to it. If you are using any kind of analyitics to parse data, then there is more towards queries and database IOPS. If you are using it as a data repo, then giant database to hold the blobs would be important.

What are you running now? What seems to be bottlenecked?

@gjacobse said:

@Dashrender said:

@gjacobse said:

Found it.

You sir, are the man!

Up until a few short months ago,.. I still had Windowds 95... and I'm sure 3.11..

Let me see about piping a ISO and let you know.

I've got all of those in some dark corner of my repo.

But of all things, I actually didn't have a Microsoft Vista ISO. Need a Win7/8/8.1 disk? How about XP/2000, even god forbid ME? Got ya covered.

Drop the MTU from 1492 to 1484 then 1476. See if it works then.

@JaredBusch said:

@brianlittlejohn said:

With only 15 users, personally, I would spend a weekend and reset up my AD environment just to avoid issues in the future.

I would agree with @brianlittlejohn here. You had no AD at all prior too few days ago.

Just remove all the machines from the domain. Nuke your DC and start over.

As someone who does this a lot, even with more users than that, it's pretty simple.

I keep a few templates ready to go to deploy a base AD environment. Takes me ~3 minutes per end point to unjoin to the domain, about 2 hours to rebuild AD from template to completed environment, then ~3 minute per endpoint to rejoin. With that in mind, a 15 users environment, I could have it done in an afternoon while drinking beer.

Shit like this is easy as hell. Although I would be investigating the cost/benefit of having an AD environment for that few of users. Unless you have a case for it, Samba will do the job of authentication just fine. And a Samba domain is just as quick to deploy. Save quite a few bucks in the process. AD is great, I made my career around it, but it's not a need.

@Lakshmana said:

How to cuustomise the Linux os according to the system to be used at any environment.
How to customise the Windows OS ?
What are the difference present between the customization?

How is babby formed?

Inbound VPN? OpenVPN or PPTP? Mushroom supports OpenVPN, Peplink only does PPTP. Every vendor supports outbound IPSec tunnels.

You can easily get Peplink gear from anywhere. I buy them a lot, easy to get one in a few days. My usual vendor has them right now:

http://www.ispsupplies.com/brands/Multi-WAN-Routers/PEPLINK-BALANCE-20.html

The other part to keep in mind is the bandwidth limits on these things. I found out the hard way my Peplink had a 20Mbps cap on how much data could flow through it. After I got an RV082, I hit the ~50Mbps limit on that one, then the RV042's 100Mbps limit. I had to go up to using a Mikrotik to support the large ass circuits I was getting from AT&T and TWC.

@Brains said:

It looks like we are going to settle with the LRT224 due to cost concerns....

Waste of money. Had one, got rid of it because it wasn't powerful enough to handle what I wanted to do.

Better off getting a Mikrotik if price is a concern. $70 for much more useful hardware.

@scottalanmiller said in Linux skills are hard to find:

@PSX_Defector said:

We have the opposite problem. Linux people who have been in multi-tenant environments are a dime a dozen. Windows people worth a damn have been hard to find.

I agree. Linux people who know large scale management are far, far more common than Windows ones. But you can normally leverage Linux people for Windows work in most cases.

No, because Linux people are assholes and bitch/whine/complain if they have to do anything related to Microsoft at all.

Take for example log reviews. Many of our Linux people cannot comprehend not using grep. Or even something as simple as disk cleanup. The C:\ drive is almost full, let's try nothing! Many don't even know what C:$Recyclin.Bin is, let alone empty it.

I can do lots of things in both types of environments, but that's because I'm old and have seen it all. I stick with Microsoft because its more lucrative, being that people expect if you know Windows then you know SQL, Sharepoint, Exchange, and XBox. Opens more doors for me.

@scottalanmiller said in Linux skills are hard to find:

@Dashrender said:

My question - why would you think that - was in regard to Jason's assumption that more people would like Linux - why would he think that?

Ah, they would like it because it is easier to learn, the knowledge lasts longer (Linux takes less retraining than Windows does as it changes more slowly)

Yeah, Windows is so fast on how it does things. Never mind the same driver method has been used since Windows 98. Or that the same command line utilities still work from NT 3.51. Or that Explorer hasn't changed since NT 4.0.

Oh, I know, SQL Server. That certainly changes every revision. Oh wait, the only thing introduced recently is AAG. Same ol' SQL Server Management Studio from 2003. Same old database stuff since 6.5. Everything else is under the hood enhancements.

Yeah, Windows is hard because it changes so much. To hell with the Start menu!