@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.
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.
And where do I modify all of the trusted sites/zones and activex now?
I think that's in the GPP area too.
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?
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.
@scottalanmiller said in What Are You Doing Right Now:
@aidan_walsh said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@dafyre said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Just broke a dish while trying to do the dishes. Argh.
Ooops!
It was super slippery. It was in the sink, but it broke the dish underneath in the sink
Soapy dishes and coffee jitters don't go well together
It was olive oil that did it.
Olive oil in Italy? I wouldn't have guessed!
This is what I go by: (updated as of February 2017)
MS Volume Licensing
Edit: Found the link: http://www.microsoftvolumelicensing.com/Downloader.aspx?DocumentId=11907
(direct download to word doc)
Here's the page I got it from if English isn't your primary reading language: http://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=1&ShowArchived=true
And for all MS products: http://www.microsoftvolumelicensing.com/Default.aspx
Just seen you have Webroot running, ignore that part.
