TEAMS #new for Virtualized Desktop Infrascructure (VDI) #deadline 30/06/2024 **no longer supported on 2016**

IMPORTANT

Microsoft announced that Classic Teams for VDI will reach end of availability on June 30th, 2024.

In case your VDI farm is on Windows Server 2016 this is no longer supported, consider previous announcement you must plan VDI migration asap.

Original article

https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy

Other important blog articles:

Teams #New Virtual Desktop Infrastructure solution #MC717969 **CITRIX**365**AZURE**

Office - Microsoft 365 Apps and operative system supported roadmap

  • Windows Server 2016: October 2025
  • Windows Server 2019: October 2025
  • Windows Server 2022: October 2026


Teams #New Virtual Desktop Infrastructure solution #MC717969 **CITRIX**365**AZURE**

Microsoft announced that The new Virtual Desktop Infrastructure (VDI) solution for Microsoft Teams is a redesigned version of the existing VDI optimization (WebRTC based) 

This release applies to Microsoft Windows endpoints connecting to Microsoft Azure Virtual Desktops, Microsoft Windows 365, and Citrix VDI environments only.

Citrix Workspace app for Windows (2203 Long Term Service Release [LTSR], or 2302 Current Release [CR] or higher)

When this will happen:

Targeted Release: We will begin rolling out early April 2024 and expect to complete by late April 2024.

Standard Release: We will begin rolling out in late April 2024 and expect to complete by early May 2024.

This message is associated with Microsoft 365 Roadmap ID 375418

more details might be found here:


Office - Microsoft 365 Apps and operative system supported roadmap

I am taking note about fact that Microsoft 365 Apps is supported on the following versions of Windows Server until the dates specified:

  • Windows Server 2016: October 2025
  • Windows Server 2019: October 2025
  • Windows Server 2022: October 2026

This news will strongly affect infrastrucures where VDI are used on previously O.S. 

https://learn.microsoft.com/en-us/deployoffice/endofsupport/windows-server-migration

Vmware #ESX upgrade from 6.7. to 7 version #Error Failed to set the time via NTP

When you upgrade vCenter from 6.7 to 7 version you might face this error:

Error Failed to set the time via NTP

Details failed to synch to the NTP server

Code com.vmware.applmgmt.err_ntp_sync_failed

Could not setup time synchronization.

Resolution Verify that provided NTP servers are valid


Solution would be to sincronize NTP service pointing internal/external IP but changing Time Syncronization Settings mode to host

Here it is more detailed article:

https://pradeeppapnai.wordpress.com/2019/06/02/vcentermigrationntperror/

Software - FastStone Capture 10.0.4 screen/video capture and other similar softwares.

I would like to mention an excellent shareware software (that till 5.3 release version was free for personal use)
FastStone Capture has several features to acquire desktop screens and video as well (with high compression ratio)

Allows you to easily capture and annotate anything on the screen including windows, objects, menus, full screen, rectangular/freehand regions and even scrolling windows/web pages. It also allows you to record screen activities, sound and webcam into MP4 video files.

Here they are relative download links:

- Old versions: http://www.oldversion.com/windows/faststone-capture/
- Freeware 5.3 version: https://www.portablefreeware.com/?id=775
- Lastest versions: https://www.faststone.org/download.htm (20$ license price)






About similar softwares I would like to mention:
- PickPic https://picpick.app/
ShareX which has powerfull settings and it is completely open-source
- LightBox that permit to easily copy and paste images https://lightboxsoftware.com/
- Greenshot that permit to modify and acquire screenshots, saving to folder, in jpg format. Be aware that all steps are automatically done https://getgreenshot.org/

ANTIVIRUS #ERROR Request: WinHttpSendRequest failed: 12029 #SOPHOS

If you have a server/client 8.1/2012 facing this problem, indicated in device sophos log, you should follow this article installing correct Microsoft Patch:

https://support.sophos.com/support/s/article/KB-000039876?language=en_US