This battlestation is fully operational!! We have the first seven nodes of lab power online now from California! Very excited for all of the cool, new projects that we will be doing shortly.

As a non-inline, backup or archival unit, I would trust this system if you get it working nicely. Likely FreeBSD or OpenSuse will be ideal. If you get it running in that capacity, then sending backups to it will be a great use of it. As long as it is not a dependency for any running system, it would be viable.

@travisdh1 said in CEH (Certified Ethical Hacker):

@scottalanmiller said in CEH (Certified Ethical Hacker):

next up the RUH... Renegade Unethical Hacker.

RUH means never having to say you're sorry?

But you will RUH the day that you messed with one?

@scottalanmiller said in Export WordPress Theme:

@stacksofplates said in Export WordPress Theme:

Why not just make the directory for the existing theme a git repo and clone it to the other?

I don't have access to the other server.

Ah that makes it more difficult.

@Son-of-Jor-El said in Over Investing Early Can Be Big Time Failure:

Interesting convo. I can't get into too much detail but in the solar industry it is ESSENTIAL to have the investors lined up. If you don't, you die.

Even with them lined up, you still want to spend money wisely.

The Linux versions of OpenJDK remain available I saw.

it is absolutely standard that it writes to the install location, it has to be modified as any install like this has to be. But you have to modify that behaviour.

@JaredBusch said in VyOS Port Address Translation for HTTPS:

@scottalanmiller said in VyOS Port Address Translation for HTTPS:

Got it working. The firewall rule was in the wrong section of the firewall.

You had it on eth0 local instead of eth0 in?

Yuppers.

That's one of those hotfixes that suck because it really has to be implemented ASAP.

@scottalanmiller said in Recovering Archived files via .OST:

@Dashrender said in Recovering Archived files via .OST:

I enforce small email quotas more to force people to clean up their shit than because I'm worried about the size on the server. But perhaps I shouldn't even worry about that.

I lean towards "don't worry about it" most of the time. But if quotas exist to force people to clean up, that rules out PSTs as that bypasses the cleanup requirement and, in fact, makes it far worse.

the only people who have PSTs in my environment are those that don't have quotas (management). The PSTs are mostly for archiving, but a few people still live and die by that old data. I should just reimport it and forget about it.

@scottalanmiller These were ordered and installed ~2 weeks ago.

I posted about it here.

@JaredBusch said in Hyper-V - 3 VM migrations to new host:

@Mike-Davis said in Hyper-V - 3 VM migrations to new host:

Were both of the Hosts domain joined?

Yes everything was domain joined. Honestly, they should always be domain joined.
You still need to allow constrained delegation though.
https://blogs.technet.microsoft.com/matthts/2012/06/10/configuring-kerberos-constrained-delegation-for-hyper-v-management/

The old host is Server 2008 R2 and the new host is running Server 2012 R2 if that makes a difference.

This makes a HUGE difference. Hyper-V was completely redone for Server 2012+

In this instance, I would export and import.

not true

even ws2016 hyper-v has something from pre-2008 (and especially azure fork -out, for example erasure coding implementation, load balancing etc)

There are multiple examples of powershell scripts that will email users with near expiring passwords. I really need to get off my ass and set on up on the DC at a few of my clients with constant problem users...

For those stumbling in here down the road, the current consensus is that FreePBX is the better option for your new PBX. Elastix 4 did release, but is not being updated enough to remain a contender at this point.

Even I've got workflow apps running and a new one is being built over the weekend by a friend for quoting. So quick and easy.

@scottalanmiller said in D-Link DSR-250n router port configuration:

If it was good gear or well known gear, it might have made sense. But D-Link stuff isn't worth saving.

Preach it!

I know a lot of people like D-Link, but I had issues with multiple pieces of equipment from D-Link a long time ago and have refused to ever look at it since.

I know that is honestly bad on my part, as I should not rule something out forever, but with all the newer option, just no reason to ever go back to it.

Just deleting the contents, its 2 years old, and the user didn't even knew it existed and hasn't accessed it.

Thanks guys.

PluralSight is pretty good, and very cheap

@JaredBusch

Cool I'll give that a read. Thanks

@Mike-Davis Assume everything dumb that could be done has been done down there. What a mess.