I used to be in the same boat with a ton of movies for about 23TB but the NAS couldn't handle more than a single stream running Plex so I kept the NAS as just storage and setup the Plex server on an actual server. Then the NAS' only task was file sharing which it did well. I've now moved the entire Plex onto a Dell R520 LFF and leverage VMs as storage and Plex server at a colo. I stream from Rokus at my house that are connected to the Plex server at the colo. Stream full uncompressed 4k without any hiccups.

This is going to save me time. Was just starting to look at this.

@JaredBusch Thanks for the hint. I'll try to set that up.

I thought it was just me. I've had the exact same issue with the "wrong password" entry in the log when I know this not to be true. If I reload the console it reconnects. Voip.ms told me to connect to a different server but that just feels like they're avoiding having to solve the issue. It happens every few days.

I met with a prospective client today over video chat (wanted to reduce physical exposure for everyone until we're in a place where onsite visit is necessary) and she walked me through her current setup and what she'd like to do. One thing stood out for me as potentially problematic so wanted to check here to see if someone could point me in the right direction.

Her current IT admin (still employed there...for now) has setup a Windows 2016 server with Hyper-V role. He's the used Disk2VHD to create a disk image of each of their business' 8 PCs and loaded them up on the Windows server to run as virtual desktop. He then uninstalled all of the business software from each of their desktops so they are now essentially running their entire business via those virtual Win10 machines. Each physical desktop is now essentially a client for accessing the users' virtual PCs. Nothing is running on their physical PCs except Windows 10 Pro. All their software is running on their virtual desktops.

I'm pretty sure that's problematic in that they are in breach of MS licensing terms (I think). There are no CALs. They simply use the Remote Desktop client on their physical desktops to access their virtual PCs and it is a 1:1 setup with everyone having their own virtual Win10 PC. There is no AD of any kind.

If I understand the licensing correctly, in this setup, they would require Windows Software Assurance, Windows VDA subscription, or Windows E3/E5 licenses, do I have that right? They would also require CALs for the appropriate # of users, correct?

I have a client that uses Kimai for this.

https://www.kimai.org/

Got this email from MS today. Oh goody! MS is publicly announcing it is getting into the PUP/malware business

Getting flashbacks of Netscape v. Microsoft.

Starting with Version 2020 of Office 365 ProPlus, an extension for Microsoft Search in Bing will be installed that makes Bing the default search engine for the Google Chrome web browser. This extension will be installed with new installations of Office 365 ProPlus or when existing installations of Office 365 ProPlus are updated. If Bing is already the default search engine, the extension doesn't get installed.

https://docs.microsoft.com/en-gb/DeployOffice/microsoft-search-bing

https://know.bishopfox.com/advisories/connectwise-control

Don’t know who Bishop Fox is or whether they’re reliable and accurate but thought I’d share since many of us use the ConnectWise products.

https://pi-hole.net/2020/01/19/announcing-a-beta-test-of-pi-hole-5-0/

@DustinB3403 said in Break-Glass Access Control For Business Owners:

@NashBrydges said in Break-Glass Access Control For Business Owners:

That would work but would not provide the "notification" that it was used. Ideally, I would setup some kind of process so that I can be notified when they actually "break the glass". I think that's an important piece of the puzzle I'm trying to solve is to be notified when they access the credentials storage/file.

Break-glass would in my mind, be used because you had an emergency (like firing your IT personal) a notification to that same person or group seems worthless in my opinion.

In my case, if my clients accessed this storage/file, it would be important to know. Not only would that mean they are potentially looking to terminate relationship (not too worrying since this is part of doing business...the majority of my clients are from other IT service providers who have screwed the pooch) or that there was some reason for someone to access the credentials and, provided I'm still the service provider of choice, would now need to closely evaluate what was done and what caused them to need to access those credentials.

*edited for spelling