OpenAI Launches GPT-5 – a new leap in Artificial Intelligence

GPT-5 is the next generation of Generative Pre-trained Transformer models, succeeding GPT-4 and built to understand, process, and generate content with unprecedented speed and accuracy. The model is already integrated into ChatGPT, available to both free users (with limitations) and subscribers on Pro and Enterprise plans.

Major Upgrades Over GPT-4

  1. Advanced Multimodal Capabilities
    GPT-5 can seamlessly handle text, images, audio, and video, enabling complex, multi-input workflows in a single conversation.

  2. Extended Context of Over 1 Million Tokens
    Compared to GPT-4’s 128K token limit, GPT-5 can manage massive projects, complex codebases, and large documents without losing coherence.

  3. GPT-5-Thinking Mode
    An optimized variant for deep reasoning and tackling highly technical challenges — ideal for developers, researchers, and engineers.

  4. Reduced “Hallucinations”
    The error rate in generated responses has been significantly lowered thanks to improved internal verification systems and cleaner training data.

  5. Boosted Performance
    Faster response times and optimized processing costs make smaller variants like GPT-5-mini and GPT-5-nano practical for embedded and on-device AI applications.

Plans and Pricing

  • Free Users: Limited GPT-5 access.

  • Pro (~$200/month): Full access to GPT-5-Pro and GPT-5-Thinking

  • Business & Enterprise: API integration, advanced tool calling, and dedicated support.

The launch of GPT-5 signals the start of a new era in AI, with transformative potential across industries such as software development, automated journalism, data analysis, healthcare, and education.

OpenAI describes GPT-5 as “the most intelligent, fastest, and most useful AI we’ve ever built”, emphasizing both its raw capabilities and improved safety features.

[mai mult...]

Adobe – CVE-2025-47110 and Massive AEM Exposure: 225 vulnerabilities

Adobe released critical security updates in June for multiple products:

  • 225 vulnerabilities in Adobe Experience Manager (AEM)

  • CVE-2025-47110 in Adobe Commerce (Magento) – a high-risk reflected XSS vulnerability (CVSS 9.1) that can lead to client-side code execution.

Risks:

  • XSS can allow attackers to hijack sessions, modify content, or launch phishing attacks

  • In unpatched Magento stores, attackers can exploit poor sanitization in URL parameters to inject malicious scripts.

Recommendations:

  • Update AEM and Commerce to latest versions immediately

  • Use a Web Application Firewall (WAF) to block known exploit vectors

  • Perform regular scans and code reviews for custom plugins or templates.

[mai mult...]

Citrix – CVE-2025-6543: Buffer Overflow in NetScaler Gateway

Citrix disclosed CVE-2025-6543, a critical buffer overflow vulnerability in NetScaler ADC and Gateway devices when configured as VPN, RDP, or AAA virtual servers.

Key Points:

  • Allows unauthenticated remote DoS (Denial of Service) or potential code execution

  • Exploited in the wild – added to CISA’s Known Exploited Vulnerabilities (KEV) list on June 30

  • Affects several versions, including 14.1, 13.1, and FIPS builds

  • Attackers can crash or potentially gain control of exposed NetScaler endpoints.

Mitigation:

  • Patch immediately (builds: 14.1-47.46, 13.1-59.19, others listed in Citrix advisory)

  • For HA environments: use kill icaconnection -all and kill pcoipConnection -all before upgrade

  • Monitor VPN gateway logs and traffic for anomalies post-June 15.

[mai mult...]

Microsoft – CVE-2025-33053: Zero-Day WebDAV RCE Exploited by Stealth Falcon

On June 10th, Microsoft addressed a zero-day vulnerability — CVE-2025-33053, a Remote Code Execution (RCE) flaw in the WebDAV component of Windows. Researchers at Check Point reported that the APT group Stealth Falcon had actively exploited this flaw in targeted attacks.

Technical Details:

  • Attackers used malicious .url files that leveraged iediagcmd.exe (a signed Windows executable) to sideload malicious DLLs via trusted locations.

  • This chain led to the deployment of Horus Agent, a backdoor with advanced evasion and persistence tactics.

  • The vulnerability affects systems where WebDAV is enabled, especially those that interact with remote content or shared locations.

