CISCO #HOW TO ENABLE DHCP ON SPECIFIC VLAN #switch #routers

Here they are commands that are required to, on a Router/L3 Switch, enable DHCP service.

There are other settings but, this example, simple give you a general idea:

Switch# config t

Switch(config)# 

Switch(config)# ip dhcp pool description_or_vlan_name

Switch(config-dhcp)# network lower_vlan_ip subnet

Switch(config-dhcp)# domain-name domain name

Switch(config-dhcp)# dns-server dns_server_1 dns_server_2 

Switch(config-dhcp)# default-router default_gateway_ip

Switch(config-dhcp)# ip dhcp excluded-address lower_vlan_ip_range upper_vlan_ip_range

Switch(config-dhcp)# ip dhcp excluded-address lower_vlan_ip_range upper_vlan_ip_range

related articles:

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr_dhcp/configuration/xe-3se/3850/dhcp-xe-3se-3850-book/config-dhcp-server.html

https://www.networkstraining.com/cisco-dhcp-configuration/

MICROSOFT #LSASS high usage #after patch installation #MARCH 2024 **how to fix**

Microsoft released bullettin advising customers experiencing excessive memory consumption by LSASS on Windows Server 2012-2022 DCs that have installed the following Windows Update(s): 

KB 5035857: March 12, 2024, KB5035857 (OS Build 20348.2340) Windows Server 2022 

KB 5035849: March 12, 2024, KB5035849 (OS Build 17763.5576) Windows Server 2019 

KB 5035855: March 14, 2024, KB5035855 (OS Build 14393.5786) Windows Server 2016

KB 5035885: March 12, 2024, KB5035885 Monthly Rollup for Windows Server 2012 R2: March 12, 2024 

Fortunately, there are workable solutions that you can use to address the high LSASS usage after the 3b Windows update has been installed.

https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2022#march-2024

Workarounds suggested by Microsoft are related to install below fix

https://support.microsoft.com/en-us/topic/march-22-2024-kb5037422-os-build-20348-2342-out-of-band-e8f5bf56-c7cb-4051-bd5c-cc35963b18f3

[original article]

https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/this-just-in-high-lsass-usage-after-windows-update-3b-march-2024/ba-p/4096250

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