I'm using a ReadyNAS 316 using my Veeam.

@NetworkNerd
Will be shortly. Stuck doing a bunch of file archiving.

Wow, this is very, very cool. Can't wait to see how it integrated into my Veeam B&R console.

@scottalanmiller said:

@DenisKelley said:

Don't even get me started. I have flagged so many of those that this one is pretty tame. When you use pics of people being disabled, you've kind of went over the line.

Flagged so many of what? What did I miss?

Behinds the scenes by me. I've done quite a few where the pic is actually offensively linked to the topic at hand. They get pulled quickly, but it has been awhile now.

Don't even get me started. I have flagged so many of those that this one is pretty tame. When you use pics of people being disabled, you've kind of went over the line.

@thecreativeone91 said:

@DenisKelley said:

@scottalanmiller

Too Bad grounding doesn't provide enough of a load on a circuit to trip a 15/20amp breaker . So you'll still get shocked or killed. 30mA is the deadly point. a GFCI will trip at 5mA (unless it's a modified 30mA)

You do realize that this was a joke....a play on words.

@scottalanmiller

Yeah, that first night was a killer.

@ajstringham
Read the guide. It is pretty short. You can force it, but once you change a GP or assign it to a User or Group, you'll need to refresh Group Policy unless you wish to wait.

@ajstringham

I realize that you are using new software, but I've always jumped to using WSUS 3.0 Step-by-step guide. It is very good on explanations and how to setup each section properly.

If you are using client-site targeting, which it looks like you are doing, you need to do two things:
(1) Attach this GP to the computer OU you wish the policy to apply
(2) Manually create that group name on the WSUS server called EW.

Obviously, you need the physical computers to be part of that OU. If you don't have the EW group setup in WSUS, PCs will never show up in WSUS because by default, only the standard-named ones.

@ajstringham said:

@thecreativeone91 said:

@ajstringham https://maas.ubuntu.com/

Echoing @DenisKelley 's comment: learn something new.

Happy Birthday.

@Mike-Ralston said:

..................we want to go with a **MAAS **Setup on.

Learned something new today.

@ajstringham said:

A second DC is always a good idea. It's never really "should I have two DCs?" It's "when should I add a third?" Why is rebooting an issue? It's not like you'll be doing that during production time. It'll be during off-hours. Also, he said it's for ten counties, or more. I still say have your main DC with File/Print on it. Use the next license for your secondary DC, and go from there.

Because it might be silly to have 2 DCs for a company with say 5 PCs. Sometimes having the ability to selectively reboot a server has it uses. Not saying it has be split, but there are use cases for that.

@ajstringham said:

Considering AD has almost zero system load, is there really any reason to separate out AD from the file and print services? If anything, use the license of Windows server you would have used for File/Print on a secondary DC.

Yeah, little load, but rebooting is a likely candidate for separating the roles. A second DC is a good idea, but we don't know how large this company is.

@thecreativeone91 said:

I personally would seperate out your domain controller and your File/Print Server. I would keep an AD server just being a DC only. and use another vm for File/Printer if budget allows.

Yeah, when I started budgeting, I split all those roles out. A little extra money, but worth it. I can quickly reboot my Print or SharePoint server without kicking people off of files.

Giggle. Now I feel old.

Thin clients are in no way dead. VDI has its place, but it doesn't eliminate RDS. A good box should be able to run many many VMs. The only thing that might affect your decision would be the SQL ones. Licensing and if the app that runs on that system likes to play well with others.

Be careful about running Office with RDS. There are additional, crazy licensing limitations that you'll need to address if you do it.

Lastly, don't forget backup.

Good Luck!

@Dashrender said:

@DenisKelley said:

You'll go through a reseller. If you have an Open License, then you can grab a single license and add to your agreement. You then can install two more VMs on that server.

Just to clarify, even if you have an Open License, you still go through your retailer, and they attach your new purchase to your existing Open License.

Yeah, the last sentence was a bonus answer.