Impact & Recommendations:

  • Already exploited in the wild

  • Patch released via June Patch Tuesday – urgently apply all updates

  • Disable WebDAV where not required

  • Monitor event logs and audit execution from signed binaries in unusual directories.

[mai mult...]

Tutorial on MPLS (Multiprotocol Label Switching)

MPLS (Multiprotocol Label Switching) is a high-performance forwarding technique used in modern networks. It directs data from one node to the next based on short path labels rather than long network addresses, speeding up traffic flow and improving scalability.

How does MPLS work?

  1. When a packet enters the MPLS network (ingress router), it gets assigned a label

  2. MPLS routers (Label Switch Routers, LSRs) forward packets based on the label, not the IP header

  3. Labels are swapped at each hop according to the MPLS forwarding table

  4. At the exit router (egress), the label is removed, and the packet is forwarded based on its original IP address.

Key Concepts

  • Labels: Short fixed-length identifiers (usually 20 bits) added to packets

  • Label Edge Router (LER): Router that adds/removes labels at network edges

  • Label Switch Router (LSR): Router that forwards packets based on labels inside the MPLS network

  • Forwarding Equivalence Class (FEC): Group of packets forwarded the same way.

Advantages of MPLS

  • Speed: Labels simplify and accelerate packet forwarding

  • Scalability: Supports large-scale networks efficiently

  • Traffic Engineering: Allows path control to optimize bandwidth and avoid congestion

  • Supports multiple protocols: Works with IP, ATM, Frame Relay, etc.

Basic MPLS Configuration Example (Cisco IOS)

mpls ip
interface GigabitEthernet0/0
mpls ip
interface GigabitEthernet0/1
mpls ip

Use Cases

  • Service Provider VPNs (like VPLS and L3VPN)

  • Traffic Engineering for optimized routing

  • MPLS-based QoS and fast reroute.

[mai mult...]

Tutorial on OTV (Overlay Transport Virtualization)

OTV is a Cisco technology that extends Layer 2 networks over a Layer 3 IP network, allowing multiple data centers to appear as if they are on the same LAN even when geographically distant.

How does it work?

  1. OTV devices (usually Cisco Nexus switches) connect to the local Layer 2 network

  2. They create a virtual interface called an Overlay that carries Layer 2 frames encapsulated in IP packets (MAC-in-IP)

  3. The packets travel over the Layer 3 IP network between sites

  4. At the destination, packets are decapsulated and delivered to the local Layer 2 network.

Advantages:

  • Does not require multicast support in the IP network.

  • Avoids Layer 2 loops.

  • Supports VM mobility and disaster recovery.

Basic Cisco Nexus configuration example:

feature otv
otv site-vlan 4094
interface Overlay1
otv join-interface Ethernet1/1
otv control-group 239.1.1.1
otv data-group 239.1.1.2
no shutdown

Simple Tutorial on VPLS (Virtual Private LAN Service)

What is VPLS?

VPLS is an MPLS technology that allows extending an Ethernet Layer 2 network between multiple sites over a provider’s MPLS network, so all sites behave like a single LAN.

How does it work?

  1. The customer has CE routers at each site

  2. CE routers connect to the provider’s PE routers

  3. The MPLS provider creates Layer 2 tunnels between PE routers

  4. Ethernet traffic is carried across sites as if on the same LAN.

Advantages:

  • Scalable and secure

  • Connects multiple sites into one bridged network

  • Uses MPLS for performance and control.

Basic Cisco IOS configuration example:

mpls ip
l2vpn vpls context CLIENT1
vpn id 100
bridge-group VPLS-BRG
interface GigabitEthernet0/1
xconnect vpls CLIENT1 100
[mai mult...]

What is OTV (Overlay Transport Virtualization) and how it works in Modern Networks

OTV, or Overlay Transport Virtualization, is a network virtualization technology developed by Cisco that enables Layer 2 extension across a Layer 3 IP core—without the typical challenges of traditional tunneling or bridging.

In simple terms: OTV lets you connect multiple data centers as if they were part of the same LAN, even if they’re geographically distant.

