jtotheb

Yup, my favourite Teamsism is that if you've installed the Teams Installer it just installs Teams rather than Teams actually being installed. It's the Charlie Day red string meme come to life.

Yes, it will not install over the top/upgrade the existing Teams Machine-Wide Installer. An odd quirk we found to it not auto-updating was rather than downloading the update exe, click your avatar top right in Teams -> check for updates and see if it finishes itself off.

I don't know about Aruba, but Cisco normally have a "suggested" release listed alongside the latest releases. All of these are normally newer than what the device shipped with. As for checklist, I make sure I've got the configs and documentation for the old switch it's replacing so I know what the new one should be doing if it's a replacement.

Define easily? But yes, entirely doable. Take a look and see what flavour you fancy: GPO is via Restricted Groups. GPP is via Local Users and Groups.

Hyper-V is a Type 1 hypervisor. https://garvis.ca/2012/01/03/layer-1-or-layer-2-hypervisor-a-common-misconception-of-hyper-v-and-a-brief-explanation-of-the-parent-partition/ Even in Windows 10 the "host" OS runs on top of Hyper-V with passthrough. Hyper-V is still what touches the bare-metal. https://docs.microsoft.com/en-gb/virtualization/hyper-v-on-windows/about/

Cool, I'd be interested to know. The reason I ask is that in the same VLAN the client is going to find the PXE boot source via a broadcast. When the client is in a different VLAN it's going to be directed by the L3 device somehow to the PXE boot source (in Cisco land it'd be an "IP Helper" but I'm going to assume HP have something very similar). I'm wondering if the switch is having to rebuild a resolution table entry which is causing the initial time out.

Does it take a few attempts to connect to the server every time? E.g. once a machine in the classroom VLAN has started to PXE boot, if you restart the machine will it then PXE boot again straight away or does it start to require a few attempts to connect again?

Yes, CPU Ready Time should be the counter to keep an eye on in VMware to spot CPU over-subscription. It seems counter-intuitive to reduce vCPU count to actually get more use out of the physical CPU until you see it in action.

Minimum licence count is 10. Plus they do trials if you want to check it all out prior to purchase. Details are here if you need them: https://helpcenter.veeam.com/docs/vbo365/guide/vbo_licensing.html?ver=40

Is it a group SharePoint site as you only need the minimum (5 or 10 from memory) licence pack from Veeam to cover those?

You can have a device tunnel Always ON VPN in Windows 10 that can automagically establish the VPN connection prior to user login. Requires no user action. It's swings and roundabouts TBH. When it works the seamlessness is great, but as it all happens without any user intervention there's no feedback to the user if there's a problem.

UDP flood protection absolutely killed the AOVPN IKEv2 throughput, especially SMB traffic, with a Sophos UTM. A to/from exception got it up to what we'd expect to see.

Conditional access should do what you're after. https://docs.microsoft.com/en-us/onedrive/enable-conditional-access https://docs.microsoft.com/en-us/sharepoint/control-access-from-unmanaged-devices

TFTPD32 is another (has some other functionality as well as providing DHCP if you want/need it too) https://tftpd32.jounin.net/

That's normal for those models. The 9500 series that we've got lists the ports with a single label of their max speed regardless of the SFP/SFP+ inserted. It still makes my head hurt having a 1gig connection showing as TWEx/x/x.

Group Policy can sort out client certificate enrolment before they go off site. Never had to do it for devices already out in the field.

Upgrading the OS is explicitly ruled out. (That goes back to every version of Exchange I can remember) https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/prerequisites?view=exchserver-2016 Exchange 2019 on Server 2019 is the first pairing to support an OS upgrade. https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/prerequisites?view=exchserver-2019

Yeah, usually that's the way the DIRECTxxx dynamic connection works. If the infrastructure is 2.4Ghz and it's a single band wireless NIC then it could be grim.

The Microsoft adapters support both for communication, but 2.4ghz has to be enabled on the wireless NIC to pair initially.

You're correct, but it's a fair bit of work. The Microsoft guide is pretty good for the basics https://docs.microsoft.com/en-us/windows-server/remote/remote-access/vpn/always-on-vpn/ with Richard Hicks' blog a welcome resource for ironing out the kinks https://directaccess.richardhicks.com/

In that situation WDS is most likely only providing PXE boot and possibly multicast support for MDT. If you're not using WDS as the deployment platform and approving machines in WDS you wouldn't be aware of it. I hope that clears it up.

Are you using it within a single organisation or are you a third party service provider?

The iFixit iOpener with a toolkit is sub £20 on Amazon. iFixit do sell it as a standalone themselves.

Veeam used to bundle a third-party product with the cloud edition of Backup and Replication before they had their own cloud platform product. It's called Cloudberry Backup and we still use it to upload Veeam backup files to an online storage provider as we got a grandfathered perpetual licence when Veeam unbundled it. The Cloudberry job is backing up the folder(s) that contain Veeam backups to the cloud provider. That Cloudberry job is triggered by the "Run the following script after the job" option on the individual Veeam jobs. Might be worth a look, but I couldn't tell you how expensive, or not, it is to buy now.

Are they Intel I219-LM onboard NICs?