free780

They should just have Team available in the Windows and Mac Store. They may wait until the new teams is GA.

ICO have posted this https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2023/04/ico-statement-on-capita-incident/

Crucially don’t put your Papercut web server on the internet. Force it through azure app proxy if external access is needed. I wouldn’t be surprised if additional vulnerabilities are found. This happened to the spooler service and Exchange. Security researchers may examine Papercut more throughly and find vulnerabilities.

So the 1:1 user must be listed as an MDM user which I can only seem to update by making the user a local admin [emoji15]. I can remove their admin rights. A IKEv2 VPN profile can only be deployed to a user which seems very illogical given that device certificates are more secure than user certs/creds. There is a IPSEC profile but it doesn’t look like split tunnel will work. But it may obey the VPN settings work. Time and again Apple seem to make decisions that are not necessarily to do with security and make it hard to push settings to devices.

I'd setup a event forwarding server. If you have multiple DCs. I try and create a filter for each change and monitor.

Fine if you’ve got 1:1 devices and possibly a retention policy / archive mailboxes. Not good on shared devices unless you have FS Logix deployed.

Try ProofPoint. I’d stay away from Mimecast. All depends on your budget of course.

I’m trying to push a IKEv2 config out from JAMF and it keeps failing. I’ve had to use the User Scope. I’ve tried a custom PLIST file which doesn’t seem to work. Has anyone attempted this before ?

We encountered an issue with Virgin where it grabbed DNS lookups and you had to opt out of a service. I can’t pasted the link due to App Protection. But you opt out.

Using FSLogix containers can create a local cache. You do need the local storage to hold all your users profiles. You may be able to use deduplication .Even if the user doesn’t wait for sync to finish. The only downside is that if they want access when off site the files won’t be in their OneDrive. It’s all designed for 1:1 scenarios.

https://msft.it/60115C4kN Keep current.

I seem to remember trying to upgrade from 1607 with this issue. We just re-imaged but you can run some dism command offline in winpe prior to upgrade. It may be the system locale buts it’s been about 3 years since I did it.

Looks like MS are treating Server 2016 as EOL. https://directaccess.richardhicks.com/2023/03/14/always-on-vpn-rras-and-stale-connections/ I guess it’s time to upgrade to 2019/2022.

I'd just get Windows Update for Business Configured via GPO. As long as you have the bandwidth and/or WUDO configured correctly. WSUS can fail for all sorts of reasons.

https://www.veeam.com/kb4424

VMWare have posted an update. https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3k-release-notes.html

Seems accurate.

Looks like VMs missing this certificate fromt he UEFi firmware have the boot issue. 738A962BD9C81B727717AF17EE093FE9B4BAEEC0 CN=VMware Secure Boot Signing, O="VMware, Inc.", L=Palo Alto, S=California, C=US You can detect this by installing the UEFIv2 Power Module. Install-Module UEFIv2 -Verbose Get-UEFISecureBootCerts | Where-Object -Property signatureSubject -like "*boot*" | Select-Object -ExpandProperty Signature If the cert is present the Feb 2023 update will work. If not you may encounter the boot failure and have to disable secure boot.

Do you have the isolation feature enabled ? This won’t block ping but will block most other traffic. A device can get isolated if the update process for the client had a delay.

MS have acknowledged the issue. https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2022

Run Run now and don’t look back. I haven’t had to deal with Onscreen in over 2 years. It may because the cert isn’t trusted. Generally certs with IP addresses aren’t used.

Official KB from VMWare https://kb.vmware.com/s/article/90947

Multiple reports of VMs failing to boot after this months updates. Issues seems to be related to Secure Boot. https://www.borncity.com/blog/2023/02/15/patchday-windows-11-server-2022-updates-14-februar-2023/#comment-142437 I'd hold off on patching Server 2022 VMs.

Stay clear on Feb 2023s CU for Server 2022 it cause boot failures on VMWare. I'll do a seperate post.

Are these VMs? If so which hypervisor?