OTV is designed to solve several problems when extending Layer 2 networks:

  • Avoids Layer 2 loops and broadcast storms

  • Requires no complex GRE or MPLS tunnels

  • Multicast-agnostic (doesn’t rely on multicast support in the core)

  • Ideal for data center interconnect (DCI), disaster recovery, and VM mobility

 How OTV Works

  • Edge Device: Connects the local LAN to the OTV overlay. Typically a Cisco Nexus 7000 or 9000 switch.

  • Join Interface: The Layer 3 interface used to reach the IP core.

  • Overlay Interface: A virtual interface that bridges Layer 2 domains across sites.

  • OTV encapsulates Layer 2 Ethernet frames inside IP packets (MAC-in-IP) for transport over the Layer 3 infrastructure.

OTV vs. Other Layer 2 Extension Technologies

Technology Overlay Type Scalability Complexity Multicast Dependency
OTV L2 over L3 High Medium No
VPLS L2 over MPLS Medium High Yes
VXLAN L2 over L3 Very High Medium Optional

Use OTV when you need:

  • Seamless connectivity between data centers

  • Zero-touch VM migration (vMotion)

  • Efficient disaster recovery configurations

  • Clean separation between core IP routing and Layer 2 domains.

[mai mult...]

End of Support for Remote Desktop App (Microsoft Store Version)

In 2025, Microsoft will implement significant changes to its Remote Desktop Protocol (RDP) ecosystem, with a particular focus on the deprecation of the Remote Desktop client (Microsoft Store version) and the transition to other solutions. As RDP plays a crucial role in enterprise IT environments, administrators must prepare for these changes to maintain secure and efficient remote access to critical resources. Below is a comprehensive overview of what administrators need to know, with a technical focus on migrating away from legacy solutions.

End of Support for Remote Desktop App (Microsoft Store Version)

Effective May 27, 2025, Microsoft will officially discontinue the Remote Desktop app from the Microsoft Store. This app, which has served as the main method for Windows clients to connect to remote desktops, will no longer be supported for remote access to services such as Azure Virtual Desktop (AVD), Windows 365, and Microsoft Dev Box.

From a technical standpoint, administrators must ensure that users who rely on this app transition to an alternative solution before support ends. The Remote Desktop app has several limitations, including:

  • Dependency on the Microsoft Store and lack of advanced customization capabilities for enterprise use.

  • Incompatibility with custom configurations such as custom Group Policies or RDP settings at the enterprise level.

To facilitate a smooth transition, Microsoft recommends moving users to the Windows App for accessing RDP-based services. This solution integrates better into enterprise ecosystems and offers the following advantages:

  1. Centralized Management via Microsoft Endpoint Manager (Intune):

    • The Windows App can be centrally managed via Intune, allowing for deployment and policy enforcement at scale.

    • Administrators can configure device redirection policies and enforce RDP security configurations at a granular level using Mobile Device Management (MDM) and Mobile Application Management (MAM).

  2. Enhanced Security and Compliance:

    • The Windows App supports Windows Hello for Business authentication and Multi-Factor Authentication (MFA), improving security during remote access sessions.

    • It integrates seamlessly with Azure Active Directory (Azure AD) for seamless user provisioning and identity management.

    • Administrators can apply conditional access policies to ensure only compliant devices can initiate remote desktop sessions.

  3. Advanced Networking Features:

    • The Windows App supports automatic VPN detection and direct routing for secure connectivity.

    • It integrates WAN optimization features, improving remote session performance over fluctuating network conditions.

  4. Customizable Deployment Options:

    • Windows App supports configurations for custom RDP file settings, allowing for more flexibility in deployment across different user groups or organizational departments.

    • Integration with Azure Virtual Desktop (AVD) and Windows 365 enables simplified session launching, reducing the need for manual configuration of RDP settings.

End of Support for Remote Desktop Client (MSI Version)

In addition to the Microsoft Store version, the standalone Remote Desktop client for Windows (MSI) will be deprecated as of March 27, 2026. While this client is still in use across many enterprises, its eventual obsolescence requires careful planning for a migration strategy. Key technical considerations include:

  • Deprecation of Support for Legacy RDP Protocols:

    • Organizations using custom RDP configurations tied to the MSI version must update their deployments to the Windows App or other Microsoft-supported RDP solutions.

    • Any use of custom RDP file configurations will need to be migrated or reconfigured in the new app.

  • Compatibility Testing:

    • For organizations that leverage the MSI RDP client with third-party RDP servers or custom load balancing configurations, comprehensive testing is required to ensure full compatibility with the Windows App.

    • Testing should include performance analysis, network load distribution, and failover mechanisms.

