@scottalanmiller lol

@DustinB3403 said in Windows Server 2012 Essentials Cannot Find Login Server for AD:

That's rough.

Very

Thanks all

@scottalanmiller Right and they leap at that without a full picture, that's all I was admittedly trying to say.

So what we are pretty sure we have narrowed it down to is a WiFi device that reports the temperature of the refrigerator to an online portal that sends out notifications when there is an out of range event.

There is an inside the fridge sensor and that sends the information to a receiver outside the fridge. The receiver part is what has the WiFi built in. I think the inside sensor to outside receiver communicate using 900 Mhz.

Who would have thought to check the refrigerator?

@obsolesce said in Handling DNS in a Single Active Directory Domain Controller Environment:

@scottalanmiller said in Handling DNS in a Single Active Directory Domain Controller Environment:

@obsolesce said in Handling DNS in a Single Active Directory Domain Controller Environment:

@stuartjordan said in Handling DNS in a Single Active Directory Domain Controller Environment:

I believe the forest level with Samba can only be 2008R2 though.

If you're not using Windows AD, what's it matter?

If he's merging in DFS, it might. It's rare to do, but could matter.

Oh I see, so Windows AD and other services were involved at some point.

Depending on what you want to do, sometimes AD has to support it.

@phlipelder said in Get Wildcard SSL Certs for IIS on Windows with LetsEncrypt:

@scottalanmiller said in Get Wildcard SSL Certs for IIS on Windows with LetsEncrypt:

@phlipelder said in Get Wildcard SSL Certs for IIS on Windows with LetsEncrypt:

@scottalanmiller said in Get Wildcard SSL Certs for IIS on Windows with LetsEncrypt:

@phlipelder said in Get Wildcard SSL Certs for IIS on Windows with LetsEncrypt:

@jaredbusch said in Get Wildcard SSL Certs for IIS on Windows with LetsEncrypt:

@scottalanmiller my problem with Certs on Windows, in general, is that you almost always have to copy it around to multiple servers to make everything work well, and that jsut defeats the purpose of LE.

Based on what is on the site, Microsoft has an intrinsic trust with LE's root store. I should be able to set up a RD Session Host with a LE certificate for publishing and there should be no untrusted publisher for RemoteApps or Session Host desktops once the certificate's thumbprint is published via Group Policy?

One would hope that they would. LE is like the standard in SSL Certs. It's from the EFF, way more trustworthy than other cert authorities, IMHO.

Snag: Valid for 90 days. In larger RDS farm settings this would be a bear to manage. That means the need for an automated process.

It is expected to be automated. SSL Cert updates should not be intrusive. All of the tools for LE SSL Certs are designed around the idea that you will automate them and never need to worry about them again. It's about being less of a snag, not more of one.

Got it thanks. Looks like a bit of a learning curve then. 🙂

It's not bad. I find learning the LE pieces easier than learning to do it the old fashioned way 🙂 And with LE it is "learn once and ignore", rather than "learn once, forget, do again in a year or two all over again."

@scottalanmiller Yeah both of my webservers use mariadb for example

@scottalanmiller said in What Is Expected of Microsoft Server Support?:

Did they fix something broken with the OS that IT could not have fixed?

There are some quirky poorly documented things that are sometimes need to be done with ESEUTIL, and repairing from corruption, or failed log replays on Exchange and SQL. In theory it's not always Microsofts fault (caused by storage layer issues).

The other issue is driver issues for IO devices. In theory this should be transative (supported by teh OEM who agree's to support your OS). That said OEM's often don't support the free OS's because they don't have joint engineering commitements to fix issues on them.

RedHat has hard commitments from Avago/Broadcom to fix a driver HBA issue if they find it. Having a Server that has a supported OS means they have Avago's commitment to spend hundreds of thousands of engineering time to fix an issue. Redhat will possibly work to mitigate it from their side if possible. Missing the OS vendor in this conversation/effort can make things move slower or stall. Avago and other component manufactoreres will refuse support calls from a customer who bought the device through an OEM so without the OEM listing your OS as supported you are kinda screwed.

(A long time ago) I saw a case where a I/O device had outright buggy silicon, and a driver and OS side workaround was needed to resolve it. This is all the more fun as how the I/O device engineering teams work is they generally refuse to work with a customer directly and require the OS vendor escalate the issue to them.

@emad-r said in Trying to correctly understand core licensing in a vmware environment:

@dave247

maybe this was answered here, but I was wondering if someone can correct me on this

If i put WIndows server VM with 2 cores on Hypervisor any brand which has 8 cores.

Do i need to license windows server VM for 2 cores or 8 cores ?

There are no cores at the VM level, those are vCPUs. Windows is licensed by cores, not by vCPUs. Cores are always physical, and the minimum is 16. No matter how you configure the VMs and vCPUs, you have to license 16 cores at a minimum.

A single vCPU could use sixteen cores or more to power it, the licensing is by the available power, not the configuration.

I update and reboot weekly where I can.

There are a few systems that fall out of this process though.

@dbeato said in Disable Network Level Authentication or NLA Remotely via PowerShell:

@scottalanmiller said in Disable Network Level Authentication or NLA Remotely via PowerShell:

(Get-WmiObject -class "Win32_TSGeneralSetting" -Namespace root\cimv2\terminalservices -ComputerName "remoteServer" -Filter "TerminalName='RDP-tcp'").SetUserAuthenticationRequired(0)

This worked, but also as soon as the server is updated to the latest then the issue goes away.

Yes, if you have that option.

This might be useful for some people:

https://mangolassi.it/topic/17197/disable-network-level-authentication-or-nla-remotely-via-powershell

GUI is there is the majority of cases for me.

You only lose on the core licensing if you have more than 16 cores on two processors or you have 1 processor wiht less than 16 cores.

1 processor with 16 cores = 1 16 core server license
1 processor with 12 cores = 1 16 core server license
1 processor with 8 cores = 1 16 core server license
2 processors with 8 cores = 1 16 core server license
2 processors with 12 cores = 1 16 core server license + 4 2 core server license packs

Microsoft designed it around the most common system being sold. Intel Xeon dual proc 8 core systems.

You can restart the Hyper-V Virtual Machine Management service or the Windows Remote Management service and it should work.