Not much pity for people not bothering to update.

https://www.theregister.co.uk/2017/04/13/microsoft_kills_support_old_windows_on_new_chips/

My answer to the OP. I mean I am not saying MS is good or bad, or Linux OS's are good or bad. But the OP was just a whiny bitch.

0_1489771473077_upload-b9cb86b3-5bb0-409a-bbe8-3b4008d3a94f

@olivier NP... I know it's isn't within your control. 🙂

Security advisories from our July 5th release are online, be sure to be up to date! See https://nextcloud.com/security/advisories/

@aaronstuder said in Moving to a New WSUS server:

@BBigford No Problem. Once I realized that the port numbers change, I realized the issue right away.

Clients are being seen by the WSUS server now 🙂

Sweet!

Top Android development frameworks, many of them are cross platform...

http://linuxgizmos.com/top-10-open-source-android-app-development-frameworks/

Yeah I read that the same way @Kelly .

That's like being paranoid about catching some tropical rain forest virus when you live in the tundra, so you just stay home all day and night.

This one bit me today. Wish I had seen this thread, but I was I. The middle of 3 other things when this user called. It was pure firefighting at that point.

Kudos to @TechnicalAngel for googling for me while I vented and leading me to the resolution.

@Dashrender said in What would you use to replace WSUS from SBS:

@Shuey said in What would you use to replace WSUS from SBS:

@JaredBusch said in What would you use to replace WSUS from SBS:

@DustinB3403 said:

Ah....

Sorry for the confusion then. Do they have the resources to run another WSUS server and proper licensing? It really is quite a simple solution.

PDQ Deply has options for 3rd party app updates etc, but requires annual renewal.

Oh, I can easily setup WSUS on one of their existing VMs. Just not really sure I want to with the size overhead for this many users.

Hey Jared, sorry if I sound a little lost, but what is the overhead you're referring to? You pretty much only have two options: Deploy a WSUS server and use a GPO (or regedit) to make the workstations talk to it, or you can manually install updates once per month (or per quarter). I would think you could easily deploy a very small WSUS server (either on 2008 or 2012) using WID and about a 60-80gb hard drive. You could even make it one of the guest VMs.

When I was supporting Office 2010 and Office 2013, Windows 7 and 8.1 I needed more like 120 GB to hold all of the updates, and monthly had to do the cleanup or I would run out of disk space.

Obviously there will be some variables to consider. I was basing my recommendation off our current WSUS setup (over 200 workstations, and 30 servers) vs his environment (8 desktop, 2 laptops and some unnumbered servers). Up until recently when MS changed the way the update cycle works, I cleaned our db every month and we've been doing completely fine with an 80GB hard drive on the server.

Thanks. Off to do some patching....

@nadnerB said:

I wonder how many times this has already been exploited?

We'll never know. Possibly a lot.

@scottalanmiller said:

I just use the console too. Few clicks and you are done.

Yup. Backup, Update, go back to sleep. that's my process.

That's insane. Luckily Oracle DB is rare in the SMB.

@JaredBusch said:

Maybe someday I will have to bend on that stance if something happens to my current client base but I have that luxury right now to be picky about the clients I keep. I'll give any client a chance, but historically that has only led to the hassle of collection attempts.

You can say that again! If they don't consider IT important, they definitely won't feel it's needed to pay for it either, instead they'll just steal your time like Scott mentions in another thread.

As for being a client or not... I was talking/arguing with a co-worker, not the people in charge. But that being said.. the people in charge definitely are frustrated that they have to do upgrades, why doesn't it just work like it did when I bought it? etc.