Traditional RDP (MSTSC) Support Continues

The legacy Remote Desktop Connection (MSTSC) tool will remain supported beyond 2025 and will continue to be a viable method for connecting to Windows servers or other RDP-enabled systems in environments where more complex configurations are unnecessary. However, MSTSC lacks the management and security benefits that come with the Windows App and Intune integration.

For enterprises relying on on-premises RDP servers or systems that do not yet use cloud-based solutions (such as Azure Virtual Desktop), MSTSC may still be the preferred option for basic RDP connectivity.

Action Steps for Administrators: A Detailed Technical Migration Guide

  1. Assess Existing RDP Infrastructure:

    • Identify all systems using the Microsoft Store app and the MSI client for remote access, including server configurations and VPNs.

    • Evaluate the network configurations, authentication requirements, and third-party integrations that will be impacted by the deprecation of the Microsoft Store app.

  2. Plan Transition to the Windows App:

    • Roll out the Windows App using Microsoft Endpoint Manager (Intune) for streamlined deployment and policy management.

    • Configure RDP settings, including device redirection, audio/video settings, and resource sharing policies via Intune to ensure compatibility with organizational requirements.

  3. Test Compatibility and Performance:

    • Perform pilot migrations with a small group of users, testing network latency, VPN performance, and resource access under real-world conditions.

    • Test compatibility with applications that rely on RDP for remote access, ensuring that custom configurations (such as session broker configurations or multi-session handling) are supported in the new app.

  4. Configure Centralized Security Controls:

    • Implement conditional access policies to restrict remote desktop access to compliant devices.

    • Enable Microsoft Defender for Endpoint for device protection and integrate with Microsoft Sentinel for continuous security monitoring of RDP connections.

  5. Migrate Users and Monitor Usage:

    • Migrate users in phases to reduce service disruption. Provide training and support resources to ensure a smooth transition.

    • Continuously monitor the performance and security of the migration process using Microsoft 365 Admin Center and Azure AD logs.

  6. Decommission Legacy RDP Clients:

    • Once the migration is complete, decommission legacy MSI RDP clients and Microsoft Store app installations.

    • Archive any data associated with legacy RDP solutions for compliance or future auditing requirements.

[mai mult...]

Migration from Skype to Microsoft Teams

As Microsoft officially ends support for Skype in 2025, Microsoft Teams has become the go-to platform for communication and collaboration within businesses. Migrating from Skype to Teams, particularly in larger organizations, requires careful planning, configuration, and execution. This guide will walk through the essential steps and technical considerations for administrators in the migration process.

While Skype revolutionized real-time communication, it lacks some critical features required by modern businesses. Microsoft Teams extends beyond chat and calling; it is an all-in-one collaboration suite that integrates with Microsoft 365 applications, including SharePoint, OneDrive, and Outlook. Teams also provides robust enterprise security and compliance capabilities, making it the ideal successor to Skype.

Additionally, Skype for Business is being phased out, and Microsoft Teams now supports business-critical functionalities such as:

  • VoIP calling

  • Meetings and video conferencing

  • Advanced file sharing and collaboration

  • Tight integration with the Microsoft 365 ecosystem

Steps for Migrating from Skype to Microsoft Teams

1. Preparation and Assessment

Before starting the migration, a comprehensive Skype usage assessment should be conducted. Administrators need to identify the features being used, such as:

  • Chat and messaging

  • VoIP calling and conferencing

  • Presence information

  • Screen sharing and file sharing

Once this assessment is done, the next step is to determine the necessary Teams configurations that will meet these needs. It’s also crucial to ensure that the Teams licensing aligns with your organization’s requirements, as different Teams plans offer varying levels of access to features like calling, meetings, and collaboration.

2. Teams Configuration

