Norphy

Bulgaria

Common

Thanks Dave, I may well take you up on that offer.

Shepherd

I’ve preordered Starlink but they’re targeting the area in mid 2022. I need something in the shorter term. I’m also going to see if cellular broadband using an external antenna will work, but I’m not that hopeful that it will.

I’m moving up to what my friend @Roberto likes to call The Land of the Deep Fried Mars Bar (and he’s half Scottish so that’s allowed) at the end of the month. The house that I’m moving to is very rural and presently has two internet connections: a satellite connection and a DSL one. I’m now working for an MSP and will be working permanently from home, so a half decent internet connection is a hard and fast requirement. The trouble is, the DSL connection has pretty poor bandwidth (1.5-3mbps with a following wind) and the satellite connection has fair bandwidth but horrible latency (1 second is typical). Being as I’m going to be using Teams, RDP etc and will be using the latter over VPN, I’m dreading what that will be like. I’m therefore wondering if there is some kind of clever firewall/router widget out there that does L7 inspection, can take two WAN connections and then route traffic over them depending on the type of traffic that it is or the destination of the traffic. For example, any Teams traffic or traffic to my MSP’s NOC goes routed over the DSL and everything else that doesn’t care about latency goes over the satellite. I’m sure there must be something that can do it, possibly Pfsense or similar, or maybe an appliance from the likes of Sonicwall but I’m not sure what. Any recommendations? Cheers [emoji4] /edit Oh, and if either connection falls over, I’d want the router to automatically fail over all traffic to the active connection and use the conditional routing again once both connections are up.

There is a group policy setting which removes profiles that haven't been used in X days - you've not got that set have you?

Re-reading the Hitch Hiker's Guide to the Galaxy trilogy at the moment. Currently on the fifth book, looking forward to the sixth as I've not read that one before. I know that one wasn't written by Douglas Adams but reviews seemed to be positive nevertheless. It's one of those books that's both incredibly hard to get through at times, yet is incredibly rewarding at other times as well. So Long and Thanks For All the Fish is still my favourite.

Oh my, yes. If anything, this time they're worse as there doesn't appear to be a workaround aside from replacing a friggin' DLL file with one from an earlier patch. https://www.bleepingcomputer.com/news/microsoft/new-windows-10-kb5006670-update-breaks-network-printing/ https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1909#1723msgdesc https://www.papercut.com/support/known-issues/#mf Hence me posting: http://www.edugeek.net/forums/behind-red-door/132256-what-annoying-things-did-you-do-today-merged-pet-peeves-1343.html#post1923752

Came in here to post a Fast Show video. Noticed I’d already done it. Five years ago. Dang it

Lustbader

Piste.

Office 2016 and 2019 were always LTSC builds of Office, they just made the labelling more obvious with 2021. I think it's more accurate to say that LTSC builds of Office don't get feature updates, rather to say that they're not updated at all. They still get security updates during their lifetime. An LTSC build of Office is essentially a snapshot of the SAC at that particular point. This means LTSC is that the interface and feature set will remain the same for the entire life of the support cycle of the product, whereas the 365 version of the desktop Office client will receive regular feature updates. There are advantages to either solution; with the LTSC build you've got a consistent experience for the three/five years you've got it installed, whereas with the SAC build you're getting new feature updates as they become available and the SAC builds work better with the Office 365 web components. The disadvantage is that Microsoft have a habit of changing things on a whim and things end up not working the way that people expect after a hotfix. They also changed the default interface for Outlook in a recent update which caused wailing and the gnashing of teeth with one of my customers fairly recently. So it's a question of weighing up the pros and cons and deciding which is the best solution for you.

Rockets

If nothing else, you can change the permissions on the RM GPOs so that they don't apply to particular PCs or a group. There are ways around it. The important thing to remember, as much as RM like to obfuscate it, a CC4 domain is still just a bog standard AD domain with some extra software installed. Sure, there are some custom schema extensions that they put in there but there's still nothing inherently special about them. You don't need to add extra DCs to your network until you're ready to remove the RM CC4 site servers. There is absolutely no reason why you can't add some PCs which don't have the RM middleware layer on them to that domain and manage them in the non-RM way.

sudo...

Hank..

Cream.

Simple answer, yes. The patch leads do need to be the same grade as the rest of the fibre run between the buildings. So if you've got OM3 multimode cable, you'll need OM3 multimode patch leads.

Weaponry

Repetition.

Are these activation locked or not? If they're not, you might be able to put them into DFU mode and factory reset them with Apple Configurator. That will at least wipe them, but if they were signed into an iCloud account it won't help.

Today’s Penny Arcade https://www.penny-arcade.com/comic/2021/10/15

I don't think it's likely. Indulging in some speculation here: AFAIK Microsoft haven't publicly stated why the 8th Gen Core ix and 2nd Gen Ryzen is the minimum required CPU for Windows 11 but the most likely sounding theories to me are: 1) There's a security related feature built into Windows 11 which isn't enabled by default which requires a certain CPU instruction which either isn't available in the earlier versions of the CPU or, if it is, isn't as developed. 2) There have been a lot of widely publicised flaws with CPUs in the past couple of years like Meltdown and SPECTRE which have workarounds either in firmware or CPU microcode updates, and older CPUs aren't as likely to have those workarounds. Either way, it's probably security related and those security reasons aren't going to go away just because we want them to. If reason 1 is true, chances are that subsequent releases of Windows 11 are going to first enable the security feature by default, then enforce it. That sort of thing is likely to come with a major release of the OS (e.g. 22H2, 23H2 etc) rather than a hotfix. That's probably what Microsoft mean when they say that they reserve the right not to update the OS on anything that's not officially supported. So, right now, this means that you can put Windows 11 on your unsupported Sandy Bridge based systems but come October next year it may well not work when the new build gets released. If you're going to keep hardware that doesn't officially support Windows 11, you're probably safer keeping Windows 10 on it. If you want to roll out Windows 11 to your estate, that means that it's safer to either wait until unsupported hardware is replaced or do it in phases with your newer hardware first. I would seriously recommend against putting W11 on unsupported hardware and putting it into production as you just don't know either when it's going to a) stop working or b) stop receiving security updates. If Microsoft do change their minds about which CPUs are supported by Windows 11, I find it unlikely that they're going to start supporting older CPUs. I think it's more likely that they're going to phase out ones which are supported right now. It's also worth pointing out that CPU requirements for Windows 10 now aren't the same as they were when Windows 10 1511 was released; Windows 10 1903 changed the CPU requirements and stopped support for a lot of older CPUs, mostly Atom based ones IIRC. Please don't take any of this as an endorsement and/or condemnation of what Microsoft are doing by the way. The fact is, this is the reality of what's happening and that reality is what we've got to work with.

Kohl..