@scottalanmiller said in Should We Ever Talk About JBODs:

I'm not clear when we can ever usefully use the term where it doesn't prompt a long and confusing explanation to clear up what is actually intended. I have a feeling that this is a term that simply should not exist as there is just no time that using it is useful.

Does anyone have any idea of a time when it would actually be important to have this term and, if so, how would we use it without further explanation?

You configure Storage Spaces from JBODs. Or technically, DAS JBODs. JBOD enclosure?

I have a pile of JBODs... Literally a heap of hard drives waiting to find a trash can.

Its like comparing ReFS to NTFS. You should always use NTFS unless you have specific reasons to use ReFS. One example is using ReFS on a VM storage only volume... it will only be holding .vhdx files.

Maybe that's not the best example because you can't use ReFS some places... but I think enough to get my point across.

Happy birthday @scottalanmiller

@Grey said in GPO Path?:

So, what's the current method to add a single trusted site to my intranet zone in GPO, eh? And where do I modify all of the trusted sites/zones and activex now?

I was answering the above question. Of course these will say not configured, because you haven't configured them yet.

So if 4th is strictly using RSAT... would 5th be full automation using SCCM, SCVMM, Orchestrator, and App Controller?

@Grey said in GPO Path?:

@DustinB3403 said in GPO Path?:

What is your domain functional level?

@DustinB3403 said in GPO Path?:

Are you using IEAK 10 by chance?

I installed it last night when I saw your question. It's on my laptop. Nothing happens when I click on it so I'm unsure what's going on here. I'd be happier if it just gave me the ADM file.

@Tim_G said in GPO Path?:

@Grey said in GPO Path?:

So, what's the current method to add a single trusted site to my intranet zone in GPO, eh? And where do I modify all of the trusted sites/zones and activex now?

Trusted sites are User Config > Policies > Admin templates > Windows Compontnets/Internet Explorer/Internet Control Panel/Security Page > Site to Zone Assignment List

The number 2 is trusted sites. You can use *.domain.com and *.ip, and IP

Every item in that tree is 'not configured' and I'm expecting that there should be items just as shown in my initial image. There should be some stuff for activex and a whole list of allowed/trusted sites and certs for many internal locations. This path doesn't have it, and the path listed (initial pic) doesn't exist.

You have "Trusted Sites Zone" selected. Select "Security Page", and edit the template named "Site to Zone Assignment List"

@scottalanmiller said in What Are You Watching Now:

@Tim_G said in What Are You Watching Now:

Downton Abbey with my wife.

We loved the first several seasons but then we felt like it fell apart.

We're almost finished, and loved it all the way through. A small rough patch, but it pulled through really well.

Downton Abbey with my wife.

That's pretty cool. I can see that being used in environments like warehouses and stuff that don't really fit the profile for a full blown Microsoft AD setup.

@scottalanmiller said in Pronunciations of SQL Derived Database Names and Terms:

The copyright conflict is purely with the spelling, not the pronunciation, so that didn't change.

I totally get it, and it makes complete sense when you look at it like that. Sure, it was originally SEQUEL (name, spelling, and pronunciation), so you still call it that even though that's not its name anymore. And you make strong points.

In the English language, the letters of a word and their ordering dictate the pronunciation. In this case, the abbreviation would be the 'word'.

For a long time now, it's been Structured Query Language, abbreviated: SQL. It's the successor of just Query Language (QUEL).

Structured 'English' Query Language (SEQUEL) just straight up does not exist. You are calling something by a name that does not exist, be it due to legal reasons or otherwise doesn't matter. The name changed, the abbreviation changed, therefore, the pronunciation changed as well. To say "SEQUEL", is to say it's Structured ENGLISH query language, which it is no longer. If you said SQUEL, you'd still be incorrect because that's not the abbreviation.

@scottalanmiller said in Pronunciations of SQL Derived Database Names and Terms:

But when spelled SQL it was still called "sequel". So I don't follow the logic of why we would call it something else today, when SQL originally was pronounced "sequel."

The logic is quite simple: It was once SEQUEL, but is no longer. The product name has changed to SQL.

@Grey said in GPO Path?:

And where do I modify all of the trusted sites/zones and activex now?

I think that's in the GPP area too.

@Grey said in GPO Path?:

So, what's the current method to add a single trusted site to my intranet zone in GPO, eh? And where do I modify all of the trusted sites/zones and activex now?

Trusted sites are User Config > Policies > Admin templates > Windows Compontnets/Internet Explorer/Internet Control Panel/Security Page > Site to Zone Assignment List

The number 2 is trusted sites. You can use *.domain.com and *.ip, and IP

I'd just copy or update all of those settings in the IE Group Policy Preferences. It basically brings up a window like "Internet Options" that you can configure.

@Dashrender said in Windows Server 2016 Licences for cluster:

@Tim_G said in Windows Server 2016 Licences for cluster:

I just wrote a whole bunch of crap, then I found this and deleted it:

Yeah - JB had a phone call with MS or their agent and basically shut them down because they were telling him that he needed to license the passive failover server for the number of licenses that could be running there. Your post says differently

But what I'm thinking, is that because of this:

...you could just move the OSE DC license (along with all 50 VMs) to the other Node in the cluster. That way the passive failover server would be properly licensed.

I just wrote a whole bunch of crap, then I found this and deleted it:

Man this stuff can be confusing in that it can be taken so many different ways depending on your perspective going into it... but I think you are right and it is huge.

But now the best thing to do is to try to disprove it using the same word doc... If you can't, then I would say what you pointed out stands.

@Dashrender said in Windows Server 2016 Licences for cluster:

OK then - holy shit! Where has this information been this whole time? This kills many SMBs need to have DC licensing for VM failover nodes. Right? SA is often way less expensive than DC licenses.

Well, only if the other node is properly licensed. It says you are free to move it from licensed server to licensed server as often as you like. Not from licensed node (server) to unlicensed node (server).

Example, if Node1 in a cluster has Datacenter, and Node2 has Standard, already with 2 VMs on NOde2... then a VM cannot fail over from node1 to node2 because it's not licensed... "Licensed Server".

Or did I misunderstand you?

@Minion-Queen said in How's the weather?:

Seriously? In NY? Shouldn't it be like -5 and snowing?

What's the current weather like at your location? (no cheating)

A simple screen shot of your app will do!

Mine: A chilly wintry day!

@Dashrender said in Windows Server 2016 Licences for cluster:

Also, the above linked Word Document doesn't discuss 2016 at all, so it's possible there is a new document with new rules.

It is completely applicable to Server 2016.