To configure Microsoft Teams for your organization, you must enable Teams in the Microsoft 365 Admin Center and set it as the default communication platform. This involves:

  • Configuring Teams policies for messaging, meetings, and calling.

  • Enabling features such as Teams Calling Plan, Direct Routing, or Operator Connect for VoIP services.

  • Setting up Security & Compliance Center policies for data retention, eDiscovery, and legal hold for Teams communications.

  • Integrating Azure Active Directory to manage user authentication and access to Teams resources.

For organizations that previously relied on Skype for Business, you’ll need to manage coexistence modes, which dictate how Skype and Teams will interact during the transition. The coexistence modes include:

  • Islands Mode: Skype and Teams operate independently.

  • Teams-Only Mode: All communication occurs exclusively through Teams.

  • Skype for Business-Only Mode: Skype is the primary platform, with Teams disabled.

3. User Migration and Transition

Once Teams is configured, it’s time to start the migration of users and data. Microsoft offers Skype to Teams Migration PowerShell Scripts and the Microsoft Teams Upgrade PowerShell Module to help automate the migration process. Key tasks during the migration include:

  • Migrating user chat history from Skype to Teams

  • Migrating users from Skype for Business Online to Teams

  • Ensuring all user profiles are updated in Active Directory

  • Transferring group chats, scheduled meetings, and file shares.

A phased migration approach is often recommended, where users can operate both Skype and Teams simultaneously (using Teams Only or Skype for Business modes) until all users are transitioned.

4. Configuring Teams Calling

If your organization relies on Skype for Business calling features (e.g., PSTN calls, voicemail, etc.), you will need to configure Teams to support Teams Calling Plans, Direct Routing, or Operator Connect. This involves:

  • Purchasing and assigning Teams Calling Licenses for users who require external calling.

  • Setting up Direct Routing with a Session Border Controller (SBC) if you’re using your own telephony infrastructure.

  • Configuring Teams Calling Policies for call forwarding, voicemail settings, and emergency calling.

5. User Training and Adoption

User adoption is critical for the success of the migration. Administrators must ensure that training materials and resources are available for end users to get acquainted with Teams. Microsoft offers Teams Training and Adoption Guides that can help users transition seamlessly. Key features to train users on include:

  • Navigating the Teams interface for chat, meetings, and file sharing

  • Understanding the difference between Channels, Teams, and Private Chats

  • Configuring Teams notifications and managing user presence

  • Sharing files and collaborating using OneDrive and SharePoint within Teams.

6. Testing and Validation

Before completing the migration, it is crucial to test key functionalities, including:

  • Call quality and reliability for VoIP and video conferencing

  • Message and file synchronization between Skype and Teams

  • Meeting scheduling and calendar integration with Outlook

  • Compliance and security controls to ensure data protection policies are met.

Testing should be done with a small group of users first, to identify any issues before rolling out Teams organization-wide.

7. Decommissioning Skype

Once Teams has been fully implemented, and all users have transitioned, you can begin the process of decommissioning Skype. This includes:

  • Disabling Skype for Business services

  • Archiving Skype data according to company compliance policies

  • Ensuring that users no longer rely on Skype for communication and collaboration.

Key Technical Considerations for Admins

  • License Management: Ensure the correct Microsoft 365 licenses are assigned to users based on the features they require (e.g., Teams Calling Plans, Office 365, Enterprise Mobility + Security).

  • Bandwidth Requirements: Teams calls and video conferencing may require significant bandwidth, especially with larger teams. Ensure your network infrastructure is prepared to handle Teams traffic.

  • End-User Experience: Teams offers a richer collaboration experience than Skype. It’s crucial to monitor the end-user experience and optimize configurations for performance and usability.

  • Compliance and Security: Teams offers advanced compliance features like information barriers, retention policies, and legal hold. Make sure these are configured according to your organization’s compliance needs.

[mai mult...]

Skype Officially shuts down after 22 Years

Skype revolutionized the way people connected across the globe, offering free video and voice calls long before Zoom or WhatsApp became mainstream. In its prime, “Skype” was a verb. However, in recent years, Skype lost market share to faster, more integrated platforms. Microsoft has gradually been phasing out Skype in favor of Microsoft Teams, especially in the business and education sectors. Today marks the official end of that transition.

What happens to user accounts?

Users are encouraged to export their chat history and data before the service becomes inaccessible. Microsoft recommends switching to Teams, which now supports both business and personal communication.

[mai mult...]