Domino

The Laura Palmer Barbie playset didn't really take off

If you can get rack shelves you can always lie the tower boxes sideways on them - something we've done in the past when rack kits aren't available

Something else to consider - Azure AD password protection can be extended to on-premise AD if the users have at least a P1 licence. https://learn.microsoft.com/en-us/entra/identity/authentication/howto-password-ban-bad-on-premises-deploy This'll use the same logic to block exposed or weak passwords that Azure uses, with the ability to add blocked terms (org name, etc) to the list. I've deployed it before, it's pretty easy to get going

leftfield option - I saw this once years ago. machine would totally lock up, took it out to a test bench, worked fine. Back to where it was, same issue. Tried swapping everything I could. ...eventually found the culprit, the USB mouse. Somehow it was malfunctioning so badly it caused the entire system to lock up. Never seen it since, but always stuck in my mind

In the teams admin portal Teams>Teams Settings>Email integration there's a setting for "users can send email to a channel email address" What are you trying to achieve? for mail to show up in teams you need to send to a channel email address IIRC

Is the time on both the DC and the host (and it's NTP config if present) it's running on correct? If it's been a long while since it's been patched you may be hitting this: https://support.microsoft.com/en-gb/topic/kb5011233-protections-in-cve-2022-21920-may-block-ntlm-authentication-if-kerberos-authentication-is-not-successful-dd415f99-a30c-4664-ba37-83d33fb071f4

Of course, there are things you could do to limit exposure, but it needs thinking about. The benefit of having an internal relay, aside from enabling TLS for the delivery over the internet, is the rule needs configuring only once regardless of how many additional devices you need to setup. Pays your money, takes your choice.

Couple of things here, if that outbound IP is a single NAT for the network, you're essentially allowing anything that can speak out on 25 on that IP to be accepted as long as the email address is valid. Might never be a problem, but worth keeping in mind if there's any enterprising young hacker types on site. Secondly, if you've multiple devices like this, setting up an internal IIS SMTP Relay to accept the mails, and then using the above config to have that send them on to 365 could be better. You can send via TLS (even if the source sends to the internal relay unencrypted) and not have the ILO IPs in a zone with any internet access at all (which is my preference).

You could also raise the issue with them through the 365 portal.

The hardcore miners have switched to ASIC - GPUs returns aren't worth the outlay anymore. I think Nvidia have gone off the extra support needed to support SLI, especially considering the diminishing returns and the power of the modern cards

From the amazon reviews from that second card: I assume he means "gen2 slot" at the end of that, in which case yeah, that's not a massively appreciable benefit over SATA. And certainly not what a 970 EVO is capable of.

IIRC the m.2 interface specifically supports PCI Express 3 (unless it's 4.0 designed variant that are specifically labelled as such) - I'm not sure you'll get an adapter to overcome that. Even if you could, there's major differences in the bandwidth overhead between PCIE 2 and 3 - I'm not sure you'd get the speed improvement much greater than a decent SATA SSD anyway?

Yes, you could break the licensing agreement and be subject to a hefty fine if caught

there's also the paging file to consider into the required space.. why not try reducing it by 2TB to begin with, you can always go down further after?

I followed this: https://jaapwesselius.com/2020/04/06/configure-oauth-authentication-in-exchange-2016/ No Hybrid, No Exchange Online Licenses for users. Your EWS needs to be externally accessible.